DNS response history for cs260.xbit.jp

cs260.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 449 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 cs260.xbit.jp.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

449 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

59.106.166.170

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 cs260.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:56 639233414056832719
276 ms 59.106.166.170
35 2026-08-26 11:38 639233403515141099
405 ms 59.106.166.170
34 2026-08-26 10:43 639233370841350248
255 ms 59.106.166.170
33 2026-08-26 10:26 639233360361507238
2378 ms 59.106.166.170
32 2026-08-26 10:09 639233350067824371
307 ms 59.106.166.170
31 2026-08-26 09:52 639233339545274518
275 ms 59.106.166.170
30 2026-08-26 09:34 639233329214918079
253 ms 59.106.166.170
29 2026-08-26 09:17 639233318749762337
268 ms 59.106.166.170
28 2026-08-26 08:59 639233308387917838
274 ms 59.106.166.170
27 2026-08-26 08:42 639233297961740122
281 ms 59.106.166.170
26 2026-08-26 08:25 639233287487159094
277 ms 59.106.166.170
25 2026-08-26 08:07 639233276995531707
298 ms 59.106.166.170
24 2026-08-26 07:50 639233266521568229
278 ms 59.106.166.170
23 2026-08-26 07:32 639233256081047431
281 ms 59.106.166.170
22 2026-08-26 06:38 639233223620132921
275 ms 59.106.166.170
21 2026-08-26 06:21 639233213287814244
293 ms 59.106.166.170
20 2026-08-26 06:04 639233202925983161
286 ms 59.106.166.170
19 2026-08-26 05:46 639233192644780696
289 ms 59.106.166.170
18 2026-08-26 05:29 639233182401183833
278 ms 59.106.166.170
17 2026-08-26 05:12 639233172074181051
279 ms 59.106.166.170
16 2026-08-26 04:55 639233161808421455
2275 ms 59.106.166.170
15 2026-08-26 04:38 639233151357344052
279 ms 59.106.166.170
14 2026-08-26 04:20 639233141034116946
282 ms 59.106.166.170
13 2026-08-26 04:03 639233130828334142
278 ms 59.106.166.170
12 2026-08-26 03:46 639233120373450007
298 ms 59.106.166.170
11 2026-08-26 03:29 639233110066216193
276 ms 59.106.166.170
10 2026-08-26 02:36 639233078065410564
271 ms 59.106.166.170
9 2026-08-26 02:18 639233067787457832
2247 ms 59.106.166.170
8 2026-08-26 02:01 639233057501801162
265 ms 59.106.166.170
7 2026-08-26 01:44 639233047089431703
294 ms 59.106.166.170
6 2026-08-26 01:27 639233036754790688
243 ms 59.106.166.170
5 2026-08-26 01:10 639233026412602472
282 ms 59.106.166.170
4 2026-08-26 00:52 639233016064066127
275 ms 59.106.166.170
3 2026-08-26 00:35 639233005922655772
256 ms 59.106.166.170
2 2026-08-26 00:18 639232995672256907
273 ms 59.106.166.170
1 2026-08-26 00:01 639232985300872416
266 ms 59.106.166.170