DNS response history for ns2.bridgemontcap.com

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

29

Historical checks stored for this nameserver on selected date

Average Latency

299 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.109.230.192

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.bridgemontcap.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
29 2026-08-25 10:01 639232482235303141
321 ms 208.109.230.192
28 2026-08-25 09:43 639232471861770303
316 ms 208.109.230.192
27 2026-08-25 09:26 639232461630217327
324 ms 208.109.230.192
26 2026-08-25 09:09 639232451282965990
324 ms 208.109.230.192
25 2026-08-25 08:51 639232440814614938
9 ms 208.109.230.192
24 2026-08-25 08:34 639232430410720425
11 ms 208.109.230.192
23 2026-08-25 08:17 639232420003096185
24 ms 208.109.230.192
22 2026-08-25 07:59 639232409467287444
311 ms 208.109.230.192
21 2026-08-25 07:42 639232399077195997
174 ms 208.109.230.192
20 2026-08-25 07:25 639232388731528337
322 ms 208.109.230.192
19 2026-08-25 07:07 639232378288598612
315 ms 208.109.230.192
18 2026-08-25 06:14 639232346196373643
320 ms 208.109.230.192
17 2026-08-25 05:57 639232336112370741
36 ms 208.109.230.192
16 2026-08-25 05:40 639232326146508970
313 ms 208.109.230.192
15 2026-08-25 05:23 639232316189381720
10 ms 208.109.230.192
14 2026-08-25 05:07 639232306217998913
280 ms 208.109.230.192
13 2026-08-25 04:50 639232296255744174
311 ms 208.109.230.192
12 2026-08-25 04:33 639232286095760789
313 ms 208.109.230.192
11 2026-08-25 04:17 639232276086186273
316 ms 208.109.230.192
10 2026-08-25 04:00 639232265900986425
310 ms 208.109.230.192
9 2026-08-25 03:43 639232255723518075
313 ms 208.109.230.192
8 2026-08-25 03:26 639232245484452890
180 ms 208.109.230.192
7 2026-08-25 03:09 639232235157175331
322 ms 208.109.230.192
6 2026-08-25 02:15 639232203197189095
317 ms 208.109.230.192
5 2026-08-25 01:58 639232192844564298
2177 ms 208.109.230.192
4 2026-08-25 01:41 639232182496008942
9 ms 208.109.230.192
3 2026-08-25 01:24 639232172197053132
175 ms 208.109.230.192
2 2026-08-25 00:30 639232140250307418
308 ms 208.109.230.192
1 2026-08-25 00:13 639232129927860324
205 ms 208.109.230.192