DNS response history for ns2.brillinjurylaw.com

ns2.brillinjurylaw.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 347 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.brillinjurylaw.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

347 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.65.3.190

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.brillinjurylaw.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:41 639232471861770303
234 ms 69.65.3.190
27 2026-08-25 09:24 639232461630217327
114 ms 69.65.3.190
26 2026-08-25 09:07 639232451282965990
240 ms 69.65.3.190
25 2026-08-25 08:49 639232440814614938
144 ms 69.65.3.190
24 2026-08-25 08:32 639232430410720425
229 ms 69.65.3.190
23 2026-08-25 08:15 639232420003096185
251 ms 69.65.3.190
22 2026-08-25 07:57 639232409467287444
129 ms 69.65.3.190
21 2026-08-25 07:40 639232399077195997
235 ms 69.65.3.190
20 2026-08-25 07:22 639232388731528337
128 ms 69.65.3.190
19 2026-08-25 07:05 639232378288598612
690 ms 69.65.3.190
18 2026-08-25 06:12 639232346196373643
237 ms 69.65.3.190
17 2026-08-25 05:55 639232336112370741
2129 ms 69.65.3.190
16 2026-08-25 05:38 639232326146508970
249 ms 69.65.3.190
15 2026-08-25 05:22 639232316189381720
2244 ms 69.65.3.190
14 2026-08-25 05:05 639232306217998913
229 ms 69.65.3.190
13 2026-08-25 04:48 639232296255744174
253 ms 69.65.3.190
12 2026-08-25 04:32 639232286095760789
118 ms 69.65.3.190
11 2026-08-25 04:15 639232276086186273
111 ms 69.65.3.190
10 2026-08-25 03:58 639232265900986425
226 ms 69.65.3.190
9 2026-08-25 03:41 639232255723518075
251 ms 69.65.3.190
8 2026-08-25 03:24 639232245484452890
114 ms 69.65.3.190
7 2026-08-25 03:07 639232235157175331
135 ms 69.65.3.190
6 2026-08-25 02:13 639232203197189095
138 ms 69.65.3.190
5 2026-08-25 01:56 639232192844564298
240 ms 69.65.3.190
4 2026-08-25 01:39 639232182496008942
237 ms 69.65.3.190
3 2026-08-25 01:22 639232172197053132
177 ms 69.65.3.190
2 2026-08-25 00:28 639232140250307418
113 ms 69.65.3.190
1 2026-08-25 00:11 639232129927860324
115 ms 69.65.3.190