DNS response history for ns2.hanflower.net

ns2.hanflower.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 571 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.hanflower.net.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

571 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

211.218.126.233

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.hanflower.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
544 ms 211.218.126.233
31 2026-08-26 09:54 639233339545274518
527 ms 211.218.126.233
30 2026-08-26 09:36 639233329214918079
578 ms 211.218.126.233
29 2026-08-26 09:19 639233318749762337
552 ms 211.218.126.233
28 2026-08-26 09:01 639233308387917838
539 ms 211.218.126.233
27 2026-08-26 08:44 639233297961740122
583 ms 211.218.126.233
26 2026-08-26 08:27 639233287487159094
568 ms 211.218.126.233
25 2026-08-26 08:09 639233276995531707
585 ms 211.218.126.233
24 2026-08-26 07:52 639233266521568229
574 ms 211.218.126.233
23 2026-08-26 07:34 639233256081047431
582 ms 211.218.126.233
22 2026-08-26 06:40 639233223620132921
679 ms 211.218.126.233
21 2026-08-26 06:23 639233213287814244
573 ms 211.218.126.233
20 2026-08-26 06:06 639233202925983161
557 ms 211.218.126.233
19 2026-08-26 05:48 639233192644780696
581 ms 211.218.126.233
18 2026-08-26 05:31 639233182401183833
551 ms 211.218.126.233
17 2026-08-26 05:14 639233172074181051
529 ms 211.218.126.233
16 2026-08-26 04:57 639233161808421455
573 ms 211.218.126.233
15 2026-08-26 04:40 639233151357344052
580 ms 211.218.126.233
14 2026-08-26 04:22 639233141034116946
580 ms 211.218.126.233
13 2026-08-26 04:05 639233130828334142
582 ms 211.218.126.233
12 2026-08-26 03:48 639233120373450007
574 ms 211.218.126.233
11 2026-08-26 03:31 639233110066216193
560 ms 211.218.126.233
10 2026-08-26 02:37 639233078065410564
583 ms 211.218.126.233
9 2026-08-26 02:20 639233067787457832
547 ms 211.218.126.233
8 2026-08-26 02:03 639233057501801162
583 ms 211.218.126.233
7 2026-08-26 01:46 639233047089431703
580 ms 211.218.126.233
6 2026-08-26 01:29 639233036754790688
580 ms 211.218.126.233
5 2026-08-26 01:11 639233026412602472
579 ms 211.218.126.233
4 2026-08-26 00:54 639233016064066127
584 ms 211.218.126.233
3 2026-08-26 00:37 639233005922655772
570 ms 211.218.126.233
2 2026-08-26 00:20 639232995672256907
587 ms 211.218.126.233
1 2026-08-26 00:03 639232985300872416
532 ms 211.218.126.233