DNS response history for ns2.bringardner.us

ns2.bringardner.us 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 448 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.bringardner.us.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

448 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

54.69.215.66

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.bringardner.us

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:04 639232482235303141
349 ms 54.69.215.66
28 2026-08-25 09:46 639232471861770303
4 ms 54.69.215.66
27 2026-08-25 09:29 639232461630217327
361 ms 54.69.215.66
26 2026-08-25 09:12 639232451282965990
4 ms 54.69.215.66
25 2026-08-25 08:55 639232440814614938
342 ms 54.69.215.66
24 2026-08-25 08:37 639232430410720425
349 ms 54.69.215.66
23 2026-08-25 08:20 639232420003096185
353 ms 54.69.215.66
22 2026-08-25 08:03 639232409467287444
346 ms 54.69.215.66
21 2026-08-25 07:45 639232399077195997
3 ms 54.69.215.66
20 2026-08-25 07:28 639232388731528337
357 ms 54.69.215.66
19 2026-08-25 07:10 639232378288598612
3 ms 54.69.215.66
18 2026-08-25 06:17 639232346196373643
354 ms 54.69.215.66
17 2026-08-25 06:00 639232336112370741
4182 ms 54.69.215.66
16 2026-08-25 05:43 639232326146508970
382 ms 54.69.215.66
15 2026-08-25 05:27 639232316189381720
342 ms 54.69.215.66
14 2026-08-25 05:10 639232306217998913
3 ms 54.69.215.66
13 2026-08-25 04:53 639232296255744174
961 ms 54.69.215.66
12 2026-08-25 04:37 639232286095760789
3 ms 54.69.215.66
11 2026-08-25 04:20 639232276086186273
338 ms 54.69.215.66
10 2026-08-25 04:03 639232265900986425
378 ms 54.69.215.66
9 2026-08-25 03:46 639232255723518075
3 ms 54.69.215.66
8 2026-08-25 03:29 639232245484452890
2 ms 54.69.215.66
7 2026-08-25 03:12 639232235157175331
328 ms 54.69.215.66
6 2026-08-25 02:18 639232203197189095
2159 ms 54.69.215.66
5 2026-08-25 02:01 639232192844564298
351 ms 54.69.215.66
4 2026-08-25 01:44 639232182496008942
375 ms 54.69.215.66
3 2026-08-25 01:27 639232172197053132
364 ms 54.69.215.66
2 2026-08-25 00:33 639232140250307418
3 ms 54.69.215.66
1 2026-08-25 00:17 639232129927860324
4 ms 54.69.215.66