DNS response history for cs265.xbit.jp

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

31

Historical checks stored for this nameserver on selected date

Average Latency

495 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

59.106.61.108

Most recently resolved hosting IP on selected date

Successful Responses

31

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 cs265.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
31 2026-08-26 09:51 639233339545274518
264 ms 59.106.61.108
30 2026-08-26 09:34 639233329214918079
285 ms 59.106.61.108
29 2026-08-26 09:17 639233318749762337
2296 ms 59.106.61.108
28 2026-08-26 08:59 639233308387917838
590 ms 59.106.61.108
27 2026-08-26 08:42 639233297961740122
273 ms 59.106.61.108
26 2026-08-26 08:24 639233287487159094
370 ms 59.106.61.108
25 2026-08-26 08:07 639233276995531707
272 ms 59.106.61.108
24 2026-08-26 07:49 639233266521568229
289 ms 59.106.61.108
23 2026-08-26 07:32 639233256081047431
277 ms 59.106.61.108
22 2026-08-26 06:38 639233223620132921
282 ms 59.106.61.108
21 2026-08-26 06:21 639233213287814244
283 ms 59.106.61.108
20 2026-08-26 06:03 639233202925983161
280 ms 59.106.61.108
19 2026-08-26 05:46 639233192644780696
280 ms 59.106.61.108
18 2026-08-26 05:29 639233182401183833
279 ms 59.106.61.108
17 2026-08-26 05:12 639233172074181051
281 ms 59.106.61.108
16 2026-08-26 04:55 639233161808421455
554 ms 59.106.61.108
15 2026-08-26 04:38 639233151357344052
286 ms 59.106.61.108
14 2026-08-26 04:20 639233141034116946
274 ms 59.106.61.108
13 2026-08-26 04:03 639233130828334142
269 ms 59.106.61.108
12 2026-08-26 03:46 639233120373450007
2275 ms 59.106.61.108
11 2026-08-26 03:29 639233110066216193
276 ms 59.106.61.108
10 2026-08-26 02:35 639233078065410564
282 ms 59.106.61.108
9 2026-08-26 02:18 639233067787457832
336 ms 59.106.61.108
8 2026-08-26 02:01 639233057501801162
278 ms 59.106.61.108
7 2026-08-26 01:44 639233047089431703
283 ms 59.106.61.108
6 2026-08-26 01:27 639233036754790688
2271 ms 59.106.61.108
5 2026-08-26 01:09 639233026412602472
283 ms 59.106.61.108
4 2026-08-26 00:52 639233016064066127
272 ms 59.106.61.108
3 2026-08-26 00:35 639233005922655772
264 ms 59.106.61.108
2 2026-08-26 00:18 639232995672256907
264 ms 59.106.61.108
1 2026-08-26 00:01 639232985300872416
282 ms 59.106.61.108