DNS response history for ns3.deverhood.com

ns3.deverhood.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 28 DNS check records, 28 successful responses, 0 failed responses, and 608 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 ns3.deverhood.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

608 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

122.155.180.161

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 ns3.deverhood.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
28 2026-08-26 09:00 639233308387917838
209 ms 122.155.180.161
27 2026-08-26 08:43 639233297961740122
1710 ms 122.155.180.161
26 2026-08-26 08:26 639233287487159094
207 ms 122.155.180.161
25 2026-08-26 08:08 639233276995531707
1727 ms 122.155.180.161
24 2026-08-26 07:51 639233266521568229
201 ms 122.155.180.161
23 2026-08-26 07:33 639233256081047431
377 ms 122.155.180.161
22 2026-08-26 06:39 639233223620132921
371 ms 122.155.180.161
21 2026-08-26 06:22 639233213287814244
1867 ms 122.155.180.161
20 2026-08-26 06:05 639233202925983161
205 ms 122.155.180.161
19 2026-08-26 05:48 639233192644780696
402 ms 122.155.180.161
18 2026-08-26 05:30 639233182401183833
211 ms 122.155.180.161
17 2026-08-26 05:13 639233172074181051
1341 ms 122.155.180.161
16 2026-08-26 04:56 639233161808421455
10 ms 122.155.180.161
15 2026-08-26 04:39 639233151357344052
418 ms 122.155.180.161
14 2026-08-26 04:22 639233141034116946
405 ms 122.155.180.161
13 2026-08-26 04:04 639233130828334142
189 ms 122.155.180.161
12 2026-08-26 03:47 639233120373450007
194 ms 122.155.180.161
11 2026-08-26 03:30 639233110066216193
409 ms 122.155.180.161
10 2026-08-26 02:37 639233078065410564
2190 ms 122.155.180.161
9 2026-08-26 02:20 639233067787457832
211 ms 122.155.180.161
8 2026-08-26 02:02 639233057501801162
1331 ms 122.155.180.161
7 2026-08-26 01:45 639233047089431703
397 ms 122.155.180.161
6 2026-08-26 01:28 639233036754790688
415 ms 122.155.180.161
5 2026-08-26 01:11 639233026412602472
411 ms 122.155.180.161
4 2026-08-26 00:53 639233016064066127
409 ms 122.155.180.161
3 2026-08-26 00:36 639233005922655772
371 ms 122.155.180.161
2 2026-08-26 00:19 639232995672256907
428 ms 122.155.180.161
1 2026-08-26 00:02 639232985300872416
403 ms 122.155.180.161