DNS response history for ns2.hear.global

ns2.hear.global 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 29 DNS check records, 29 successful responses, 0 failed responses, and 21 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.hear.global.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

21 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.178.87.8

Most recently resolved hosting IP on selected date

Successful Responses

29

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.hear.global

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
29 2026-08-24 12:10 639231693747052549
27 ms 51.178.87.8
28 2026-08-24 11:53 639231683712487276
37 ms 51.178.87.8
27 2026-08-24 11:36 639231673513573868
9 ms 51.178.87.8
26 2026-08-24 10:43 639231641791249939
4 ms 51.178.87.8
25 2026-08-24 10:26 639231631866211033
10 ms 51.178.87.8
24 2026-08-24 10:10 639231621644955316
33 ms 51.178.87.8
23 2026-08-24 09:53 639231611478799259
25 ms 51.178.87.8
22 2026-08-24 09:00 639231579923718211
4 ms 51.178.87.8
21 2026-08-24 08:43 639231569810702936
130 ms 51.178.87.8
20 2026-08-24 08:26 639231559762411619
29 ms 51.178.87.8
19 2026-08-24 08:10 639231549663595407
40 ms 51.178.87.8
18 2026-08-24 07:17 639231518076817246
24 ms 51.178.87.8
17 2026-08-24 07:00 639231508078650885
31 ms 51.178.87.8
16 2026-08-24 06:44 639231498210697093
8 ms 51.178.87.8
15 2026-08-24 06:27 639231488109699360
4 ms 51.178.87.8
14 2026-08-24 05:35 639231456772510692
8 ms 51.178.87.8
13 2026-08-24 05:18 639231447084631185
3 ms 51.178.87.8
12 2026-08-24 05:02 639231437208519473
36 ms 51.178.87.8
11 2026-08-24 04:45 639231427209627490
10 ms 51.178.87.8
10 2026-08-24 03:53 639231395791246644
7 ms 51.178.87.8
9 2026-08-24 03:37 639231386075551458
26 ms 51.178.87.8
8 2026-08-24 03:20 639231376208713791
10 ms 51.178.87.8
7 2026-08-24 03:04 639231366170589276
9 ms 51.178.87.8
6 2026-08-24 02:11 639231334732159368
3 ms 51.178.87.8
5 2026-08-24 01:55 639231325035670078
7 ms 51.178.87.8
4 2026-08-24 01:39 639231315132253837
3 ms 51.178.87.8
3 2026-08-24 01:22 639231305014280808
20 ms 51.178.87.8
2 2026-08-24 00:29 639231273779380675
18 ms 51.178.87.8
1 2026-08-24 00:14 639231264180839154
35 ms 51.178.87.8