DNS response history for ns2.hanserver.net

ns2.hanserver.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 32 DNS check records, 32 successful responses, 0 failed responses, and 554 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.hanserver.net.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

554 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

222.122.63.17

Most recently resolved hosting IP on selected date

Successful Responses

32

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.hanserver.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
32 2026-08-26 10:11 639233350067824371
519 ms 222.122.63.17
31 2026-08-26 09:53 639233339545274518
470 ms 222.122.63.17
30 2026-08-26 09:36 639233329214918079
629 ms 222.122.63.17
29 2026-08-26 09:19 639233318749762337
527 ms 222.122.63.17
28 2026-08-26 09:01 639233308387917838
463 ms 222.122.63.17
27 2026-08-26 08:44 639233297961740122
521 ms 222.122.63.17
26 2026-08-26 08:26 639233287487159094
535 ms 222.122.63.17
25 2026-08-26 08:09 639233276995531707
466 ms 222.122.63.17
24 2026-08-26 07:51 639233266521568229
465 ms 222.122.63.17
23 2026-08-26 07:34 639233256081047431
835 ms 222.122.63.17
22 2026-08-26 06:40 639233223620132921
462 ms 222.122.63.17
21 2026-08-26 06:23 639233213287814244
468 ms 222.122.63.17
20 2026-08-26 06:05 639233202925983161
913 ms 222.122.63.17
19 2026-08-26 05:48 639233192644780696
583 ms 222.122.63.17
18 2026-08-26 05:31 639233182401183833
575 ms 222.122.63.17
17 2026-08-26 05:14 639233172074181051
523 ms 222.122.63.17
16 2026-08-26 04:57 639233161808421455
522 ms 222.122.63.17
15 2026-08-26 04:40 639233151357344052
523 ms 222.122.63.17
14 2026-08-26 04:22 639233141034116946
563 ms 222.122.63.17
13 2026-08-26 04:05 639233130828334142
527 ms 222.122.63.17
12 2026-08-26 03:48 639233120373450007
569 ms 222.122.63.17
11 2026-08-26 03:30 639233110066216193
541 ms 222.122.63.17
10 2026-08-26 02:37 639233078065410564
570 ms 222.122.63.17
9 2026-08-26 02:20 639233067787457832
520 ms 222.122.63.17
8 2026-08-26 02:03 639233057501801162
565 ms 222.122.63.17
7 2026-08-26 01:46 639233047089431703
568 ms 222.122.63.17
6 2026-08-26 01:28 639233036754790688
564 ms 222.122.63.17
5 2026-08-26 01:11 639233026412602472
508 ms 222.122.63.17
4 2026-08-26 00:54 639233016064066127
589 ms 222.122.63.17
3 2026-08-26 00:37 639233005922655772
522 ms 222.122.63.17
2 2026-08-26 00:20 639232995672256907
566 ms 222.122.63.17
1 2026-08-26 00:03 639232985300872416
571 ms 222.122.63.17