DNS response history for ns1.neweb.ne.jp

ns1.neweb.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 31 DNS check records, 31 successful responses, 0 failed responses, and 330 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 ns1.neweb.ne.jp.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

330 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.140.129.2

Most recently resolved hosting IP on selected date

Successful Responses

31

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 ns1.neweb.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
31 2026-08-25 11:14 639232524938080723
608 ms 203.140.129.2
30 2026-08-25 10:21 639232492740373468
605 ms 203.140.129.2
29 2026-08-25 10:03 639232482235303141
5 ms 203.140.129.2
28 2026-08-25 09:46 639232471861770303
587 ms 203.140.129.2
27 2026-08-25 09:29 639232461630217327
573 ms 203.140.129.2
26 2026-08-25 09:11 639232451282965990
5 ms 203.140.129.2
25 2026-08-25 08:54 639232440814614938
3 ms 203.140.129.2
24 2026-08-25 08:37 639232430410720425
552 ms 203.140.129.2
23 2026-08-25 08:19 639232420003096185
551 ms 203.140.129.2
22 2026-08-25 08:02 639232409467287444
621 ms 203.140.129.2
21 2026-08-25 07:45 639232399077195997
5 ms 203.140.129.2
20 2026-08-25 07:27 639232388731528337
558 ms 203.140.129.2
19 2026-08-25 07:10 639232378288598612
629 ms 203.140.129.2
18 2026-08-25 06:16 639232346196373643
4 ms 203.140.129.2
17 2026-08-25 05:59 639232336112370741
279 ms 203.140.129.2
16 2026-08-25 05:43 639232326146508970
581 ms 203.140.129.2
15 2026-08-25 05:26 639232316189381720
561 ms 203.140.129.2
14 2026-08-25 05:10 639232306217998913
561 ms 203.140.129.2
13 2026-08-25 04:53 639232296255744174
64 ms 203.140.129.2
12 2026-08-25 04:36 639232286095760789
3 ms 203.140.129.2
11 2026-08-25 04:19 639232276086186273
569 ms 203.140.129.2
10 2026-08-25 04:02 639232265900986425
559 ms 203.140.129.2
9 2026-08-25 03:46 639232255723518075
568 ms 203.140.129.2
8 2026-08-25 03:28 639232245484452890
10 ms 203.140.129.2
7 2026-08-25 03:11 639232235157175331
33 ms 203.140.129.2
6 2026-08-25 02:18 639232203197189095
543 ms 203.140.129.2
5 2026-08-25 02:01 639232192844564298
8 ms 203.140.129.2
4 2026-08-25 01:44 639232182496008942
567 ms 203.140.129.2
3 2026-08-25 01:26 639232172197053132
3 ms 203.140.129.2
2 2026-08-25 00:33 639232140250307418
17 ms 203.140.129.2
1 2026-08-25 00:16 639232129927860324
2 ms 203.140.129.2