DNS response history for ns02.dswks.jp

ns02.dswks.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 30 DNS check records, 30 successful responses, 0 failed responses, and 503 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 ns02.dswks.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

503 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.129.12.184

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns02.dswks.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
30 2026-08-25 10:05 639232482235303141
500 ms 210.129.12.184
29 2026-08-25 09:47 639232471861770303
490 ms 210.129.12.184
28 2026-08-25 09:30 639232461630217327
517 ms 210.129.12.184
27 2026-08-25 09:13 639232451282965990
511 ms 210.129.12.184
26 2026-08-25 08:55 639232440814614938
503 ms 210.129.12.184
25 2026-08-25 08:38 639232430410720425
505 ms 210.129.12.184
24 2026-08-25 08:21 639232420003096185
530 ms 210.129.12.184
23 2026-08-25 08:03 639232409467287444
512 ms 210.129.12.184
22 2026-08-25 07:46 639232399077195997
516 ms 210.129.12.184
21 2026-08-25 07:28 639232388731528337
515 ms 210.129.12.184
20 2026-08-25 07:11 639232378288598612
528 ms 210.129.12.184
19 2026-08-25 06:17 639232346196373643
522 ms 210.129.12.184
18 2026-08-25 06:00 639232336112370741
505 ms 210.129.12.184
17 2026-08-25 05:44 639232326146508970
523 ms 210.129.12.184
16 2026-08-25 05:27 639232316189381720
520 ms 210.129.12.184
15 2026-08-25 05:11 639232306217998913
272 ms 210.129.12.184
14 2026-08-25 04:54 639232296255744174
492 ms 210.129.12.184
13 2026-08-25 04:37 639232286095760789
502 ms 210.129.12.184
12 2026-08-25 04:20 639232276086186273
509 ms 210.129.12.184
11 2026-08-25 04:03 639232265900986425
507 ms 210.129.12.184
10 2026-08-25 03:47 639232255723518075
539 ms 210.129.12.184
9 2026-08-25 03:29 639232245484452890
518 ms 210.129.12.184
8 2026-08-25 03:12 639232235157175331
511 ms 210.129.12.184
7 2026-08-25 02:19 639232203197189095
497 ms 210.129.12.184
6 2026-08-25 02:02 639232192844564298
495 ms 210.129.12.184
5 2026-08-25 01:45 639232182496008942
496 ms 210.129.12.184
4 2026-08-25 01:27 639232172197053132
505 ms 210.129.12.184
3 2026-08-25 00:34 639232140250307418
495 ms 210.129.12.184
2 2026-08-25 00:17 639232129927860324
539 ms 210.129.12.184
1 2026-08-25 00:00 639232119551972438
515 ms 210.129.12.184