DNS response history for ns2.hamerdns.com

ns2.hamerdns.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 34 DNS check records, 34 successful responses, 0 failed responses, and 396 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.hamerdns.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

396 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

71.19.251.36

Most recently resolved hosting IP on selected date

Successful Responses

34

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.hamerdns.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
34 2026-08-26 10:43 639233370841350248
343 ms 71.19.251.36
33 2026-08-26 10:26 639233360361507238
327 ms 71.19.251.36
32 2026-08-26 10:08 639233350067824371
327 ms 71.19.251.36
31 2026-08-26 09:51 639233339545274518
347 ms 71.19.251.36
30 2026-08-26 09:34 639233329214918079
346 ms 71.19.251.36
29 2026-08-26 09:16 639233318749762337
2187 ms 71.19.251.36
28 2026-08-26 08:59 639233308387917838
330 ms 71.19.251.36
27 2026-08-26 08:42 639233297961740122
469 ms 71.19.251.36
26 2026-08-26 08:24 639233287487159094
327 ms 71.19.251.36
25 2026-08-26 08:07 639233276995531707
327 ms 71.19.251.36
24 2026-08-26 07:49 639233266521568229
348 ms 71.19.251.36
23 2026-08-26 07:32 639233256081047431
342 ms 71.19.251.36
22 2026-08-26 06:38 639233223620132921
326 ms 71.19.251.36
21 2026-08-26 06:21 639233213287814244
341 ms 71.19.251.36
20 2026-08-26 06:03 639233202925983161
360 ms 71.19.251.36
19 2026-08-26 05:46 639233192644780696
366 ms 71.19.251.36
18 2026-08-26 05:29 639233182401183833
345 ms 71.19.251.36
17 2026-08-26 05:12 639233172074181051
325 ms 71.19.251.36
16 2026-08-26 04:55 639233161808421455
427 ms 71.19.251.36
15 2026-08-26 04:37 639233151357344052
327 ms 71.19.251.36
14 2026-08-26 04:20 639233141034116946
325 ms 71.19.251.36
13 2026-08-26 04:03 639233130828334142
175 ms 71.19.251.36
12 2026-08-26 03:46 639233120373450007
345 ms 71.19.251.36
11 2026-08-26 03:28 639233110066216193
346 ms 71.19.251.36
10 2026-08-26 02:35 639233078065410564
335 ms 71.19.251.36
9 2026-08-26 02:18 639233067787457832
345 ms 71.19.251.36
8 2026-08-26 02:01 639233057501801162
345 ms 71.19.251.36
7 2026-08-26 01:44 639233047089431703
352 ms 71.19.251.36
6 2026-08-26 01:26 639233036754790688
363 ms 71.19.251.36
5 2026-08-26 01:09 639233026412602472
341 ms 71.19.251.36
4 2026-08-26 00:52 639233016064066127
341 ms 71.19.251.36
3 2026-08-26 00:35 639233005922655772
326 ms 71.19.251.36
2 2026-08-26 00:18 639232995672256907
354 ms 71.19.251.36
1 2026-08-26 00:01 639232985300872416
344 ms 71.19.251.36