DNS response history for ns202.3-8.jp

ns202.3-8.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-24. For this date, NameServerHistory found 30 DNS check records, 29 successful responses, 1 failed responses, and 139 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 ns202.3-8.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

139 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

133.117.155.145

Most recently resolved hosting IP on selected date

Successful Responses

29

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns202.3-8.jp

Showing DNS history for 2026-08-24 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
30 2026-08-24 12:24 639231703815441688
292 ms 133.117.155.145
29 2026-08-24 12:07 639231693747052549
28 ms 133.117.155.145
28 2026-08-24 11:51 639231683712487276
11 ms 133.117.155.145
27 2026-08-24 11:34 639231673513573868
271 ms 133.117.155.145
26 2026-08-24 10:41 639231641791249939
296 ms 133.117.155.145
25 2026-08-24 10:24 639231631866211033
-
24 2026-08-24 10:07 639231621644955316
297 ms 133.117.155.145
23 2026-08-24 09:50 639231611478799259
281 ms 133.117.155.145
22 2026-08-24 08:58 639231579923718211
17 ms 133.117.155.145
21 2026-08-24 08:41 639231569810702936
298 ms 133.117.155.145
20 2026-08-24 08:24 639231559762411619
306 ms 133.117.155.145
19 2026-08-24 08:07 639231549663595407
23 ms 133.117.155.145
18 2026-08-24 07:15 639231518076817246
257 ms 133.117.155.145
17 2026-08-24 06:58 639231508078650885
11 ms 133.117.155.145
16 2026-08-24 06:41 639231498210697093
289 ms 133.117.155.145
15 2026-08-24 06:25 639231488109699360
17 ms 133.117.155.145
14 2026-08-24 05:32 639231456772510692
31 ms 133.117.155.145
13 2026-08-24 05:16 639231447084631185
300 ms 133.117.155.145
12 2026-08-24 05:00 639231437208519473
30 ms 133.117.155.145
11 2026-08-24 04:43 639231427209627490
7 ms 133.117.155.145
10 2026-08-24 03:51 639231395791246644
18 ms 133.117.155.145
9 2026-08-24 03:34 639231386075551458
295 ms 133.117.155.145
8 2026-08-24 03:18 639231376208713791
18 ms 133.117.155.145
7 2026-08-24 03:01 639231366170589276
9 ms 133.117.155.145
6 2026-08-24 02:09 639231334732159368
8 ms 133.117.155.145
5 2026-08-24 01:53 639231325035670078
285 ms 133.117.155.145
4 2026-08-24 01:36 639231315132253837
25 ms 133.117.155.145
3 2026-08-24 01:20 639231305014280808
294 ms 133.117.155.145
2 2026-08-24 00:27 639231273779380675
7 ms 133.117.155.145
1 2026-08-24 00:11 639231264180839154
12 ms 133.117.155.145