DNS response history for ns1.clearlytravel.com

ns1.clearlytravel.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 33 DNS check records, 32 successful responses, 1 failed responses, and 260 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.clearlytravel.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

260 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.163.16.20

Most recently resolved hosting IP on selected date

Successful Responses

32

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.clearlytravel.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
33 2026-08-25 11:40 639232545839529039
113 ms 185.163.16.20
32 2026-08-25 11:23 639232535349285207
53 ms 185.163.16.20
31 2026-08-25 11:05 639232524938080723
101 ms 185.163.16.20
30 2026-08-25 10:12 639232492740373468
128 ms 185.163.16.20
29 2026-08-25 09:54 639232482235303141
67 ms 185.163.16.20
28 2026-08-25 09:37 639232471861770303
50 ms 185.163.16.20
27 2026-08-25 09:20 639232461630217327
52 ms 185.163.16.20
26 2026-08-25 09:03 639232451282965990
97 ms 185.163.16.20
25 2026-08-25 08:45 639232440814614938
47 ms 185.163.16.20
24 2026-08-25 08:28 639232430410720425
2068 ms 185.163.16.20
23 2026-08-25 08:11 639232420003096185
87 ms 185.163.16.20
22 2026-08-25 07:53 639232409467287444
10 ms 185.163.16.20
21 2026-08-25 07:36 639232399077195997
92 ms 185.163.16.20
20 2026-08-25 07:18 639232388731528337
2047 ms 185.163.16.20
19 2026-08-25 07:01 639232378288598612
109 ms 185.163.16.20
18 2026-08-25 06:07 639232346196373643
92 ms 185.163.16.20
17 2026-08-25 05:51 639232336112370741
115 ms 185.163.16.20
16 2026-08-25 05:34 639232326146508970
102 ms 185.163.16.20
15 2026-08-25 05:17 639232316189381720
43 ms 185.163.16.20
14 2026-08-25 05:01 639232306217998913
5 ms 185.163.16.20
13 2026-08-25 04:44 639232296255744174
87 ms 185.163.16.20
12 2026-08-25 04:27 639232286095760789
91 ms 185.163.16.20
11 2026-08-25 04:11 639232276086186273
136 ms 185.163.16.20
10 2026-08-25 03:54 639232265900986425
2060 ms 185.163.16.20
9 2026-08-25 03:37 639232255723518075
120 ms 185.163.16.20
8 2026-08-25 03:20 639232245484452890
23 ms 185.163.16.20
7 2026-08-25 03:02 639232235157175331
-
6 2026-08-25 02:09 639232203197189095
89 ms 185.163.16.20
5 2026-08-25 01:52 639232192844564298
90 ms 185.163.16.20
4 2026-08-25 01:35 639232182496008942
7 ms 185.163.16.20
3 2026-08-25 01:17 639232172197053132
46 ms 185.163.16.20
2 2026-08-25 00:24 639232140250307418
9 ms 185.163.16.20
1 2026-08-25 00:07 639232129927860324
68 ms 185.163.16.20