DNS response history for ns1.claydrop.com

ns1.claydrop.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, 29 successful responses, 2 failed responses, and 269 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 ns1.claydrop.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

269 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

5.196.101.250

Most recently resolved hosting IP on selected date

Successful Responses

29

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

6%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.claydrop.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 10:22 639232492740373468
252 ms 5.196.101.250
30 2026-08-25 10:05 639232482235303141
253 ms 5.196.101.250
29 2026-08-25 09:48 639232471861770303
280 ms 5.196.101.250
28 2026-08-25 09:31 639232461630217327
-
27 2026-08-25 09:13 639232451282965990
252 ms 5.196.101.250
26 2026-08-25 08:56 639232440814614938
250 ms 5.196.101.250
25 2026-08-25 08:39 639232430410720425
294 ms 5.196.101.250
24 2026-08-25 08:21 639232420003096185
286 ms 5.196.101.250
23 2026-08-25 08:04 639232409467287444
280 ms 5.196.101.250
22 2026-08-25 07:46 639232399077195997
280 ms 5.196.101.250
21 2026-08-25 07:29 639232388731528337
252 ms 5.196.101.250
20 2026-08-25 07:12 639232378288598612
251 ms 5.196.101.250
19 2026-08-25 06:18 639232346196373643
281 ms 5.196.101.250
18 2026-08-25 06:01 639232336112370741
293 ms 5.196.101.250
17 2026-08-25 05:44 639232326146508970
279 ms 5.196.101.250
16 2026-08-25 05:28 639232316189381720
279 ms 5.196.101.250
15 2026-08-25 05:11 639232306217998913
246 ms 5.196.101.250
14 2026-08-25 04:54 639232296255744174
279 ms 5.196.101.250
13 2026-08-25 04:38 639232286095760789
248 ms 5.196.101.250
12 2026-08-25 04:21 639232276086186273
250 ms 5.196.101.250
11 2026-08-25 04:04 639232265900986425
252 ms 5.196.101.250
10 2026-08-25 03:47 639232255723518075
279 ms 5.196.101.250
9 2026-08-25 03:30 639232245484452890
278 ms 5.196.101.250
8 2026-08-25 03:13 639232235157175331
278 ms 5.196.101.250
7 2026-08-25 02:20 639232203197189095
-
6 2026-08-25 02:03 639232192844564298
279 ms 5.196.101.250
5 2026-08-25 01:45 639232182496008942
279 ms 5.196.101.250
4 2026-08-25 01:28 639232172197053132
250 ms 5.196.101.250
3 2026-08-25 00:35 639232140250307418
248 ms 5.196.101.250
2 2026-08-25 00:18 639232129927860324
265 ms 5.196.101.250
1 2026-08-25 00:00 639232119551972438
298 ms 5.196.101.250