DNS response history for cuns.chiba-u.jp

cuns.chiba-u.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 327 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 cuns.chiba-u.jp.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

327 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

220.156.10.185

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 cuns.chiba-u.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
279 ms 220.156.10.185
35 2026-08-26 11:39 639233403515141099
265 ms 220.156.10.185
34 2026-08-26 10:44 639233370841350248
273 ms 220.156.10.185
33 2026-08-26 10:27 639233360361507238
256 ms 220.156.10.185
32 2026-08-26 10:09 639233350067824371
560 ms 220.156.10.185
31 2026-08-26 09:52 639233339545274518
274 ms 220.156.10.185
30 2026-08-26 09:35 639233329214918079
528 ms 220.156.10.185
29 2026-08-26 09:18 639233318749762337
281 ms 220.156.10.185
28 2026-08-26 09:00 639233308387917838
273 ms 220.156.10.185
27 2026-08-26 08:43 639233297961740122
277 ms 220.156.10.185
26 2026-08-26 08:25 639233287487159094
272 ms 220.156.10.185
25 2026-08-26 08:08 639233276995531707
280 ms 220.156.10.185
24 2026-08-26 07:50 639233266521568229
275 ms 220.156.10.185
23 2026-08-26 07:33 639233256081047431
275 ms 220.156.10.185
22 2026-08-26 06:39 639233223620132921
282 ms 220.156.10.185
21 2026-08-26 06:22 639233213287814244
282 ms 220.156.10.185
20 2026-08-26 06:04 639233202925983161
282 ms 220.156.10.185
19 2026-08-26 05:47 639233192644780696
556 ms 220.156.10.185
18 2026-08-26 05:30 639233182401183833
286 ms 220.156.10.185
17 2026-08-26 05:13 639233172074181051
280 ms 220.156.10.185
16 2026-08-26 04:56 639233161808421455
276 ms 220.156.10.185
15 2026-08-26 04:39 639233151357344052
273 ms 220.156.10.185
14 2026-08-26 04:21 639233141034116946
562 ms 220.156.10.185
13 2026-08-26 04:04 639233130828334142
571 ms 220.156.10.185
12 2026-08-26 03:47 639233120373450007
283 ms 220.156.10.185
11 2026-08-26 03:29 639233110066216193
279 ms 220.156.10.185
10 2026-08-26 02:36 639233078065410564
257 ms 220.156.10.185
9 2026-08-26 02:19 639233067787457832
257 ms 220.156.10.185
8 2026-08-26 02:02 639233057501801162
267 ms 220.156.10.185
7 2026-08-26 01:45 639233047089431703
522 ms 220.156.10.185
6 2026-08-26 01:27 639233036754790688
278 ms 220.156.10.185
5 2026-08-26 01:10 639233026412602472
527 ms 220.156.10.185
4 2026-08-26 00:53 639233016064066127
268 ms 220.156.10.185
3 2026-08-26 00:36 639233005922655772
275 ms 220.156.10.185
2 2026-08-26 00:19 639232995672256907
263 ms 220.156.10.185
1 2026-08-26 00:02 639232985300872416
272 ms 220.156.10.185