DNS response history for ns5.ablecc.net

ns5.ablecc.net 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-24. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 428 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 ns5.ablecc.net.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

428 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.151.145.87

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns5.ablecc.net

Showing DNS history for 2026-08-24 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
37 2026-08-24 15:36 639231818080917481
120 ms 209.151.145.87
36 2026-08-24 15:19 639231807961539652
470 ms 209.151.145.87
35 2026-08-24 15:02 639231797631669865
469 ms 209.151.145.87
34 2026-08-24 14:09 639231765923559455
469 ms 209.151.145.87
33 2026-08-24 13:52 639231755868832964
30 ms 209.151.145.87
32 2026-08-24 13:35 639231745628278877
471 ms 209.151.145.87
31 2026-08-24 13:18 639231735407682062
471 ms 209.151.145.87
30 2026-08-24 12:25 639231703815441688
2007 ms 209.151.145.87
29 2026-08-24 12:09 639231693747052549
2722 ms 209.151.145.87
28 2026-08-24 11:52 639231683712487276
483 ms 209.151.145.87
27 2026-08-24 11:35 639231673513573868
469 ms 209.151.145.87
26 2026-08-24 10:42 639231641791249939
5 ms 209.151.145.87
25 2026-08-24 10:25 639231631866211033
4 ms 209.151.145.87
24 2026-08-24 10:09 639231621644955316
467 ms 209.151.145.87
23 2026-08-24 09:52 639231611478799259
153 ms 209.151.145.87
22 2026-08-24 08:59 639231579923718211
477 ms 209.151.145.87
21 2026-08-24 08:42 639231569810702936
574 ms 209.151.145.87
20 2026-08-24 08:25 639231559762411619
581 ms 209.151.145.87
19 2026-08-24 08:08 639231549663595407
4 ms 209.151.145.87
18 2026-08-24 07:16 639231518076817246
491 ms 209.151.145.87
17 2026-08-24 06:59 639231508078650885
4 ms 209.151.145.87
16 2026-08-24 06:43 639231498210697093
2720 ms 209.151.145.87
15 2026-08-24 06:26 639231488109699360
474 ms 209.151.145.87
14 2026-08-24 05:34 639231456772510692
4 ms 209.151.145.87
13 2026-08-24 05:17 639231447084631185
3 ms 209.151.145.87
12 2026-08-24 05:01 639231437208519473
4 ms 209.151.145.87
11 2026-08-24 04:44 639231427209627490
472 ms 209.151.145.87
10 2026-08-24 03:52 639231395791246644
3 ms 209.151.145.87
9 2026-08-24 03:36 639231386075551458
3 ms 209.151.145.87
8 2026-08-24 03:19 639231376208713791
2 ms 209.151.145.87
7 2026-08-24 03:03 639231366170589276
119 ms 209.151.145.87
6 2026-08-24 02:10 639231334732159368
120 ms 209.151.145.87
5 2026-08-24 01:54 639231325035670078
467 ms 209.151.145.87
4 2026-08-24 01:38 639231315132253837
3 ms 209.151.145.87
3 2026-08-24 01:21 639231305014280808
486 ms 209.151.145.87
2 2026-08-24 00:28 639231273779380675
4 ms 209.151.145.87
1 2026-08-24 00:13 639231264180839154
2 ms 209.151.145.87