DNS response history for ns.jf-wakachu.com

ns.jf-wakachu.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 36 DNS check records, 36 successful responses, 0 failed responses, and 607 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 ns.jf-wakachu.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

607 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.230.232.240

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns.jf-wakachu.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
36 2026-08-26 11:58 639233414056832719
514 ms 202.230.232.240
35 2026-08-26 11:40 639233403515141099
493 ms 202.230.232.240
34 2026-08-26 10:46 639233370841350248
779 ms 202.230.232.240
33 2026-08-26 10:28 639233360361507238
493 ms 202.230.232.240
32 2026-08-26 10:11 639233350067824371
484 ms 202.230.232.240
31 2026-08-26 09:54 639233339545274518
504 ms 202.230.232.240
30 2026-08-26 09:36 639233329214918079
492 ms 202.230.232.240
29 2026-08-26 09:19 639233318749762337
772 ms 202.230.232.240
28 2026-08-26 09:02 639233308387917838
488 ms 202.230.232.240
27 2026-08-26 08:44 639233297961740122
1038 ms 202.230.232.240
26 2026-08-26 08:27 639233287487159094
487 ms 202.230.232.240
25 2026-08-26 08:10 639233276995531707
761 ms 202.230.232.240
24 2026-08-26 07:52 639233266521568229
498 ms 202.230.232.240
23 2026-08-26 07:34 639233256081047431
760 ms 202.230.232.240
22 2026-08-26 06:40 639233223620132921
775 ms 202.230.232.240
21 2026-08-26 06:23 639233213287814244
766 ms 202.230.232.240
20 2026-08-26 06:06 639233202925983161
487 ms 202.230.232.240
19 2026-08-26 05:49 639233192644780696
764 ms 202.230.232.240
18 2026-08-26 05:31 639233182401183833
493 ms 202.230.232.240
17 2026-08-26 05:14 639233172074181051
478 ms 202.230.232.240
16 2026-08-26 04:57 639233161808421455
603 ms 202.230.232.240
15 2026-08-26 04:40 639233151357344052
605 ms 202.230.232.240
14 2026-08-26 04:23 639233141034116946
495 ms 202.230.232.240
13 2026-08-26 04:05 639233130828334142
780 ms 202.230.232.240
12 2026-08-26 03:48 639233120373450007
773 ms 202.230.232.240
11 2026-08-26 03:31 639233110066216193
497 ms 202.230.232.240
10 2026-08-26 02:38 639233078065410564
781 ms 202.230.232.240
9 2026-08-26 02:21 639233067787457832
488 ms 202.230.232.240
8 2026-08-26 02:03 639233057501801162
506 ms 202.230.232.240
7 2026-08-26 01:46 639233047089431703
516 ms 202.230.232.240
6 2026-08-26 01:29 639233036754790688
489 ms 202.230.232.240
5 2026-08-26 01:12 639233026412602472
490 ms 202.230.232.240
4 2026-08-26 00:54 639233016064066127
501 ms 202.230.232.240
3 2026-08-26 00:37 639233005922655772
1035 ms 202.230.232.240
2 2026-08-26 00:20 639232995672256907
481 ms 202.230.232.240
1 2026-08-26 00:03 639232985300872416
497 ms 202.230.232.240