DNS response history for ns2.bridgeconnectgy.com

ns2.bridgeconnectgy.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 28 DNS check records, 28 successful responses, 0 failed responses, and 330 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.bridgeconnectgy.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

330 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.50.108.204

Most recently resolved hosting IP on selected date

Successful Responses

28

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.bridgeconnectgy.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
28 2026-08-25 09:30 639232461630217327
426 ms 74.50.108.204
27 2026-08-25 09:13 639232451282965990
409 ms 74.50.108.204
26 2026-08-25 08:56 639232440814614938
384 ms 74.50.108.204
25 2026-08-25 08:39 639232430410720425
406 ms 74.50.108.204
24 2026-08-25 08:21 639232420003096185
404 ms 74.50.108.204
23 2026-08-25 08:04 639232409467287444
5 ms 74.50.108.204
22 2026-08-25 07:46 639232399077195997
387 ms 74.50.108.204
21 2026-08-25 07:29 639232388731528337
407 ms 74.50.108.204
20 2026-08-25 07:12 639232378288598612
390 ms 74.50.108.204
19 2026-08-25 06:18 639232346196373643
3 ms 74.50.108.204
18 2026-08-25 06:01 639232336112370741
5 ms 74.50.108.204
17 2026-08-25 05:44 639232326146508970
2 ms 74.50.108.204
16 2026-08-25 05:28 639232316189381720
5 ms 74.50.108.204
15 2026-08-25 05:11 639232306217998913
399 ms 74.50.108.204
14 2026-08-25 04:54 639232296255744174
128 ms 74.50.108.204
13 2026-08-25 04:38 639232286095760789
231 ms 74.50.108.204
12 2026-08-25 04:21 639232276086186273
229 ms 74.50.108.204
11 2026-08-25 04:04 639232265900986425
402 ms 74.50.108.204
10 2026-08-25 03:47 639232255723518075
234 ms 74.50.108.204
9 2026-08-25 03:30 639232245484452890
231 ms 74.50.108.204
8 2026-08-25 03:13 639232235157175331
237 ms 74.50.108.204
7 2026-08-25 02:20 639232203197189095
2119 ms 74.50.108.204
6 2026-08-25 02:03 639232192844564298
257 ms 74.50.108.204
5 2026-08-25 01:45 639232182496008942
238 ms 74.50.108.204
4 2026-08-25 01:28 639232172197053132
232 ms 74.50.108.204
3 2026-08-25 00:35 639232140250307418
246 ms 74.50.108.204
2 2026-08-25 00:18 639232129927860324
416 ms 74.50.108.204
1 2026-08-25 00:00 639232119551972438
405 ms 74.50.108.204