DNS response history for ns2.jameshanson.net

ns2.jameshanson.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-26. For this date, NameServerHistory found 34 DNS check records, 33 successful responses, 1 failed responses, and 156 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.jameshanson.net.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

156 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

64.71.176.172

Most recently resolved hosting IP on selected date

Successful Responses

33

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.jameshanson.net

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:45 639233370841350248
180 ms 64.71.176.172
33 2026-08-26 10:28 639233360361507238
10 ms 64.71.176.172
32 2026-08-26 10:11 639233350067824371
67 ms 64.71.176.172
31 2026-08-26 09:53 639233339545274518
12 ms 64.71.176.172
30 2026-08-26 09:36 639233329214918079
181 ms 64.71.176.172
29 2026-08-26 09:19 639233318749762337
178 ms 64.71.176.172
28 2026-08-26 09:01 639233308387917838
174 ms 64.71.176.172
27 2026-08-26 08:44 639233297961740122
181 ms 64.71.176.172
26 2026-08-26 08:26 639233287487159094
181 ms 64.71.176.172
25 2026-08-26 08:09 639233276995531707
181 ms 64.71.176.172
24 2026-08-26 07:51 639233266521568229
174 ms 64.71.176.172
23 2026-08-26 07:34 639233256081047431
182 ms 64.71.176.172
22 2026-08-26 06:40 639233223620132921
174 ms 64.71.176.172
21 2026-08-26 06:23 639233213287814244
181 ms 64.71.176.172
20 2026-08-26 06:05 639233202925983161
9 ms 64.71.176.172
19 2026-08-26 05:48 639233192644780696
174 ms 64.71.176.172
18 2026-08-26 05:31 639233182401183833
-
17 2026-08-26 05:14 639233172074181051
178 ms 64.71.176.172
16 2026-08-26 04:57 639233161808421455
173 ms 64.71.176.172
15 2026-08-26 04:40 639233151357344052
9 ms 64.71.176.172
14 2026-08-26 04:22 639233141034116946
172 ms 64.71.176.172
13 2026-08-26 04:05 639233130828334142
173 ms 64.71.176.172
12 2026-08-26 03:48 639233120373450007
8 ms 64.71.176.172
11 2026-08-26 03:30 639233110066216193
174 ms 64.71.176.172
10 2026-08-26 02:37 639233078065410564
9 ms 64.71.176.172
9 2026-08-26 02:20 639233067787457832
1114 ms 64.71.176.172
8 2026-08-26 02:03 639233057501801162
8 ms 64.71.176.172
7 2026-08-26 01:46 639233047089431703
8 ms 64.71.176.172
6 2026-08-26 01:28 639233036754790688
7 ms 64.71.176.172
5 2026-08-26 01:11 639233026412602472
175 ms 64.71.176.172
4 2026-08-26 00:54 639233016064066127
174 ms 64.71.176.172
3 2026-08-26 00:37 639233005922655772
172 ms 64.71.176.172
2 2026-08-26 00:20 639232995672256907
176 ms 64.71.176.172
1 2026-08-26 00:03 639232985300872416
174 ms 64.71.176.172