DNS response history for fws102.wadax-sv.jp

fws102.wadax-sv.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 300 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 fws102.wadax-sv.jp.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

300 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.123.7.211

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 fws102.wadax-sv.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 11:12 639232524938080723
249 ms 153.123.7.211
30 2026-08-25 10:18 639232492740373468
60 ms 153.123.7.211
29 2026-08-25 10:01 639232482235303141
242 ms 153.123.7.211
28 2026-08-25 09:44 639232471861770303
242 ms 153.123.7.211
27 2026-08-25 09:27 639232461630217327
241 ms 153.123.7.211
26 2026-08-25 09:10 639232451282965990
2282 ms 153.123.7.211
25 2026-08-25 08:52 639232440814614938
246 ms 153.123.7.211
24 2026-08-25 08:35 639232430410720425
247 ms 153.123.7.211
23 2026-08-25 08:17 639232420003096185
253 ms 153.123.7.211
22 2026-08-25 08:00 639232409467287444
252 ms 153.123.7.211
21 2026-08-25 07:42 639232399077195997
242 ms 153.123.7.211
20 2026-08-25 07:25 639232388731528337
242 ms 153.123.7.211
19 2026-08-25 07:08 639232378288598612
240 ms 153.123.7.211
18 2026-08-25 06:14 639232346196373643
264 ms 153.123.7.211
17 2026-08-25 05:57 639232336112370741
4 ms 153.123.7.211
16 2026-08-25 05:41 639232326146508970
21 ms 153.123.7.211
15 2026-08-25 05:24 639232316189381720
243 ms 153.123.7.211
14 2026-08-25 05:08 639232306217998913
242 ms 153.123.7.211
13 2026-08-25 04:51 639232296255744174
493 ms 153.123.7.211
12 2026-08-25 04:34 639232286095760789
244 ms 153.123.7.211
11 2026-08-25 04:17 639232276086186273
248 ms 153.123.7.211
10 2026-08-25 04:00 639232265900986425
254 ms 153.123.7.211
9 2026-08-25 03:43 639232255723518075
251 ms 153.123.7.211
8 2026-08-25 03:26 639232245484452890
245 ms 153.123.7.211
7 2026-08-25 03:09 639232235157175331
246 ms 153.123.7.211
6 2026-08-25 02:16 639232203197189095
261 ms 153.123.7.211
5 2026-08-25 01:59 639232192844564298
247 ms 153.123.7.211
4 2026-08-25 01:42 639232182496008942
242 ms 153.123.7.211
3 2026-08-25 01:24 639232172197053132
245 ms 153.123.7.211
2 2026-08-25 00:31 639232140250307418
260 ms 153.123.7.211
1 2026-08-25 00:14 639232129927860324
251 ms 153.123.7.211