DNS response history for h2.core-dns.net

h2.core-dns.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-25. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 95 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 h2.core-dns.net.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

95 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

199.102.44.62

Most recently resolved hosting IP on selected date

Successful Responses

28

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 h2.core-dns.net

Showing DNS history for 2026-08-25 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
28 2026-08-25 09:34 639232471861770303
20 ms 199.102.44.62
27 2026-08-25 09:17 639232461630217327
29 ms 199.102.44.62
26 2026-08-25 09:00 639232451282965990
53 ms 199.102.44.62
25 2026-08-25 08:43 639232440814614938
5 ms 199.102.44.62
24 2026-08-25 08:25 639232430410720425
21 ms 199.102.44.62
23 2026-08-25 08:08 639232420003096185
39 ms 199.102.44.62
22 2026-08-25 07:50 639232409467287444
36 ms 199.102.44.62
21 2026-08-25 07:33 639232399077195997
8 ms 199.102.44.62
20 2026-08-25 07:16 639232388731528337
43 ms 199.102.44.62
19 2026-08-25 06:58 639232378288598612
16 ms 199.102.44.62
18 2026-08-25 06:05 639232346196373643
19 ms 199.102.44.62
17 2026-08-25 05:48 639232336112370741
10 ms 199.102.44.62
16 2026-08-25 05:31 639232326146508970
44 ms 199.102.44.62
15 2026-08-25 05:15 639232316189381720
69 ms 199.102.44.62
14 2026-08-25 04:58 639232306217998913
20 ms 199.102.44.62
13 2026-08-25 04:42 639232296255744174
30 ms 199.102.44.62
12 2026-08-25 04:25 639232286095760789
24 ms 199.102.44.62
11 2026-08-25 04:08 639232276086186273
36 ms 199.102.44.62
10 2026-08-25 03:51 639232265900986425
13 ms 199.102.44.62
9 2026-08-25 03:34 639232255723518075
5 ms 199.102.44.62
8 2026-08-25 03:17 639232245484452890
2020 ms 199.102.44.62
7 2026-08-25 03:00 639232235157175331
13 ms 199.102.44.62
6 2026-08-25 02:06 639232203197189095
5 ms 199.102.44.62
5 2026-08-25 01:49 639232192844564298
14 ms 199.102.44.62
4 2026-08-25 01:32 639232182496008942
8 ms 199.102.44.62
3 2026-08-25 01:15 639232172197053132
9 ms 199.102.44.62
2 2026-08-25 00:22 639232140250307418
6 ms 199.102.44.62
1 2026-08-25 00:04 639232129927860324
34 ms 199.102.44.62