DNS response history for ns2.brandol.jp

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

27

Historical checks stored for this nameserver on selected date

Average Latency

508 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.122.4.133

Most recently resolved hosting IP on selected date

Successful Responses

27

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.brandol.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
27 2026-08-25 09:29 639232461630217327
548 ms 153.122.4.133
26 2026-08-25 09:12 639232451282965990
560 ms 153.122.4.133
25 2026-08-25 08:54 639232440814614938
9 ms 153.122.4.133
24 2026-08-25 08:37 639232430410720425
534 ms 153.122.4.133
23 2026-08-25 08:20 639232420003096185
535 ms 153.122.4.133
22 2026-08-25 08:02 639232409467287444
39 ms 153.122.4.133
21 2026-08-25 07:45 639232399077195997
549 ms 153.122.4.133
20 2026-08-25 07:27 639232388731528337
2007 ms 153.122.4.133
19 2026-08-25 07:10 639232378288598612
572 ms 153.122.4.133
18 2026-08-25 06:16 639232346196373643
4 ms 153.122.4.133
17 2026-08-25 05:59 639232336112370741
8 ms 153.122.4.133
16 2026-08-25 05:43 639232326146508970
3 ms 153.122.4.133
15 2026-08-25 05:26 639232316189381720
2298 ms 153.122.4.133
14 2026-08-25 05:10 639232306217998913
3 ms 153.122.4.133
13 2026-08-25 04:53 639232296255744174
531 ms 153.122.4.133
12 2026-08-25 04:36 639232286095760789
537 ms 153.122.4.133
11 2026-08-25 04:19 639232276086186273
3 ms 153.122.4.133
10 2026-08-25 04:03 639232265900986425
553 ms 153.122.4.133
9 2026-08-25 03:46 639232255723518075
547 ms 153.122.4.133
8 2026-08-25 03:29 639232245484452890
553 ms 153.122.4.133
7 2026-08-25 03:11 639232235157175331
3 ms 153.122.4.133
6 2026-08-25 02:18 639232203197189095
568 ms 153.122.4.133
5 2026-08-25 02:01 639232192844564298
547 ms 153.122.4.133
4 2026-08-25 01:44 639232182496008942
548 ms 153.122.4.133
3 2026-08-25 01:26 639232172197053132
543 ms 153.122.4.133
2 2026-08-25 00:33 639232140250307418
560 ms 153.122.4.133
1 2026-08-25 00:16 639232129927860324
555 ms 153.122.4.133