DNS response history for ns2.dataworks.jp

ns2.dataworks.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 816 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.dataworks.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

816 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

160.16.111.203

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 ns2.dataworks.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:21 639232492740373468
285 ms 160.16.111.203
29 2026-08-25 10:04 639232482235303141
256 ms 160.16.111.203
28 2026-08-25 09:46 639232471861770303
272 ms 160.16.111.203
27 2026-08-25 09:29 639232461630217327
803 ms 160.16.111.203
26 2026-08-25 09:12 639232451282965990
268 ms 160.16.111.203
25 2026-08-25 08:55 639232440814614938
511 ms 160.16.111.203
24 2026-08-25 08:37 639232430410720425
259 ms 160.16.111.203
23 2026-08-25 08:20 639232420003096185
1729 ms 160.16.111.203
22 2026-08-25 08:02 639232409467287444
256 ms 160.16.111.203
21 2026-08-25 07:45 639232399077195997
303 ms 160.16.111.203
20 2026-08-25 07:28 639232388731528337
1960 ms 160.16.111.203
19 2026-08-25 07:10 639232378288598612
1943 ms 160.16.111.203
18 2026-08-25 06:17 639232346196373643
267 ms 160.16.111.203
17 2026-08-25 06:00 639232336112370741
2306 ms 160.16.111.203
16 2026-08-25 05:43 639232326146508970
1397 ms 160.16.111.203
15 2026-08-25 05:26 639232316189381720
3 ms 160.16.111.203
14 2026-08-25 05:10 639232306217998913
1499 ms 160.16.111.203
13 2026-08-25 04:53 639232296255744174
1753 ms 160.16.111.203
12 2026-08-25 04:36 639232286095760789
535 ms 160.16.111.203
11 2026-08-25 04:19 639232276086186273
558 ms 160.16.111.203
10 2026-08-25 04:03 639232265900986425
277 ms 160.16.111.203
9 2026-08-25 03:46 639232255723518075
565 ms 160.16.111.203
8 2026-08-25 03:29 639232245484452890
523 ms 160.16.111.203
7 2026-08-25 03:12 639232235157175331
1822 ms 160.16.111.203
6 2026-08-25 02:18 639232203197189095
2250 ms 160.16.111.203
5 2026-08-25 02:01 639232192844564298
273 ms 160.16.111.203
4 2026-08-25 01:44 639232182496008942
530 ms 160.16.111.203
3 2026-08-25 01:27 639232172197053132
269 ms 160.16.111.203
2 2026-08-25 00:33 639232140250307418
262 ms 160.16.111.203
1 2026-08-25 00:16 639232129927860324
542 ms 160.16.111.203