DNS response history for cs365.xbit.jp

cs365.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 36 DNS check records, 36 successful responses, 0 failed responses, and 444 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 cs365.xbit.jp.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

444 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:55

All timestamps shown in UTC

Latest Resolved IP on Selected Date

59.106.59.205

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 cs365.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
36 2026-08-26 11:55 639233414056832719
284 ms 59.106.59.205
35 2026-08-26 11:38 639233403515141099
2260 ms 59.106.59.205
34 2026-08-26 10:43 639233370841350248
281 ms 59.106.59.205
33 2026-08-26 10:26 639233360361507238
274 ms 59.106.59.205
32 2026-08-26 10:09 639233350067824371
278 ms 59.106.59.205
31 2026-08-26 09:51 639233339545274518
289 ms 59.106.59.205
30 2026-08-26 09:34 639233329214918079
280 ms 59.106.59.205
29 2026-08-26 09:17 639233318749762337
294 ms 59.106.59.205
28 2026-08-26 08:59 639233308387917838
280 ms 59.106.59.205
27 2026-08-26 08:42 639233297961740122
281 ms 59.106.59.205
26 2026-08-26 08:24 639233287487159094
286 ms 59.106.59.205
25 2026-08-26 08:07 639233276995531707
279 ms 59.106.59.205
24 2026-08-26 07:49 639233266521568229
282 ms 59.106.59.205
23 2026-08-26 07:32 639233256081047431
270 ms 59.106.59.205
22 2026-08-26 06:38 639233223620132921
280 ms 59.106.59.205
21 2026-08-26 06:21 639233213287814244
285 ms 59.106.59.205
20 2026-08-26 06:03 639233202925983161
278 ms 59.106.59.205
19 2026-08-26 05:46 639233192644780696
281 ms 59.106.59.205
18 2026-08-26 05:29 639233182401183833
2280 ms 59.106.59.205
17 2026-08-26 05:12 639233172074181051
288 ms 59.106.59.205
16 2026-08-26 04:55 639233161808421455
275 ms 59.106.59.205
15 2026-08-26 04:38 639233151357344052
274 ms 59.106.59.205
14 2026-08-26 04:20 639233141034116946
283 ms 59.106.59.205
13 2026-08-26 04:03 639233130828334142
2243 ms 59.106.59.205
12 2026-08-26 03:46 639233120373450007
279 ms 59.106.59.205
11 2026-08-26 03:29 639233110066216193
273 ms 59.106.59.205
10 2026-08-26 02:35 639233078065410564
262 ms 59.106.59.205
9 2026-08-26 02:18 639233067787457832
271 ms 59.106.59.205
8 2026-08-26 02:01 639233057501801162
267 ms 59.106.59.205
7 2026-08-26 01:44 639233047089431703
272 ms 59.106.59.205
6 2026-08-26 01:26 639233036754790688
274 ms 59.106.59.205
5 2026-08-26 01:09 639233026412602472
273 ms 59.106.59.205
4 2026-08-26 00:52 639233016064066127
279 ms 59.106.59.205
3 2026-08-26 00:35 639233005922655772
282 ms 59.106.59.205
2 2026-08-26 00:18 639232995672256907
284 ms 59.106.59.205
1 2026-08-26 00:01 639232985300872416
271 ms 59.106.59.205