DNS response history for ns2.heimdal31.com

ns2.heimdal31.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, 34 successful responses, 2 failed responses, and 203 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.heimdal31.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

203 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.136.97.77

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

6%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.heimdal31.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:07 639231807961539652
2046 ms 185.136.97.77
35 2026-08-24 14:50 639231797631669865
32 ms 185.136.97.77
34 2026-08-24 13:57 639231765923559455
37 ms 185.136.97.77
33 2026-08-24 13:40 639231755868832964
7 ms 185.136.97.77
32 2026-08-24 13:23 639231745628278877
22 ms 185.136.97.77
31 2026-08-24 13:06 639231735407682062
12 ms 185.136.97.77
30 2026-08-24 12:13 639231703815441688
20 ms 185.136.97.77
29 2026-08-24 11:57 639231693747052549
5 ms 185.136.97.77
28 2026-08-24 11:40 639231683712487276
42 ms 185.136.97.77
27 2026-08-24 11:23 639231673513573868
50 ms 185.136.97.77
26 2026-08-24 10:30 639231641791249939
88 ms 185.136.97.77
25 2026-08-24 10:14 639231631866211033
22 ms 185.136.97.77
24 2026-08-24 09:56 639231621644955316
5 ms 185.136.97.77
23 2026-08-24 09:40 639231611478799259
65 ms 185.136.97.77
22 2026-08-24 08:47 639231579923718211
-
21 2026-08-24 08:30 639231569810702936
28 ms 185.136.97.77
20 2026-08-24 08:13 639231559762411619
-
19 2026-08-24 07:56 639231549663595407
9 ms 185.136.97.77
18 2026-08-24 07:04 639231518076817246
6 ms 185.136.97.77
17 2026-08-24 06:47 639231508078650885
13 ms 185.136.97.77
16 2026-08-24 06:31 639231498210697093
2058 ms 185.136.97.77
15 2026-08-24 06:14 639231488109699360
7 ms 185.136.97.77
14 2026-08-24 05:22 639231456772510692
4 ms 185.136.97.77
13 2026-08-24 05:06 639231447084631185
55 ms 185.136.97.77
12 2026-08-24 04:49 639231437208519473
8 ms 185.136.97.77
11 2026-08-24 04:32 639231427209627490
11 ms 185.136.97.77
10 2026-08-24 03:40 639231395791246644
4 ms 185.136.97.77
9 2026-08-24 03:24 639231386075551458
17 ms 185.136.97.77
8 2026-08-24 03:07 639231376208713791
48 ms 185.136.97.77
7 2026-08-24 02:51 639231366170589276
38 ms 185.136.97.77
6 2026-08-24 01:58 639231334732159368
2 ms 185.136.97.77
5 2026-08-24 01:42 639231325035670078
2025 ms 185.136.97.77
4 2026-08-24 01:26 639231315132253837
33 ms 185.136.97.77
3 2026-08-24 01:09 639231305014280808
13 ms 185.136.97.77
2 2026-08-24 00:17 639231273779380675
25 ms 185.136.97.77
1 2026-08-24 00:01 639231264180839154
39 ms 185.136.97.77