DNS response history for ns02.futureweb.jp

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

29

Historical checks stored for this nameserver on selected date

Average Latency

1055 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

219.99.166.51

Most recently resolved hosting IP on selected date

Successful Responses

29

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.futureweb.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
29 2026-08-25 09:48 639232471861770303
1130 ms 219.99.166.51
28 2026-08-25 09:31 639232461630217327
1122 ms 219.99.166.51
27 2026-08-25 09:14 639232451282965990
2264 ms 219.99.166.51
26 2026-08-25 08:57 639232440814614938
1122 ms 219.99.166.51
25 2026-08-25 08:39 639232430410720425
1142 ms 219.99.166.51
24 2026-08-25 08:22 639232420003096185
1111 ms 219.99.166.51
23 2026-08-25 08:04 639232409467287444
1124 ms 219.99.166.51
22 2026-08-25 07:47 639232399077195997
1136 ms 219.99.166.51
21 2026-08-25 07:29 639232388731528337
568 ms 219.99.166.51
20 2026-08-25 07:12 639232378288598612
840 ms 219.99.166.51
19 2026-08-25 06:18 639232346196373643
565 ms 219.99.166.51
18 2026-08-25 06:01 639232336112370741
536 ms 219.99.166.51
17 2026-08-25 05:45 639232326146508970
869 ms 219.99.166.51
16 2026-08-25 05:28 639232316189381720
1105 ms 219.99.166.51
15 2026-08-25 05:12 639232306217998913
838 ms 219.99.166.51
14 2026-08-25 04:55 639232296255744174
1117 ms 219.99.166.51
13 2026-08-25 04:38 639232286095760789
1113 ms 219.99.166.51
12 2026-08-25 04:21 639232276086186273
1128 ms 219.99.166.51
11 2026-08-25 04:05 639232265900986425
1097 ms 219.99.166.51
10 2026-08-25 03:48 639232255723518075
1119 ms 219.99.166.51
9 2026-08-25 03:31 639232245484452890
1125 ms 219.99.166.51
8 2026-08-25 03:14 639232235157175331
1155 ms 219.99.166.51
7 2026-08-25 02:20 639232203197189095
1105 ms 219.99.166.51
6 2026-08-25 02:03 639232192844564298
1126 ms 219.99.166.51
5 2026-08-25 01:46 639232182496008942
565 ms 219.99.166.51
4 2026-08-25 01:29 639232172197053132
1109 ms 219.99.166.51
3 2026-08-25 00:35 639232140250307418
1106 ms 219.99.166.51
2 2026-08-25 00:18 639232129927860324
1109 ms 219.99.166.51
1 2026-08-25 00:01 639232119551972438
1142 ms 219.99.166.51