DNS response history for ns2.bridgecontinentsgroup.com

ns2.bridgecontinentsgroup.com 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 342 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.bridgecontinentsgroup.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

342 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

68.178.163.162

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.bridgecontinentsgroup.com

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:27 639232461630217327
182 ms 68.178.163.162
26 2026-08-25 09:10 639232451282965990
331 ms 68.178.163.162
25 2026-08-25 08:52 639232440814614938
337 ms 68.178.163.162
24 2026-08-25 08:35 639232430410720425
324 ms 68.178.163.162
23 2026-08-25 08:18 639232420003096185
169 ms 68.178.163.162
22 2026-08-25 08:00 639232409467287444
323 ms 68.178.163.162
21 2026-08-25 07:43 639232399077195997
167 ms 68.178.163.162
20 2026-08-25 07:25 639232388731528337
325 ms 68.178.163.162
19 2026-08-25 07:08 639232378288598612
3 ms 68.178.163.162
18 2026-08-25 06:14 639232346196373643
2321 ms 68.178.163.162
17 2026-08-25 05:57 639232336112370741
322 ms 68.178.163.162
16 2026-08-25 05:41 639232326146508970
334 ms 68.178.163.162
15 2026-08-25 05:24 639232316189381720
164 ms 68.178.163.162
14 2026-08-25 05:08 639232306217998913
323 ms 68.178.163.162
13 2026-08-25 04:51 639232296255744174
321 ms 68.178.163.162
12 2026-08-25 04:34 639232286095760789
324 ms 68.178.163.162
11 2026-08-25 04:17 639232276086186273
323 ms 68.178.163.162
10 2026-08-25 04:01 639232265900986425
343 ms 68.178.163.162
9 2026-08-25 03:44 639232255723518075
322 ms 68.178.163.162
8 2026-08-25 03:26 639232245484452890
167 ms 68.178.163.162
7 2026-08-25 03:09 639232235157175331
178 ms 68.178.163.162
6 2026-08-25 02:16 639232203197189095
163 ms 68.178.163.162
5 2026-08-25 01:59 639232192844564298
334 ms 68.178.163.162
4 2026-08-25 01:42 639232182496008942
332 ms 68.178.163.162
3 2026-08-25 01:24 639232172197053132
320 ms 68.178.163.162
2 2026-08-25 00:31 639232140250307418
159 ms 68.178.163.162
1 2026-08-25 00:14 639232129927860324
330 ms 68.178.163.162