DNS response history for ns2.shadowalert.com

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

32

Historical checks stored for this nameserver on selected date

Average Latency

425 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

216.106.179.165

Most recently resolved hosting IP on selected date

Successful Responses

32

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.shadowalert.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
32 2026-08-25 11:29 639232535349285207
256 ms 216.106.179.165
31 2026-08-25 11:12 639232524938080723
252 ms 216.106.179.165
30 2026-08-25 10:18 639232492740373468
242 ms 216.106.179.165
29 2026-08-25 10:01 639232482235303141
245 ms 216.106.179.165
28 2026-08-25 09:43 639232471861770303
247 ms 216.106.179.165
27 2026-08-25 09:26 639232461630217327
245 ms 216.106.179.165
26 2026-08-25 09:09 639232451282965990
249 ms 216.106.179.165
25 2026-08-25 08:52 639232440814614938
238 ms 216.106.179.165
24 2026-08-25 08:34 639232430410720425
259 ms 216.106.179.165
23 2026-08-25 08:17 639232420003096185
240 ms 216.106.179.165
22 2026-08-25 08:00 639232409467287444
262 ms 216.106.179.165
21 2026-08-25 07:42 639232399077195997
250 ms 216.106.179.165
20 2026-08-25 07:25 639232388731528337
243 ms 216.106.179.165
19 2026-08-25 07:07 639232378288598612
2182 ms 216.106.179.165
18 2026-08-25 06:14 639232346196373643
266 ms 216.106.179.165
17 2026-08-25 05:57 639232336112370741
269 ms 216.106.179.165
16 2026-08-25 05:40 639232326146508970
247 ms 216.106.179.165
15 2026-08-25 05:24 639232316189381720
261 ms 216.106.179.165
14 2026-08-25 05:07 639232306217998913
2192 ms 216.106.179.165
13 2026-08-25 04:51 639232296255744174
2186 ms 216.106.179.165
12 2026-08-25 04:34 639232286095760789
129 ms 216.106.179.165
11 2026-08-25 04:17 639232276086186273
264 ms 216.106.179.165
10 2026-08-25 04:00 639232265900986425
251 ms 216.106.179.165
9 2026-08-25 03:43 639232255723518075
242 ms 216.106.179.165
8 2026-08-25 03:26 639232245484452890
261 ms 216.106.179.165
7 2026-08-25 03:09 639232235157175331
265 ms 216.106.179.165
6 2026-08-25 02:16 639232203197189095
126 ms 216.106.179.165
5 2026-08-25 01:58 639232192844564298
241 ms 216.106.179.165
4 2026-08-25 01:41 639232182496008942
244 ms 216.106.179.165
3 2026-08-25 01:24 639232172197053132
260 ms 216.106.179.165
2 2026-08-25 00:31 639232140250307418
245 ms 216.106.179.165
1 2026-08-25 00:14 639232129927860324
238 ms 216.106.179.165