DNS response history for ns2.bridgeband.net

ns2.bridgeband.net 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 29 DNS check records, 29 successful responses, 0 failed responses, and 399 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.bridgeband.net.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

399 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

63.166.28.2

Most recently resolved hosting IP on selected date

Successful Responses

29

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.bridgeband.net

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
29 2026-08-25 10:03 639232482235303141
399 ms 63.166.28.2
28 2026-08-25 09:45 639232471861770303
201 ms 63.166.28.2
27 2026-08-25 09:28 639232461630217327
209 ms 63.166.28.2
26 2026-08-25 09:11 639232451282965990
202 ms 63.166.28.2
25 2026-08-25 08:53 639232440814614938
209 ms 63.166.28.2
24 2026-08-25 08:36 639232430410720425
226 ms 63.166.28.2
23 2026-08-25 08:19 639232420003096185
213 ms 63.166.28.2
22 2026-08-25 08:01 639232409467287444
416 ms 63.166.28.2
21 2026-08-25 07:44 639232399077195997
211 ms 63.166.28.2
20 2026-08-25 07:26 639232388731528337
207 ms 63.166.28.2
19 2026-08-25 07:09 639232378288598612
205 ms 63.166.28.2
18 2026-08-25 06:15 639232346196373643
199 ms 63.166.28.2
17 2026-08-25 05:58 639232336112370741
178 ms 63.166.28.2
16 2026-08-25 05:42 639232326146508970
560 ms 63.166.28.2
15 2026-08-25 05:25 639232316189381720
210 ms 63.166.28.2
14 2026-08-25 05:09 639232306217998913
203 ms 63.166.28.2
13 2026-08-25 04:52 639232296255744174
2178 ms 63.166.28.2
12 2026-08-25 04:35 639232286095760789
159 ms 63.166.28.2
11 2026-08-25 04:18 639232276086186273
196 ms 63.166.28.2
10 2026-08-25 04:02 639232265900986425
2179 ms 63.166.28.2
9 2026-08-25 03:45 639232255723518075
205 ms 63.166.28.2
8 2026-08-25 03:28 639232245484452890
198 ms 63.166.28.2
7 2026-08-25 03:10 639232235157175331
209 ms 63.166.28.2
6 2026-08-25 02:17 639232203197189095
282 ms 63.166.28.2
5 2026-08-25 02:00 639232192844564298
578 ms 63.166.28.2
4 2026-08-25 01:43 639232182496008942
416 ms 63.166.28.2
3 2026-08-25 01:25 639232172197053132
198 ms 63.166.28.2
2 2026-08-25 00:32 639232140250307418
219 ms 63.166.28.2
1 2026-08-25 00:15 639232129927860324
507 ms 63.166.28.2