DNS response history for ns2.hiberd.com

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

26

Historical checks stored for this nameserver on selected date

Average Latency

201 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

136.243.150.138

Most recently resolved hosting IP on selected date

Successful Responses

26

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

Showing DNS history for 2026-08-26 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
26 2026-08-26 08:31 639233297961740122
41 ms 136.243.150.138
25 2026-08-26 08:14 639233287487159094
46 ms 136.243.150.138
24 2026-08-26 07:57 639233276995531707
60 ms 136.243.150.138
23 2026-08-26 07:39 639233266521568229
43 ms 136.243.150.138
22 2026-08-26 07:22 639233256081047431
50 ms 136.243.150.138
21 2026-08-26 06:28 639233223620132921
58 ms 136.243.150.138
20 2026-08-26 06:10 639233213287814244
27 ms 136.243.150.138
19 2026-08-26 05:53 639233202925983161
88 ms 136.243.150.138
18 2026-08-26 05:36 639233192644780696
69 ms 136.243.150.138
17 2026-08-26 05:19 639233182401183833
31 ms 136.243.150.138
16 2026-08-26 05:02 639233172074181051
54 ms 136.243.150.138
15 2026-08-26 04:45 639233161808421455
44 ms 136.243.150.138
14 2026-08-26 04:27 639233151357344052
73 ms 136.243.150.138
13 2026-08-26 04:10 639233141034116946
75 ms 136.243.150.138
12 2026-08-26 03:53 639233130828334142
35 ms 136.243.150.138
11 2026-08-26 03:36 639233120373450007
23 ms 136.243.150.138
10 2026-08-26 03:18 639233110066216193
64 ms 136.243.150.138
9 2026-08-26 02:25 639233078065410564
2044 ms 136.243.150.138
8 2026-08-26 02:08 639233067787457832
9 ms 136.243.150.138
7 2026-08-26 01:51 639233057501801162
2031 ms 136.243.150.138
6 2026-08-26 01:33 639233047089431703
58 ms 136.243.150.138
5 2026-08-26 01:16 639233036754790688
77 ms 136.243.150.138
4 2026-08-26 00:59 639233026412602472
29 ms 136.243.150.138
3 2026-08-26 00:42 639233016064066127
10 ms 136.243.150.138
2 2026-08-26 00:25 639233005922655772
61 ms 136.243.150.138
1 2026-08-26 00:08 639232995672256907
25 ms 136.243.150.138