DNS response history for cs362.xbit.jp

cs362.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-26. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 353 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 cs362.xbit.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

353 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

59.106.35.118

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 cs362.xbit.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
30 2026-08-26 09:34 639233329214918079
243 ms 59.106.35.118
29 2026-08-26 09:17 639233318749762337
265 ms 59.106.35.118
28 2026-08-26 09:00 639233308387917838
274 ms 59.106.35.118
27 2026-08-26 08:43 639233297961740122
276 ms 59.106.35.118
26 2026-08-26 08:25 639233287487159094
285 ms 59.106.35.118
25 2026-08-26 08:08 639233276995531707
283 ms 59.106.35.118
24 2026-08-26 07:50 639233266521568229
497 ms 59.106.35.118
23 2026-08-26 07:33 639233256081047431
274 ms 59.106.35.118
22 2026-08-26 06:39 639233223620132921
288 ms 59.106.35.118
21 2026-08-26 06:21 639233213287814244
264 ms 59.106.35.118
20 2026-08-26 06:04 639233202925983161
277 ms 59.106.35.118
19 2026-08-26 05:47 639233192644780696
274 ms 59.106.35.118
18 2026-08-26 05:30 639233182401183833
283 ms 59.106.35.118
17 2026-08-26 05:13 639233172074181051
273 ms 59.106.35.118
16 2026-08-26 04:55 639233161808421455
271 ms 59.106.35.118
15 2026-08-26 04:38 639233151357344052
286 ms 59.106.35.118
14 2026-08-26 04:21 639233141034116946
274 ms 59.106.35.118
13 2026-08-26 04:04 639233130828334142
275 ms 59.106.35.118
12 2026-08-26 03:47 639233120373450007
281 ms 59.106.35.118
11 2026-08-26 03:29 639233110066216193
280 ms 59.106.35.118
10 2026-08-26 02:36 639233078065410564
246 ms 59.106.35.118
9 2026-08-26 02:19 639233067787457832
249 ms 59.106.35.118
8 2026-08-26 02:02 639233057501801162
265 ms 59.106.35.118
7 2026-08-26 01:45 639233047089431703
283 ms 59.106.35.118
6 2026-08-26 01:27 639233036754790688
268 ms 59.106.35.118
5 2026-08-26 01:10 639233026412602472
264 ms 59.106.35.118
4 2026-08-26 00:53 639233016064066127
286 ms 59.106.35.118
3 2026-08-26 00:36 639233005922655772
413 ms 59.106.35.118
2 2026-08-26 00:19 639232995672256907
260 ms 59.106.35.118
1 2026-08-26 00:01 639232985300872416
2320 ms 59.106.35.118