DNS response history for ns2.bridengrooom.com

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

37

Historical checks stored for this nameserver on selected date

Average Latency

272 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.29.135.118

Most recently resolved hosting IP on selected date

Successful Responses

37

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.bridengrooom.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
37 2026-08-25 12:43 639232576780683689
311 ms 66.29.135.118
36 2026-08-25 12:25 639232566381512620
294 ms 66.29.135.118
35 2026-08-25 12:08 639232556111768563
294 ms 66.29.135.118
34 2026-08-25 11:51 639232545839529039
312 ms 66.29.135.118
33 2026-08-25 11:34 639232535349285207
316 ms 66.29.135.118
32 2026-08-25 11:16 639232524938080723
307 ms 66.29.135.118
31 2026-08-25 10:22 639232492740373468
167 ms 66.29.135.118
30 2026-08-25 10:05 639232482235303141
325 ms 66.29.135.118
29 2026-08-25 09:48 639232471861770303
300 ms 66.29.135.118
28 2026-08-25 09:30 639232461630217327
306 ms 66.29.135.118
27 2026-08-25 09:13 639232451282965990
298 ms 66.29.135.118
26 2026-08-25 08:56 639232440814614938
304 ms 66.29.135.118
25 2026-08-25 08:39 639232430410720425
315 ms 66.29.135.118
24 2026-08-25 08:21 639232420003096185
329 ms 66.29.135.118
23 2026-08-25 08:04 639232409467287444
311 ms 66.29.135.118
22 2026-08-25 07:46 639232399077195997
310 ms 66.29.135.118
21 2026-08-25 07:29 639232388731528337
345 ms 66.29.135.118
20 2026-08-25 07:12 639232378288598612
314 ms 66.29.135.118
19 2026-08-25 06:18 639232346196373643
3 ms 66.29.135.118
18 2026-08-25 06:01 639232336112370741
4 ms 66.29.135.118
17 2026-08-25 05:44 639232326146508970
327 ms 66.29.135.118
16 2026-08-25 05:28 639232316189381720
4 ms 66.29.135.118
15 2026-08-25 05:11 639232306217998913
318 ms 66.29.135.118
14 2026-08-25 04:55 639232296255744174
297 ms 66.29.135.118
13 2026-08-25 04:38 639232286095760789
306 ms 66.29.135.118
12 2026-08-25 04:21 639232276086186273
3 ms 66.29.135.118
11 2026-08-25 04:04 639232265900986425
320 ms 66.29.135.118
10 2026-08-25 03:47 639232255723518075
312 ms 66.29.135.118
9 2026-08-25 03:30 639232245484452890
309 ms 66.29.135.118
8 2026-08-25 03:13 639232235157175331
297 ms 66.29.135.118
7 2026-08-25 02:20 639232203197189095
308 ms 66.29.135.118
6 2026-08-25 02:03 639232192844564298
297 ms 66.29.135.118
5 2026-08-25 01:45 639232182496008942
293 ms 66.29.135.118
4 2026-08-25 01:28 639232172197053132
306 ms 66.29.135.118
3 2026-08-25 00:35 639232140250307418
307 ms 66.29.135.118
2 2026-08-25 00:18 639232129927860324
306 ms 66.29.135.118
1 2026-08-25 00:00 639232119551972438
300 ms 66.29.135.118