DNS response history for ns2.inforent.jp

ns2.inforent.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-25. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 479 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 ns2.inforent.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

479 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.230.201.192

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns2.inforent.jp

Showing DNS history for 2026-08-25 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-25 10:21 639232492740373468
797 ms 202.230.201.192
29 2026-08-25 10:04 639232482235303141
506 ms 202.230.201.192
28 2026-08-25 09:46 639232471861770303
512 ms 202.230.201.192
27 2026-08-25 09:29 639232461630217327
510 ms 202.230.201.192
26 2026-08-25 09:12 639232451282965990
495 ms 202.230.201.192
25 2026-08-25 08:54 639232440814614938
517 ms 202.230.201.192
24 2026-08-25 08:37 639232430410720425
509 ms 202.230.201.192
23 2026-08-25 08:20 639232420003096185
505 ms 202.230.201.192
22 2026-08-25 08:02 639232409467287444
504 ms 202.230.201.192
21 2026-08-25 07:45 639232399077195997
520 ms 202.230.201.192
20 2026-08-25 07:27 639232388731528337
4 ms 202.230.201.192
19 2026-08-25 07:10 639232378288598612
503 ms 202.230.201.192
18 2026-08-25 06:16 639232346196373643
509 ms 202.230.201.192
17 2026-08-25 05:59 639232336112370741
511 ms 202.230.201.192
16 2026-08-25 05:43 639232326146508970
507 ms 202.230.201.192
15 2026-08-25 05:26 639232316189381720
524 ms 202.230.201.192
14 2026-08-25 05:10 639232306217998913
10 ms 202.230.201.192
13 2026-08-25 04:53 639232296255744174
511 ms 202.230.201.192
12 2026-08-25 04:36 639232286095760789
247 ms 202.230.201.192
11 2026-08-25 04:19 639232276086186273
518 ms 202.230.201.192
10 2026-08-25 04:03 639232265900986425
2278 ms 202.230.201.192
9 2026-08-25 03:46 639232255723518075
505 ms 202.230.201.192
8 2026-08-25 03:29 639232245484452890
3 ms 202.230.201.192
7 2026-08-25 03:11 639232235157175331
517 ms 202.230.201.192
6 2026-08-25 02:18 639232203197189095
3 ms 202.230.201.192
5 2026-08-25 02:01 639232192844564298
523 ms 202.230.201.192
4 2026-08-25 01:44 639232182496008942
517 ms 202.230.201.192
3 2026-08-25 01:26 639232172197053132
3 ms 202.230.201.192
2 2026-08-25 00:33 639232140250307418
509 ms 202.230.201.192
1 2026-08-25 00:16 639232129927860324
284 ms 202.230.201.192