DNS response history for ns3.ingnet.ne.jp

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

35

Historical checks stored for this nameserver on selected date

Average Latency

518 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.43.105.50

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 ns3.ingnet.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
35 2026-08-25 12:24 639232566381512620
520 ms 162.43.105.50
34 2026-08-25 12:07 639232556111768563
493 ms 162.43.105.50
33 2026-08-25 11:50 639232545839529039
484 ms 162.43.105.50
32 2026-08-25 11:32 639232535349285207
504 ms 162.43.105.50
31 2026-08-25 11:15 639232524938080723
497 ms 162.43.105.50
30 2026-08-25 10:21 639232492740373468
489 ms 162.43.105.50
29 2026-08-25 10:04 639232482235303141
500 ms 162.43.105.50
28 2026-08-25 09:46 639232471861770303
5 ms 162.43.105.50
27 2026-08-25 09:29 639232461630217327
499 ms 162.43.105.50
26 2026-08-25 09:12 639232451282965990
484 ms 162.43.105.50
25 2026-08-25 08:55 639232440814614938
498 ms 162.43.105.50
24 2026-08-25 08:37 639232430410720425
3 ms 162.43.105.50
23 2026-08-25 08:20 639232420003096185
482 ms 162.43.105.50
22 2026-08-25 08:03 639232409467287444
501 ms 162.43.105.50
21 2026-08-25 07:45 639232399077195997
480 ms 162.43.105.50
20 2026-08-25 07:28 639232388731528337
2240 ms 162.43.105.50
19 2026-08-25 07:10 639232378288598612
612 ms 162.43.105.50
18 2026-08-25 06:17 639232346196373643
505 ms 162.43.105.50
17 2026-08-25 06:00 639232336112370741
4 ms 162.43.105.50
16 2026-08-25 05:43 639232326146508970
504 ms 162.43.105.50
15 2026-08-25 05:27 639232316189381720
768 ms 162.43.105.50
14 2026-08-25 05:10 639232306217998913
273 ms 162.43.105.50
13 2026-08-25 04:53 639232296255744174
480 ms 162.43.105.50
12 2026-08-25 04:37 639232286095760789
491 ms 162.43.105.50
11 2026-08-25 04:20 639232276086186273
511 ms 162.43.105.50
10 2026-08-25 04:03 639232265900986425
475 ms 162.43.105.50
9 2026-08-25 03:46 639232255723518075
500 ms 162.43.105.50
8 2026-08-25 03:29 639232245484452890
790 ms 162.43.105.50
7 2026-08-25 03:12 639232235157175331
518 ms 162.43.105.50
6 2026-08-25 02:18 639232203197189095
548 ms 162.43.105.50
5 2026-08-25 02:01 639232192844564298
485 ms 162.43.105.50
4 2026-08-25 01:44 639232182496008942
482 ms 162.43.105.50
3 2026-08-25 01:27 639232172197053132
492 ms 162.43.105.50
2 2026-08-25 00:33 639232140250307418
508 ms 162.43.105.50
1 2026-08-25 00:17 639232129927860324
501 ms 162.43.105.50