DNS response history for ns3.incl.ne.jp

ns3.incl.ne.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 32 DNS check records, 32 successful responses, 0 failed responses, and 428 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 ns3.incl.ne.jp.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

428 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.239.85.155

Most recently resolved hosting IP on selected date

Successful Responses

32

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 ns3.incl.ne.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
32 2026-08-25 11:15 639232524938080723
271 ms 210.239.85.155
31 2026-08-25 10:22 639232492740373468
569 ms 210.239.85.155
30 2026-08-25 10:04 639232482235303141
590 ms 210.239.85.155
29 2026-08-25 09:47 639232471861770303
575 ms 210.239.85.155
28 2026-08-25 09:30 639232461630217327
568 ms 210.239.85.155
27 2026-08-25 09:12 639232451282965990
3 ms 210.239.85.155
26 2026-08-25 08:55 639232440814614938
273 ms 210.239.85.155
25 2026-08-25 08:38 639232430410720425
5 ms 210.239.85.155
24 2026-08-25 08:20 639232420003096185
826 ms 210.239.85.155
23 2026-08-25 08:03 639232409467287444
565 ms 210.239.85.155
22 2026-08-25 07:46 639232399077195997
550 ms 210.239.85.155
21 2026-08-25 07:28 639232388731528337
534 ms 210.239.85.155
20 2026-08-25 07:11 639232378288598612
264 ms 210.239.85.155
19 2026-08-25 06:17 639232346196373643
8 ms 210.239.85.155
18 2026-08-25 06:00 639232336112370741
554 ms 210.239.85.155
17 2026-08-25 05:44 639232326146508970
263 ms 210.239.85.155
16 2026-08-25 05:27 639232316189381720
521 ms 210.239.85.155
15 2026-08-25 05:10 639232306217998913
276 ms 210.239.85.155
14 2026-08-25 04:54 639232296255744174
265 ms 210.239.85.155
13 2026-08-25 04:37 639232286095760789
3 ms 210.239.85.155
12 2026-08-25 04:20 639232276086186273
545 ms 210.239.85.155
11 2026-08-25 04:03 639232265900986425
258 ms 210.239.85.155
10 2026-08-25 03:46 639232255723518075
529 ms 210.239.85.155
9 2026-08-25 03:29 639232245484452890
548 ms 210.239.85.155
8 2026-08-25 03:12 639232235157175331
548 ms 210.239.85.155
7 2026-08-25 02:19 639232203197189095
534 ms 210.239.85.155
6 2026-08-25 02:02 639232192844564298
534 ms 210.239.85.155
5 2026-08-25 01:45 639232182496008942
572 ms 210.239.85.155
4 2026-08-25 01:27 639232172197053132
527 ms 210.239.85.155
3 2026-08-25 00:34 639232140250307418
524 ms 210.239.85.155
2 2026-08-25 00:17 639232129927860324
538 ms 210.239.85.155
1 2026-08-25 00:00 639232119551972438
564 ms 210.239.85.155