DNS response history for bs-ns-user02.bindcloud.jp

bs-ns-user02.bindcloud.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 34 DNS check records, 34 successful responses, 0 failed responses, and 368 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 bs-ns-user02.bindcloud.jp.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

368 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.131.150.85

Most recently resolved hosting IP on selected date

Successful Responses

34

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 bs-ns-user02.bindcloud.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
34 2026-08-25 12:06 639232556111768563
242 ms 210.131.150.85
33 2026-08-25 11:49 639232545839529039
482 ms 210.131.150.85
32 2026-08-25 11:32 639232535349285207
236 ms 210.131.150.85
31 2026-08-25 11:14 639232524938080723
243 ms 210.131.150.85
30 2026-08-25 10:21 639232492740373468
469 ms 210.131.150.85
29 2026-08-25 10:03 639232482235303141
241 ms 210.131.150.85
28 2026-08-25 09:46 639232471861770303
499 ms 210.131.150.85
27 2026-08-25 09:29 639232461630217327
512 ms 210.131.150.85
26 2026-08-25 09:12 639232451282965990
240 ms 210.131.150.85
25 2026-08-25 08:54 639232440814614938
486 ms 210.131.150.85
24 2026-08-25 08:37 639232430410720425
294 ms 210.131.150.85
23 2026-08-25 08:20 639232420003096185
243 ms 210.131.150.85
22 2026-08-25 08:02 639232409467287444
244 ms 210.131.150.85
21 2026-08-25 07:45 639232399077195997
287 ms 210.131.150.85
20 2026-08-25 07:27 639232388731528337
18 ms 210.131.150.85
19 2026-08-25 07:10 639232378288598612
488 ms 210.131.150.85
18 2026-08-25 06:16 639232346196373643
278 ms 210.131.150.85
17 2026-08-25 05:59 639232336112370741
245 ms 210.131.150.85
16 2026-08-25 05:43 639232326146508970
33 ms 210.131.150.85
15 2026-08-25 05:26 639232316189381720
263 ms 210.131.150.85
14 2026-08-25 05:10 639232306217998913
242 ms 210.131.150.85
13 2026-08-25 04:53 639232296255744174
2284 ms 210.131.150.85
12 2026-08-25 04:36 639232286095760789
479 ms 210.131.150.85
11 2026-08-25 04:19 639232276086186273
242 ms 210.131.150.85
10 2026-08-25 04:03 639232265900986425
244 ms 210.131.150.85
9 2026-08-25 03:46 639232255723518075
495 ms 210.131.150.85
8 2026-08-25 03:29 639232245484452890
486 ms 210.131.150.85
7 2026-08-25 03:11 639232235157175331
238 ms 210.131.150.85
6 2026-08-25 02:18 639232203197189095
479 ms 210.131.150.85
5 2026-08-25 02:01 639232192844564298
312 ms 210.131.150.85
4 2026-08-25 01:44 639232182496008942
242 ms 210.131.150.85
3 2026-08-25 01:26 639232172197053132
243 ms 210.131.150.85
2 2026-08-25 00:33 639232140250307418
479 ms 210.131.150.85
1 2026-08-25 00:16 639232129927860324
9 ms 210.131.150.85