DNS response history for ns02.xbit.jp

ns02.xbit.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-24. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 479 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 ns02.xbit.jp.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

479 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

59.106.35.117

Most recently resolved hosting IP on selected date

Successful Responses

28

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 ns02.xbit.jp

Showing DNS history for 2026-08-24 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
28 2026-08-24 11:52 639231683712487276
279 ms 59.106.35.117
27 2026-08-24 11:35 639231673513573868
289 ms 59.106.35.117
26 2026-08-24 10:42 639231641791249939
266 ms 59.106.35.117
25 2026-08-24 10:25 639231631866211033
261 ms 59.106.35.117
24 2026-08-24 10:08 639231621644955316
278 ms 59.106.35.117
23 2026-08-24 09:51 639231611478799259
284 ms 59.106.35.117
22 2026-08-24 08:59 639231579923718211
278 ms 59.106.35.117
21 2026-08-24 08:42 639231569810702936
268 ms 59.106.35.117
20 2026-08-24 08:25 639231559762411619
264 ms 59.106.35.117
19 2026-08-24 08:08 639231549663595407
273 ms 59.106.35.117
18 2026-08-24 07:16 639231518076817246
273 ms 59.106.35.117
17 2026-08-24 06:59 639231508078650885
284 ms 59.106.35.117
16 2026-08-24 06:42 639231498210697093
289 ms 59.106.35.117
15 2026-08-24 06:26 639231488109699360
291 ms 59.106.35.117
14 2026-08-24 05:34 639231456772510692
276 ms 59.106.35.117
13 2026-08-24 05:17 639231447084631185
282 ms 59.106.35.117
12 2026-08-24 05:01 639231437208519473
265 ms 59.106.35.117
11 2026-08-24 04:44 639231427209627490
272 ms 59.106.35.117
10 2026-08-24 03:52 639231395791246644
271 ms 59.106.35.117
9 2026-08-24 03:36 639231386075551458
2021 ms 59.106.35.117
8 2026-08-24 03:19 639231376208713791
286 ms 59.106.35.117
7 2026-08-24 03:03 639231366170589276
532 ms 59.106.35.117
6 2026-08-24 02:10 639231334732159368
256 ms 59.106.35.117
5 2026-08-24 01:54 639231325035670078
245 ms 59.106.35.117
4 2026-08-24 01:37 639231315132253837
273 ms 59.106.35.117
3 2026-08-24 01:21 639231305014280808
2296 ms 59.106.35.117
2 2026-08-24 00:28 639231273779380675
249 ms 59.106.35.117
1 2026-08-24 00:12 639231264180839154
2021 ms 59.106.35.117