DNS response history for ns4.harenohi.world

ns4.harenohi.world 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-27. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 562 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 ns4.harenohi.world.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

562 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

220.110.205.71

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns4.harenohi.world

Showing DNS history for 2026-08-27 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
30 2026-08-27 09:51 639234202117531850
508 ms 220.110.205.71
29 2026-08-27 09:33 639234191649612722
600 ms 220.110.205.71
28 2026-08-27 09:16 639234181105879568
588 ms 220.110.205.71
27 2026-08-27 08:58 639234170713214496
473 ms 220.110.205.71
26 2026-08-27 08:41 639234160341037652
624 ms 220.110.205.71
25 2026-08-27 08:24 639234149799404224
496 ms 220.110.205.71
24 2026-08-27 08:06 639234139553286469
758 ms 220.110.205.71
23 2026-08-27 07:12 639234107183588293
581 ms 220.110.205.71
22 2026-08-27 06:55 639234096905435724
463 ms 220.110.205.71
21 2026-08-27 06:38 639234086579410775
534 ms 220.110.205.71
20 2026-08-27 06:21 639234076291157956
639 ms 220.110.205.71
19 2026-08-27 06:04 639234065981939454
518 ms 220.110.205.71
18 2026-08-27 05:47 639234055548642997
518 ms 220.110.205.71
17 2026-08-27 05:29 639234045267979603
602 ms 220.110.205.71
16 2026-08-27 05:12 639234034999717463
806 ms 220.110.205.71
15 2026-08-27 04:55 639234024739225358
526 ms 220.110.205.71
14 2026-08-27 04:38 639234014311170162
511 ms 220.110.205.71
13 2026-08-27 04:20 639234003806017640
634 ms 220.110.205.71
12 2026-08-27 04:03 639233993356203030
537 ms 220.110.205.71
11 2026-08-27 03:09 639233961301716608
633 ms 220.110.205.71
10 2026-08-27 02:52 639233950834200647
511 ms 220.110.205.71
9 2026-08-27 02:35 639233940431849026
484 ms 220.110.205.71
8 2026-08-27 02:17 639233930110596398
527 ms 220.110.205.71
7 2026-08-27 02:00 639233919705434540
508 ms 220.110.205.71
6 2026-08-27 01:43 639233909452807845
635 ms 220.110.205.71
5 2026-08-27 01:26 639233899096420820
499 ms 220.110.205.71
4 2026-08-27 01:08 639233888707824939
507 ms 220.110.205.71
3 2026-08-27 00:51 639233878461203802
530 ms 220.110.205.71
2 2026-08-27 00:34 639233868060868209
636 ms 220.110.205.71
1 2026-08-27 00:17 639233857450922991
468 ms 220.110.205.71