DNS response history for ns2.danewerk.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

285 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.222.57.220

Most recently resolved hosting IP on selected date

Successful Responses

30

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.danewerk.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
30 2026-08-25 10:20 639232492740373468
358 ms 51.222.57.220
29 2026-08-25 10:03 639232482235303141
352 ms 51.222.57.220
28 2026-08-25 09:45 639232471861770303
232 ms 51.222.57.220
27 2026-08-25 09:28 639232461630217327
240 ms 51.222.57.220
26 2026-08-25 09:11 639232451282965990
233 ms 51.222.57.220
25 2026-08-25 08:54 639232440814614938
346 ms 51.222.57.220
24 2026-08-25 08:36 639232430410720425
350 ms 51.222.57.220
23 2026-08-25 08:19 639232420003096185
360 ms 51.222.57.220
22 2026-08-25 08:02 639232409467287444
360 ms 51.222.57.220
21 2026-08-25 07:44 639232399077195997
238 ms 51.222.57.220
20 2026-08-25 07:27 639232388731528337
345 ms 51.222.57.220
19 2026-08-25 07:09 639232378288598612
350 ms 51.222.57.220
18 2026-08-25 06:16 639232346196373643
352 ms 51.222.57.220
17 2026-08-25 05:59 639232336112370741
7 ms 51.222.57.220
16 2026-08-25 05:42 639232326146508970
361 ms 51.222.57.220
15 2026-08-25 05:26 639232316189381720
354 ms 51.222.57.220
14 2026-08-25 05:09 639232306217998913
2 ms 51.222.57.220
13 2026-08-25 04:52 639232296255744174
9 ms 51.222.57.220
12 2026-08-25 04:36 639232286095760789
216 ms 51.222.57.220
11 2026-08-25 04:19 639232276086186273
360 ms 51.222.57.220
10 2026-08-25 04:02 639232265900986425
237 ms 51.222.57.220
9 2026-08-25 03:45 639232255723518075
348 ms 51.222.57.220
8 2026-08-25 03:28 639232245484452890
350 ms 51.222.57.220
7 2026-08-25 03:11 639232235157175331
351 ms 51.222.57.220
6 2026-08-25 02:18 639232203197189095
353 ms 51.222.57.220
5 2026-08-25 02:01 639232192844564298
346 ms 51.222.57.220
4 2026-08-25 01:43 639232182496008942
347 ms 51.222.57.220
3 2026-08-25 01:26 639232172197053132
228 ms 51.222.57.220
2 2026-08-25 00:33 639232140250307418
349 ms 51.222.57.220
1 2026-08-25 00:16 639232129927860324
214 ms 51.222.57.220