DNS response history for ns1.900.jp

ns1.900.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 588 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.900.jp.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

588 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

210.171.141.60

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.900.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 10:21 639232492740373468
508 ms 210.171.141.60
30 2026-08-25 10:04 639232482235303141
234 ms 210.171.141.60
29 2026-08-25 09:47 639232471861770303
470 ms 210.171.141.60
28 2026-08-25 09:30 639232461630217327
234 ms 210.171.141.60
27 2026-08-25 09:12 639232451282965990
4250 ms 210.171.141.60
26 2026-08-25 08:55 639232440814614938
471 ms 210.171.141.60
25 2026-08-25 08:38 639232430410720425
490 ms 210.171.141.60
24 2026-08-25 08:20 639232420003096185
463 ms 210.171.141.60
23 2026-08-25 08:03 639232409467287444
233 ms 210.171.141.60
22 2026-08-25 07:45 639232399077195997
484 ms 210.171.141.60
21 2026-08-25 07:28 639232388731528337
235 ms 210.171.141.60
20 2026-08-25 07:11 639232378288598612
468 ms 210.171.141.60
19 2026-08-25 06:17 639232346196373643
472 ms 210.171.141.60
18 2026-08-25 06:00 639232336112370741
469 ms 210.171.141.60
17 2026-08-25 05:43 639232326146508970
255 ms 210.171.141.60
16 2026-08-25 05:27 639232316189381720
468 ms 210.171.141.60
15 2026-08-25 05:10 639232306217998913
246 ms 210.171.141.60
14 2026-08-25 04:54 639232296255744174
467 ms 210.171.141.60
13 2026-08-25 04:37 639232286095760789
462 ms 210.171.141.60
12 2026-08-25 04:20 639232276086186273
233 ms 210.171.141.60
11 2026-08-25 04:03 639232265900986425
482 ms 210.171.141.60
10 2026-08-25 03:46 639232255723518075
775 ms 210.171.141.60
9 2026-08-25 03:29 639232245484452890
467 ms 210.171.141.60
8 2026-08-25 03:12 639232235157175331
273 ms 210.171.141.60
7 2026-08-25 02:19 639232203197189095
468 ms 210.171.141.60
6 2026-08-25 02:02 639232192844564298
233 ms 210.171.141.60
5 2026-08-25 01:44 639232182496008942
468 ms 210.171.141.60
4 2026-08-25 01:27 639232172197053132
467 ms 210.171.141.60
3 2026-08-25 00:34 639232140250307418
468 ms 210.171.141.60
2 2026-08-25 00:17 639232129927860324
233 ms 210.171.141.60
1 2026-08-25 00:00 639232119551972438
2291 ms 210.171.141.60