DNS response history for ns01.xaas3.jp

ns01.xaas3.jp 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 38 DNS check records, 38 successful responses, 0 failed responses, and 536 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 ns01.xaas3.jp.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

536 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.129.8.104

Most recently resolved hosting IP on selected date

Successful Responses

38

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 ns01.xaas3.jp

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
38 2026-08-26 12:32 639233434974187439
514 ms 210.129.8.104
37 2026-08-26 12:14 639233424567558554
506 ms 210.129.8.104
36 2026-08-26 11:57 639233414056832719
493 ms 210.129.8.104
35 2026-08-26 11:39 639233403515141099
522 ms 210.129.8.104
34 2026-08-26 10:45 639233370841350248
512 ms 210.129.8.104
33 2026-08-26 10:27 639233360361507238
515 ms 210.129.8.104
32 2026-08-26 10:10 639233350067824371
504 ms 210.129.8.104
31 2026-08-26 09:53 639233339545274518
509 ms 210.129.8.104
30 2026-08-26 09:35 639233329214918079
495 ms 210.129.8.104
29 2026-08-26 09:18 639233318749762337
493 ms 210.129.8.104
28 2026-08-26 09:00 639233308387917838
517 ms 210.129.8.104
27 2026-08-26 08:43 639233297961740122
526 ms 210.129.8.104
26 2026-08-26 08:26 639233287487159094
644 ms 210.129.8.104
25 2026-08-26 08:08 639233276995531707
508 ms 210.129.8.104
24 2026-08-26 07:51 639233266521568229
504 ms 210.129.8.104
23 2026-08-26 07:33 639233256081047431
515 ms 210.129.8.104
22 2026-08-26 06:39 639233223620132921
518 ms 210.129.8.104
21 2026-08-26 06:22 639233213287814244
253 ms 210.129.8.104
20 2026-08-26 06:05 639233202925983161
504 ms 210.129.8.104
19 2026-08-26 05:48 639233192644780696
304 ms 210.129.8.104
18 2026-08-26 05:30 639233182401183833
503 ms 210.129.8.104
17 2026-08-26 05:13 639233172074181051
522 ms 210.129.8.104
16 2026-08-26 04:56 639233161808421455
307 ms 210.129.8.104
15 2026-08-26 04:39 639233151357344052
660 ms 210.129.8.104
14 2026-08-26 04:22 639233141034116946
515 ms 210.129.8.104
13 2026-08-26 04:04 639233130828334142
284 ms 210.129.8.104
12 2026-08-26 03:47 639233120373450007
519 ms 210.129.8.104
11 2026-08-26 03:30 639233110066216193
500 ms 210.129.8.104
10 2026-08-26 02:37 639233078065410564
259 ms 210.129.8.104
9 2026-08-26 02:20 639233067787457832
508 ms 210.129.8.104
8 2026-08-26 02:02 639233057501801162
533 ms 210.129.8.104
7 2026-08-26 01:45 639233047089431703
505 ms 210.129.8.104
6 2026-08-26 01:28 639233036754790688
532 ms 210.129.8.104
5 2026-08-26 01:11 639233026412602472
2560 ms 210.129.8.104
4 2026-08-26 00:53 639233016064066127
257 ms 210.129.8.104
3 2026-08-26 00:36 639233005922655772
505 ms 210.129.8.104
2 2026-08-26 00:19 639232995672256907
525 ms 210.129.8.104
1 2026-08-26 00:02 639232985300872416
512 ms 210.129.8.104