DNS response history for ns2.dc1.jp

ns2.dc1.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 347 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.dc1.jp.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

347 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

168.119.140.25

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 ns2.dc1.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:17 639232566381512620
596 ms 168.119.140.25
34 2026-08-25 12:00 639232556111768563
2168 ms 168.119.140.25
33 2026-08-25 11:43 639232545839529039
519 ms 168.119.140.25
32 2026-08-25 11:25 639232535349285207
100 ms 168.119.140.25
31 2026-08-25 11:08 639232524938080723
53 ms 168.119.140.25
30 2026-08-25 10:14 639232492740373468
424 ms 168.119.140.25
29 2026-08-25 09:57 639232482235303141
244 ms 168.119.140.25
28 2026-08-25 09:39 639232471861770303
56 ms 168.119.140.25
27 2026-08-25 09:22 639232461630217327
286 ms 168.119.140.25
26 2026-08-25 09:05 639232451282965990
26 ms 168.119.140.25
25 2026-08-25 08:48 639232440814614938
39 ms 168.119.140.25
24 2026-08-25 08:30 639232430410720425
338 ms 168.119.140.25
23 2026-08-25 08:13 639232420003096185
344 ms 168.119.140.25
22 2026-08-25 07:55 639232409467287444
15 ms 168.119.140.25
21 2026-08-25 07:38 639232399077195997
15 ms 168.119.140.25
20 2026-08-25 07:21 639232388731528337
31 ms 168.119.140.25
19 2026-08-25 07:03 639232378288598612
39 ms 168.119.140.25
18 2026-08-25 06:10 639232346196373643
2191 ms 168.119.140.25
17 2026-08-25 05:53 639232336112370741
42 ms 168.119.140.25
16 2026-08-25 05:36 639232326146508970
30 ms 168.119.140.25
15 2026-08-25 05:20 639232316189381720
44 ms 168.119.140.25
14 2026-08-25 05:03 639232306217998913
192 ms 168.119.140.25
13 2026-08-25 04:47 639232296255744174
273 ms 168.119.140.25
12 2026-08-25 04:30 639232286095760789
296 ms 168.119.140.25
11 2026-08-25 04:13 639232276086186273
288 ms 168.119.140.25
10 2026-08-25 03:56 639232265900986425
305 ms 168.119.140.25
9 2026-08-25 03:39 639232255723518075
186 ms 168.119.140.25
8 2026-08-25 03:22 639232245484452890
32 ms 168.119.140.25
7 2026-08-25 03:05 639232235157175331
23 ms 168.119.140.25
6 2026-08-25 02:12 639232203197189095
2266 ms 168.119.140.25
5 2026-08-25 01:54 639232192844564298
14 ms 168.119.140.25
4 2026-08-25 01:37 639232182496008942
321 ms 168.119.140.25
3 2026-08-25 01:20 639232172197053132
31 ms 168.119.140.25
2 2026-08-25 00:27 639232140250307418
31 ms 168.119.140.25
1 2026-08-25 00:09 639232129927860324
281 ms 168.119.140.25