DNS response history for bzhns2.plala.or.jp

bzhns2.plala.or.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 35 DNS check records, 35 successful responses, 0 failed responses, and 314 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 bzhns2.plala.or.jp.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

314 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

220.220.248.123

Most recently resolved hosting IP on selected date

Successful Responses

35

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 bzhns2.plala.or.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
35 2026-08-25 12:21 639232566381512620
244 ms 220.220.248.123
34 2026-08-25 12:04 639232556111768563
259 ms 220.220.248.123
33 2026-08-25 11:47 639232545839529039
257 ms 220.220.248.123
32 2026-08-25 11:30 639232535349285207
272 ms 220.220.248.123
31 2026-08-25 11:12 639232524938080723
250 ms 220.220.248.123
30 2026-08-25 10:18 639232492740373468
266 ms 220.220.248.123
29 2026-08-25 10:01 639232482235303141
252 ms 220.220.248.123
28 2026-08-25 09:44 639232471861770303
281 ms 220.220.248.123
27 2026-08-25 09:27 639232461630217327
260 ms 220.220.248.123
26 2026-08-25 09:09 639232451282965990
346 ms 220.220.248.123
25 2026-08-25 08:52 639232440814614938
242 ms 220.220.248.123
24 2026-08-25 08:35 639232430410720425
236 ms 220.220.248.123
23 2026-08-25 08:17 639232420003096185
260 ms 220.220.248.123
22 2026-08-25 08:00 639232409467287444
262 ms 220.220.248.123
21 2026-08-25 07:42 639232399077195997
2257 ms 220.220.248.123
20 2026-08-25 07:25 639232388731528337
255 ms 220.220.248.123
19 2026-08-25 07:08 639232378288598612
257 ms 220.220.248.123
18 2026-08-25 06:14 639232346196373643
296 ms 220.220.248.123
17 2026-08-25 05:57 639232336112370741
247 ms 220.220.248.123
16 2026-08-25 05:41 639232326146508970
251 ms 220.220.248.123
15 2026-08-25 05:24 639232316189381720
258 ms 220.220.248.123
14 2026-08-25 05:08 639232306217998913
241 ms 220.220.248.123
13 2026-08-25 04:51 639232296255744174
242 ms 220.220.248.123
12 2026-08-25 04:34 639232286095760789
258 ms 220.220.248.123
11 2026-08-25 04:17 639232276086186273
250 ms 220.220.248.123
10 2026-08-25 04:00 639232265900986425
253 ms 220.220.248.123
9 2026-08-25 03:43 639232255723518075
243 ms 220.220.248.123
8 2026-08-25 03:26 639232245484452890
232 ms 220.220.248.123
7 2026-08-25 03:09 639232235157175331
237 ms 220.220.248.123
6 2026-08-25 02:16 639232203197189095
248 ms 220.220.248.123
5 2026-08-25 01:59 639232192844564298
246 ms 220.220.248.123
4 2026-08-25 01:41 639232182496008942
243 ms 220.220.248.123
3 2026-08-25 01:24 639232172197053132
258 ms 220.220.248.123
2 2026-08-25 00:31 639232140250307418
269 ms 220.220.248.123
1 2026-08-25 00:14 639232129927860324
258 ms 220.220.248.123