DNS response history for ns1.clm-connect.com

ns1.clm-connect.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 339 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.clm-connect.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

339 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.49.247.91

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.clm-connect.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:16 639232492740373468
4 ms 69.49.247.91
29 2026-08-25 09:59 639232482235303141
250 ms 69.49.247.91
28 2026-08-25 09:42 639232471861770303
236 ms 69.49.247.91
27 2026-08-25 09:25 639232461630217327
260 ms 69.49.247.91
26 2026-08-25 09:07 639232451282965990
2113 ms 69.49.247.91
25 2026-08-25 08:50 639232440814614938
236 ms 69.49.247.91
24 2026-08-25 08:33 639232430410720425
124 ms 69.49.247.91
23 2026-08-25 08:15 639232420003096185
136 ms 69.49.247.91
22 2026-08-25 07:58 639232409467287444
236 ms 69.49.247.91
21 2026-08-25 07:40 639232399077195997
235 ms 69.49.247.91
20 2026-08-25 07:23 639232388731528337
242 ms 69.49.247.91
19 2026-08-25 07:06 639232378288598612
238 ms 69.49.247.91
18 2026-08-25 06:12 639232346196373643
2125 ms 69.49.247.91
17 2026-08-25 05:55 639232336112370741
3 ms 69.49.247.91
16 2026-08-25 05:39 639232326146508970
259 ms 69.49.247.91
15 2026-08-25 05:22 639232316189381720
235 ms 69.49.247.91
14 2026-08-25 05:06 639232306217998913
118 ms 69.49.247.91
13 2026-08-25 04:49 639232296255744174
281 ms 69.49.247.91
12 2026-08-25 04:32 639232286095760789
251 ms 69.49.247.91
11 2026-08-25 04:15 639232276086186273
241 ms 69.49.247.91
10 2026-08-25 03:58 639232265900986425
147 ms 69.49.247.91
9 2026-08-25 03:41 639232255723518075
250 ms 69.49.247.91
8 2026-08-25 03:24 639232245484452890
234 ms 69.49.247.91
7 2026-08-25 03:07 639232235157175331
237 ms 69.49.247.91
6 2026-08-25 02:14 639232203197189095
236 ms 69.49.247.91
5 2026-08-25 01:57 639232192844564298
296 ms 69.49.247.91
4 2026-08-25 01:39 639232182496008942
238 ms 69.49.247.91
3 2026-08-25 01:22 639232172197053132
239 ms 69.49.247.91
2 2026-08-25 00:29 639232140250307418
249 ms 69.49.247.91
1 2026-08-25 00:12 639232129927860324
231 ms 69.49.247.91