DNS response history for ns2.bridalnetwork.net

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

27

Historical checks stored for this nameserver on selected date

Average Latency

638 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

65.61.236.72

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.bridalnetwork.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
27 2026-08-25 09:27 639232461630217327
252 ms 65.61.236.72
26 2026-08-25 09:10 639232451282965990
3724 ms 65.61.236.72
25 2026-08-25 08:53 639232440814614938
229 ms 65.61.236.72
24 2026-08-25 08:35 639232430410720425
239 ms 65.61.236.72
23 2026-08-25 08:18 639232420003096185
235 ms 65.61.236.72
22 2026-08-25 08:01 639232409467287444
249 ms 65.61.236.72
21 2026-08-25 07:43 639232399077195997
239 ms 65.61.236.72
20 2026-08-25 07:26 639232388731528337
234 ms 65.61.236.72
19 2026-08-25 07:08 639232378288598612
2140 ms 65.61.236.72
18 2026-08-25 06:15 639232346196373643
242 ms 65.61.236.72
17 2026-08-25 05:58 639232336112370741
154 ms 65.61.236.72
16 2026-08-25 05:41 639232326146508970
251 ms 65.61.236.72
15 2026-08-25 05:25 639232316189381720
244 ms 65.61.236.72
14 2026-08-25 05:08 639232306217998913
123 ms 65.61.236.72
13 2026-08-25 04:52 639232296255744174
2137 ms 65.61.236.72
12 2026-08-25 04:35 639232286095760789
246 ms 65.61.236.72
11 2026-08-25 04:18 639232276086186273
266 ms 65.61.236.72
10 2026-08-25 04:01 639232265900986425
237 ms 65.61.236.72
9 2026-08-25 03:44 639232255723518075
230 ms 65.61.236.72
8 2026-08-25 03:27 639232245484452890
2117 ms 65.61.236.72
7 2026-08-25 03:10 639232235157175331
230 ms 65.61.236.72
6 2026-08-25 02:17 639232203197189095
139 ms 65.61.236.72
5 2026-08-25 02:00 639232192844564298
222 ms 65.61.236.72
4 2026-08-25 01:42 639232182496008942
239 ms 65.61.236.72
3 2026-08-25 01:25 639232172197053132
221 ms 65.61.236.72
2 2026-08-25 00:32 639232140250307418
2167 ms 65.61.236.72
1 2026-08-25 00:15 639232129927860324
228 ms 65.61.236.72