DNS response history for ts002.hit.ac.jp

ts002.hit.ac.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 35 DNS check records, 35 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 ts002.hit.ac.jp.
Records on Selected Date

35

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:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.255.192.2

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ts002.hit.ac.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
35 2026-08-26 11:42 639233403515141099
567 ms 202.255.192.2
34 2026-08-26 10:47 639233370841350248
389 ms 202.255.192.2
33 2026-08-26 10:30 639233360361507238
551 ms 202.255.192.2
32 2026-08-26 10:12 639233350067824371
312 ms 202.255.192.2
31 2026-08-26 09:55 639233339545274518
292 ms 202.255.192.2
30 2026-08-26 09:38 639233329214918079
305 ms 202.255.192.2
29 2026-08-26 09:20 639233318749762337
566 ms 202.255.192.2
28 2026-08-26 09:03 639233308387917838
304 ms 202.255.192.2
27 2026-08-26 08:46 639233297961740122
594 ms 202.255.192.2
26 2026-08-26 08:28 639233287487159094
586 ms 202.255.192.2
25 2026-08-26 08:11 639233276995531707
581 ms 202.255.192.2
24 2026-08-26 07:53 639233266521568229
606 ms 202.255.192.2
23 2026-08-26 07:36 639233256081047431
310 ms 202.255.192.2
22 2026-08-26 06:42 639233223620132921
598 ms 202.255.192.2
21 2026-08-26 06:24 639233213287814244
319 ms 202.255.192.2
20 2026-08-26 06:07 639233202925983161
294 ms 202.255.192.2
19 2026-08-26 05:50 639233192644780696
587 ms 202.255.192.2
18 2026-08-26 05:33 639233182401183833
301 ms 202.255.192.2
17 2026-08-26 05:16 639233172074181051
313 ms 202.255.192.2
16 2026-08-26 04:58 639233161808421455
301 ms 202.255.192.2
15 2026-08-26 04:41 639233151357344052
358 ms 202.255.192.2
14 2026-08-26 04:24 639233141034116946
592 ms 202.255.192.2
13 2026-08-26 04:07 639233130828334142
290 ms 202.255.192.2
12 2026-08-26 03:50 639233120373450007
588 ms 202.255.192.2
11 2026-08-26 03:32 639233110066216193
290 ms 202.255.192.2
10 2026-08-26 02:39 639233078065410564
559 ms 202.255.192.2
9 2026-08-26 02:22 639233067787457832
544 ms 202.255.192.2
8 2026-08-26 02:05 639233057501801162
567 ms 202.255.192.2
7 2026-08-26 01:48 639233047089431703
656 ms 202.255.192.2
6 2026-08-26 01:30 639233036754790688
293 ms 202.255.192.2
5 2026-08-26 01:13 639233026412602472
293 ms 202.255.192.2
4 2026-08-26 00:56 639233016064066127
573 ms 202.255.192.2
3 2026-08-26 00:39 639233005922655772
564 ms 202.255.192.2
2 2026-08-26 00:22 639232995672256907
562 ms 202.255.192.2
1 2026-08-26 00:04 639232985300872416
305 ms 202.255.192.2