DNS response history for ns1.claim4d.org

ns1.claim4d.org 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 491 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.claim4d.org.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

491 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

27.102.138.16

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 ns1.claim4d.org

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:21 639232492740373468
298 ms 27.102.138.16
29 2026-08-25 10:04 639232482235303141
593 ms 27.102.138.16
28 2026-08-25 09:46 639232471861770303
609 ms 27.102.138.16
27 2026-08-25 09:29 639232461630217327
619 ms 27.102.138.16
26 2026-08-25 09:12 639232451282965990
603 ms 27.102.138.16
25 2026-08-25 08:55 639232440814614938
295 ms 27.102.138.16
24 2026-08-25 08:37 639232430410720425
609 ms 27.102.138.16
23 2026-08-25 08:20 639232420003096185
7 ms 27.102.138.16
22 2026-08-25 08:03 639232409467287444
603 ms 27.102.138.16
21 2026-08-25 07:45 639232399077195997
4 ms 27.102.138.16
20 2026-08-25 07:28 639232388731528337
305 ms 27.102.138.16
19 2026-08-25 07:10 639232378288598612
601 ms 27.102.138.16
18 2026-08-25 06:17 639232346196373643
616 ms 27.102.138.16
17 2026-08-25 06:00 639232336112370741
597 ms 27.102.138.16
16 2026-08-25 05:43 639232326146508970
1070 ms 27.102.138.16
15 2026-08-25 05:27 639232316189381720
602 ms 27.102.138.16
14 2026-08-25 05:10 639232306217998913
286 ms 27.102.138.16
13 2026-08-25 04:53 639232296255744174
297 ms 27.102.138.16
12 2026-08-25 04:37 639232286095760789
598 ms 27.102.138.16
11 2026-08-25 04:20 639232276086186273
274 ms 27.102.138.16
10 2026-08-25 04:03 639232265900986425
612 ms 27.102.138.16
9 2026-08-25 03:46 639232255723518075
301 ms 27.102.138.16
8 2026-08-25 03:29 639232245484452890
605 ms 27.102.138.16
7 2026-08-25 03:12 639232235157175331
416 ms 27.102.138.16
6 2026-08-25 02:18 639232203197189095
596 ms 27.102.138.16
5 2026-08-25 02:01 639232192844564298
303 ms 27.102.138.16
4 2026-08-25 01:44 639232182496008942
595 ms 27.102.138.16
3 2026-08-25 01:27 639232172197053132
603 ms 27.102.138.16
2 2026-08-25 00:33 639232140250307418
596 ms 27.102.138.16
1 2026-08-25 00:17 639232129927860324
616 ms 27.102.138.16