DNS response history for ns2.briancueny.com

ns2.briancueny.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 162 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.briancueny.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

162 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

13.13.13.97

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.briancueny.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:43 639232471861770303
157 ms 13.13.13.97
27 2026-08-25 09:26 639232461630217327
166 ms 13.13.13.97
26 2026-08-25 09:09 639232451282965990
155 ms 13.13.13.97
25 2026-08-25 08:52 639232440814614938
388 ms 13.13.13.97
24 2026-08-25 08:34 639232430410720425
145 ms 13.13.13.97
23 2026-08-25 08:17 639232420003096185
143 ms 13.13.13.97
22 2026-08-25 08:00 639232409467287444
148 ms 13.13.13.97
21 2026-08-25 07:42 639232399077195997
153 ms 13.13.13.97
20 2026-08-25 07:25 639232388731528337
162 ms 13.13.13.97
19 2026-08-25 07:07 639232378288598612
141 ms 13.13.13.97
18 2026-08-25 06:14 639232346196373643
159 ms 13.13.13.97
17 2026-08-25 05:57 639232336112370741
159 ms 13.13.13.97
16 2026-08-25 05:40 639232326146508970
142 ms 13.13.13.97
15 2026-08-25 05:24 639232316189381720
25 ms 13.13.13.97
14 2026-08-25 05:07 639232306217998913
6 ms 13.13.13.97
13 2026-08-25 04:50 639232296255744174
6 ms 13.13.13.97
12 2026-08-25 04:34 639232286095760789
152 ms 13.13.13.97
11 2026-08-25 04:17 639232276086186273
149 ms 13.13.13.97
10 2026-08-25 04:00 639232265900986425
154 ms 13.13.13.97
9 2026-08-25 03:43 639232255723518075
146 ms 13.13.13.97
8 2026-08-25 03:26 639232245484452890
142 ms 13.13.13.97
7 2026-08-25 03:09 639232235157175331
151 ms 13.13.13.97
6 2026-08-25 02:15 639232203197189095
158 ms 13.13.13.97
5 2026-08-25 01:58 639232192844564298
145 ms 13.13.13.97
4 2026-08-25 01:41 639232182496008942
140 ms 13.13.13.97
3 2026-08-25 01:24 639232172197053132
141 ms 13.13.13.97
2 2026-08-25 00:30 639232140250307418
643 ms 13.13.13.97
1 2026-08-25 00:13 639232129927860324
158 ms 13.13.13.97