DNS response history for ns2.consumerlawattorneys.com

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

31

Historical checks stored for this nameserver on selected date

Average Latency

186 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.241.191.112

Most recently resolved hosting IP on selected date

Successful Responses

31

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.consumerlawattorneys.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
31 2026-08-25 11:11 639232524938080723
283 ms 162.241.191.112
30 2026-08-25 10:17 639232492740373468
3 ms 162.241.191.112
29 2026-08-25 10:00 639232482235303141
277 ms 162.241.191.112
28 2026-08-25 09:43 639232471861770303
139 ms 162.241.191.112
27 2026-08-25 09:26 639232461630217327
273 ms 162.241.191.112
26 2026-08-25 09:08 639232451282965990
276 ms 162.241.191.112
25 2026-08-25 08:51 639232440814614938
8 ms 162.241.191.112
24 2026-08-25 08:34 639232430410720425
280 ms 162.241.191.112
23 2026-08-25 08:16 639232420003096185
142 ms 162.241.191.112
22 2026-08-25 07:59 639232409467287444
279 ms 162.241.191.112
21 2026-08-25 07:41 639232399077195997
284 ms 162.241.191.112
20 2026-08-25 07:24 639232388731528337
155 ms 162.241.191.112
19 2026-08-25 07:07 639232378288598612
277 ms 162.241.191.112
18 2026-08-25 06:13 639232346196373643
274 ms 162.241.191.112
17 2026-08-25 05:56 639232336112370741
278 ms 162.241.191.112
16 2026-08-25 05:40 639232326146508970
274 ms 162.241.191.112
15 2026-08-25 05:23 639232316189381720
9 ms 162.241.191.112
14 2026-08-25 05:07 639232306217998913
157 ms 162.241.191.112
13 2026-08-25 04:50 639232296255744174
271 ms 162.241.191.112
12 2026-08-25 04:33 639232286095760789
231 ms 162.241.191.112
11 2026-08-25 04:16 639232276086186273
137 ms 162.241.191.112
10 2026-08-25 03:59 639232265900986425
3 ms 162.241.191.112
9 2026-08-25 03:42 639232255723518075
4 ms 162.241.191.112
8 2026-08-25 03:25 639232245484452890
140 ms 162.241.191.112
7 2026-08-25 03:08 639232235157175331
276 ms 162.241.191.112
6 2026-08-25 02:15 639232203197189095
146 ms 162.241.191.112
5 2026-08-25 01:58 639232192844564298
134 ms 162.241.191.112
4 2026-08-25 01:40 639232182496008942
132 ms 162.241.191.112
3 2026-08-25 01:23 639232172197053132
289 ms 162.241.191.112
2 2026-08-25 00:30 639232140250307418
274 ms 162.241.191.112
1 2026-08-25 00:13 639232129927860324
49 ms 162.241.191.112