DNS response history for ns2.route53med.com

ns2.route53med.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 27 DNS check records, 27 successful responses, 0 failed responses, and 417 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.route53med.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

417 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.180.146.158

Most recently resolved hosting IP on selected date

Successful Responses

27

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.route53med.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
27 2026-08-26 08:44 639233297961740122
317 ms 66.180.146.158
26 2026-08-26 08:26 639233287487159094
505 ms 66.180.146.158
25 2026-08-26 08:09 639233276995531707
325 ms 66.180.146.158
24 2026-08-26 07:51 639233266521568229
330 ms 66.180.146.158
23 2026-08-26 07:34 639233256081047431
330 ms 66.180.146.158
22 2026-08-26 06:40 639233223620132921
729 ms 66.180.146.158
21 2026-08-26 06:23 639233213287814244
497 ms 66.180.146.158
20 2026-08-26 06:05 639233202925983161
487 ms 66.180.146.158
19 2026-08-26 05:48 639233192644780696
508 ms 66.180.146.158
18 2026-08-26 05:31 639233182401183833
489 ms 66.180.146.158
17 2026-08-26 05:14 639233172074181051
504 ms 66.180.146.158
16 2026-08-26 04:57 639233161808421455
337 ms 66.180.146.158
15 2026-08-26 04:39 639233151357344052
322 ms 66.180.146.158
14 2026-08-26 04:22 639233141034116946
323 ms 66.180.146.158
13 2026-08-26 04:05 639233130828334142
330 ms 66.180.146.158
12 2026-08-26 03:48 639233120373450007
329 ms 66.180.146.158
11 2026-08-26 03:30 639233110066216193
328 ms 66.180.146.158
10 2026-08-26 02:37 639233078065410564
333 ms 66.180.146.158
9 2026-08-26 02:20 639233067787457832
486 ms 66.180.146.158
8 2026-08-26 02:03 639233057501801162
344 ms 66.180.146.158
7 2026-08-26 01:46 639233047089431703
484 ms 66.180.146.158
6 2026-08-26 01:28 639233036754790688
491 ms 66.180.146.158
5 2026-08-26 01:11 639233026412602472
488 ms 66.180.146.158
4 2026-08-26 00:54 639233016064066127
335 ms 66.180.146.158
3 2026-08-26 00:37 639233005922655772
480 ms 66.180.146.158
2 2026-08-26 00:20 639232995672256907
499 ms 66.180.146.158
1 2026-08-26 00:03 639232985300872416
332 ms 66.180.146.158