DNS response history for ns2.heredns.com

ns2.heredns.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-24. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 228 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.heredns.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

228 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

157.53.236.129

Most recently resolved hosting IP on selected date

Successful Responses

36

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.heredns.com

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
36 2026-08-24 15:10 639231807961539652
46 ms 157.53.236.129
35 2026-08-24 14:53 639231797631669865
2018 ms 157.53.236.129
34 2026-08-24 14:00 639231765923559455
112 ms 157.53.236.129
33 2026-08-24 13:43 639231755868832964
17 ms 157.53.236.129
32 2026-08-24 13:26 639231745628278877
29 ms 157.53.236.129
31 2026-08-24 13:09 639231735407682062
133 ms 157.53.236.129
30 2026-08-24 12:17 639231703815441688
109 ms 157.53.236.129
29 2026-08-24 12:00 639231693747052549
19 ms 157.53.236.129
28 2026-08-24 11:43 639231683712487276
110 ms 157.53.236.129
27 2026-08-24 11:26 639231673513573868
150 ms 157.53.236.129
26 2026-08-24 10:33 639231641791249939
33 ms 157.53.236.129
25 2026-08-24 10:17 639231631866211033
100 ms 157.53.236.129
24 2026-08-24 10:00 639231621644955316
122 ms 157.53.236.129
23 2026-08-24 09:43 639231611478799259
92 ms 157.53.236.129
22 2026-08-24 08:50 639231579923718211
106 ms 157.53.236.129
21 2026-08-24 08:33 639231569810702936
120 ms 157.53.236.129
20 2026-08-24 08:16 639231559762411619
40 ms 157.53.236.129
19 2026-08-24 08:00 639231549663595407
114 ms 157.53.236.129
18 2026-08-24 07:07 639231518076817246
19 ms 157.53.236.129
17 2026-08-24 06:51 639231508078650885
119 ms 157.53.236.129
16 2026-08-24 06:34 639231498210697093
6 ms 157.53.236.129
15 2026-08-24 06:17 639231488109699360
113 ms 157.53.236.129
14 2026-08-24 05:25 639231456772510692
2020 ms 157.53.236.129
13 2026-08-24 05:09 639231447084631185
4 ms 157.53.236.129
12 2026-08-24 04:52 639231437208519473
102 ms 157.53.236.129
11 2026-08-24 04:36 639231427209627490
14 ms 157.53.236.129
10 2026-08-24 03:43 639231395791246644
29 ms 157.53.236.129
9 2026-08-24 03:27 639231386075551458
2009 ms 157.53.236.129
8 2026-08-24 03:11 639231376208713791
5 ms 157.53.236.129
7 2026-08-24 02:54 639231366170589276
13 ms 157.53.236.129
6 2026-08-24 02:02 639231334732159368
15 ms 157.53.236.129
5 2026-08-24 01:45 639231325035670078
41 ms 157.53.236.129
4 2026-08-24 01:29 639231315132253837
7 ms 157.53.236.129
3 2026-08-24 01:12 639231305014280808
120 ms 157.53.236.129
2 2026-08-24 00:20 639231273779380675
3 ms 157.53.236.129
1 2026-08-24 00:04 639231264180839154
114 ms 157.53.236.129