DNS response history for ns2.mtcmanado.com

ns2.mtcmanado.com is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-26. For this date, NameServerHistory found 24 DNS check records, 24 successful responses, 0 failed responses, and 424 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for ns2.mtcmanado.com.
Records on Selected Date

24

Historical checks stored for this nameserver on selected date

Average Latency

424 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 07:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

31.97.66.230

Most recently resolved hosting IP on selected date

Successful Responses

24

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.mtcmanado.com

Showing DNS history for 2026-08-26 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
24 2026-08-26 07:51 639233266521568229
519 ms 31.97.66.230
23 2026-08-26 07:33 639233256081047431
339 ms 31.97.66.230
22 2026-08-26 06:39 639233223620132921
505 ms 31.97.66.230
21 2026-08-26 06:22 639233213287814244
507 ms 31.97.66.230
20 2026-08-26 06:05 639233202925983161
4 ms 31.97.66.230
19 2026-08-26 05:48 639233192644780696
180 ms 31.97.66.230
18 2026-08-26 05:30 639233182401183833
344 ms 31.97.66.230
17 2026-08-26 05:13 639233172074181051
3 ms 31.97.66.230
16 2026-08-26 04:56 639233161808421455
337 ms 31.97.66.230
15 2026-08-26 04:39 639233151357344052
166 ms 31.97.66.230
14 2026-08-26 04:22 639233141034116946
339 ms 31.97.66.230
13 2026-08-26 04:04 639233130828334142
333 ms 31.97.66.230
12 2026-08-26 03:47 639233120373450007
506 ms 31.97.66.230
11 2026-08-26 03:30 639233110066216193
166 ms 31.97.66.230
10 2026-08-26 02:37 639233078065410564
277 ms 31.97.66.230
9 2026-08-26 02:20 639233067787457832
1013 ms 31.97.66.230
8 2026-08-26 02:02 639233057501801162
343 ms 31.97.66.230
7 2026-08-26 01:45 639233047089431703
336 ms 31.97.66.230
6 2026-08-26 01:28 639233036754790688
344 ms 31.97.66.230
5 2026-08-26 01:11 639233026412602472
180 ms 31.97.66.230
4 2026-08-26 00:53 639233016064066127
1679 ms 31.97.66.230
3 2026-08-26 00:36 639233005922655772
924 ms 31.97.66.230
2 2026-08-26 00:19 639232995672256907
505 ms 31.97.66.230
1 2026-08-26 00:02 639232985300872416
338 ms 31.97.66.230