DNS response history for ns2.bccable.net

ns2.bccable.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-28. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 455 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.bccable.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

455 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 15:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.21.229.202

Most recently resolved hosting IP on selected date

Successful Responses

36

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

Showing DNS history for 2026-08-28 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
36 2026-08-28 15:09 639235258803654519
4 ms 50.21.229.202
35 2026-08-28 14:52 639235248596087996
5 ms 50.21.229.202
34 2026-08-28 14:35 639235238225955920
318 ms 50.21.229.202
33 2026-08-28 14:17 639235227727862105
341 ms 50.21.229.202
32 2026-08-28 13:23 639235195230848570
2156 ms 50.21.229.202
31 2026-08-28 13:06 639235184840503274
178 ms 50.21.229.202
30 2026-08-28 12:48 639235174453894956
341 ms 50.21.229.202
29 2026-08-28 12:31 639235163898672622
317 ms 50.21.229.202
28 2026-08-28 11:38 639235132147470568
335 ms 50.21.229.202
27 2026-08-28 11:21 639235121907744088
316 ms 50.21.229.202
26 2026-08-28 11:04 639235111428014262
169 ms 50.21.229.202
25 2026-08-28 10:46 639235100921813626
322 ms 50.21.229.202
24 2026-08-28 09:52 639235068670703481
314 ms 50.21.229.202
23 2026-08-28 09:35 639235058337459445
313 ms 50.21.229.202
22 2026-08-28 09:18 639235047825109146
334 ms 50.21.229.202
21 2026-08-28 09:00 639235037383229033
333 ms 50.21.229.202
20 2026-08-28 08:07 639235005619242711
317 ms 50.21.229.202
19 2026-08-28 07:50 639234995310346584
2008 ms 50.21.229.202
18 2026-08-28 07:33 639234984946548933
177 ms 50.21.229.202
17 2026-08-28 07:15 639234974608077290
343 ms 50.21.229.202
16 2026-08-28 06:22 639234942529845595
157 ms 50.21.229.202
15 2026-08-28 06:05 639234932259126627
316 ms 50.21.229.202
14 2026-08-28 05:48 639234921916735988
312 ms 50.21.229.202
13 2026-08-28 05:30 639234911470038027
316 ms 50.21.229.202
12 2026-08-28 04:37 639234879588411654
334 ms 50.21.229.202
11 2026-08-28 04:20 639234869341589104
330 ms 50.21.229.202
10 2026-08-28 04:03 639234859012216675
332 ms 50.21.229.202
9 2026-08-28 03:45 639234848695364934
320 ms 50.21.229.202
8 2026-08-28 02:53 639234816952458162
4 ms 50.21.229.202
7 2026-08-28 02:36 639234806773081598
2009 ms 50.21.229.202
6 2026-08-28 02:19 639234796382955255
190 ms 50.21.229.202
5 2026-08-28 02:01 639234786015782563
4 ms 50.21.229.202
4 2026-08-28 01:07 639234753811917646
314 ms 50.21.229.202
3 2026-08-28 00:50 639234743739767811
314 ms 50.21.229.202
2 2026-08-28 00:34 639234733372362811
2016 ms 50.21.229.202
1 2026-08-28 00:16 639234723048550337
159 ms 50.21.229.202