DNS response history for ns1.claimtv.link

ns1.claimtv.link 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 177 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.claimtv.link.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

177 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

15.197.177.102

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.claimtv.link

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:13 639232492740373468
40 ms 15.197.177.102
29 2026-08-25 09:56 639232482235303141
39 ms 15.197.177.102
28 2026-08-25 09:39 639232471861770303
23 ms 207.174.61.1
27 2026-08-25 09:22 639232461630217327
64 ms 15.197.177.102
26 2026-08-25 09:04 639232451282965990
60 ms 15.197.177.102
25 2026-08-25 08:47 639232440814614938
35 ms 15.197.177.102
24 2026-08-25 08:29 639232430410720425
48 ms 15.197.177.102
23 2026-08-25 08:12 639232420003096185
28 ms 15.197.177.102
22 2026-08-25 07:55 639232409467287444
2051 ms 207.174.61.1
21 2026-08-25 07:37 639232399077195997
15 ms 15.197.177.102
20 2026-08-25 07:20 639232388731528337
28 ms 15.197.177.102
19 2026-08-25 07:03 639232378288598612
39 ms 207.174.61.1
18 2026-08-25 06:09 639232346196373643
88 ms 207.174.61.1
17 2026-08-25 05:52 639232336112370741
21 ms 15.197.177.102
16 2026-08-25 05:36 639232326146508970
28 ms 15.197.177.102
15 2026-08-25 05:19 639232316189381720
40 ms 15.197.177.102
14 2026-08-25 05:03 639232306217998913
33 ms 15.197.177.102
13 2026-08-25 04:46 639232296255744174
10 ms 15.197.177.102
12 2026-08-25 04:29 639232286095760789
81 ms 15.197.177.102
11 2026-08-25 04:12 639232276086186273
62 ms 207.174.61.1
10 2026-08-25 03:55 639232265900986425
27 ms 15.197.177.102
9 2026-08-25 03:38 639232255723518075
2018 ms 207.174.61.1
8 2026-08-25 03:21 639232245484452890
76 ms 15.197.177.102
7 2026-08-25 03:04 639232235157175331
32 ms 15.197.177.102
6 2026-08-25 02:11 639232203197189095
80 ms 15.197.177.102
5 2026-08-25 01:54 639232192844564298
31 ms 15.197.177.102
4 2026-08-25 01:36 639232182496008942
123 ms 15.197.177.102
3 2026-08-25 01:19 639232172197053132
31 ms 15.197.177.102
2 2026-08-25 00:26 639232140250307418
36 ms 15.197.177.102
1 2026-08-25 00:09 639232129927860324
30 ms 15.197.177.102