DNS response history for ns2.wbh.jp

ns2.wbh.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 32 DNS check records, 32 successful responses, 0 failed responses, and 476 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.wbh.jp.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

476 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.121.58.112

Most recently resolved hosting IP on selected date

Successful Responses

32

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.wbh.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
32 2026-08-25 11:33 639232535349285207
578 ms 153.121.58.112
31 2026-08-25 11:15 639232524938080723
561 ms 153.121.58.112
30 2026-08-25 10:21 639232492740373468
547 ms 153.121.58.112
29 2026-08-25 10:04 639232482235303141
559 ms 153.121.58.112
28 2026-08-25 09:47 639232471861770303
555 ms 153.121.58.112
27 2026-08-25 09:29 639232461630217327
576 ms 153.121.58.112
26 2026-08-25 09:12 639232451282965990
560 ms 153.121.58.112
25 2026-08-25 08:55 639232440814614938
566 ms 153.121.58.112
24 2026-08-25 08:38 639232430410720425
570 ms 153.121.58.112
23 2026-08-25 08:20 639232420003096185
560 ms 153.121.58.112
22 2026-08-25 08:03 639232409467287444
575 ms 153.121.58.112
21 2026-08-25 07:45 639232399077195997
569 ms 153.121.58.112
20 2026-08-25 07:28 639232388731528337
562 ms 153.121.58.112
19 2026-08-25 07:11 639232378288598612
554 ms 153.121.58.112
18 2026-08-25 06:17 639232346196373643
4 ms 153.121.58.112
17 2026-08-25 06:00 639232336112370741
565 ms 153.121.58.112
16 2026-08-25 05:43 639232326146508970
552 ms 153.121.58.112
15 2026-08-25 05:27 639232316189381720
4 ms 153.121.58.112
14 2026-08-25 05:10 639232306217998913
583 ms 153.121.58.112
13 2026-08-25 04:54 639232296255744174
553 ms 153.121.58.112
12 2026-08-25 04:37 639232286095760789
542 ms 153.121.58.112
11 2026-08-25 04:20 639232276086186273
2 ms 153.121.58.112
10 2026-08-25 04:03 639232265900986425
577 ms 153.121.58.112
9 2026-08-25 03:46 639232255723518075
573 ms 153.121.58.112
8 2026-08-25 03:29 639232245484452890
554 ms 153.121.58.112
7 2026-08-25 03:12 639232235157175331
574 ms 153.121.58.112
6 2026-08-25 02:19 639232203197189095
4 ms 153.121.58.112
5 2026-08-25 02:02 639232192844564298
556 ms 153.121.58.112
4 2026-08-25 01:44 639232182496008942
548 ms 153.121.58.112
3 2026-08-25 01:27 639232172197053132
582 ms 153.121.58.112
2 2026-08-25 00:34 639232140250307418
4 ms 153.121.58.112
1 2026-08-25 00:17 639232129927860324
550 ms 153.121.58.112