DNS response history for ns3.cleartechnologies.net

ns3.cleartechnologies.net 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, 33 successful responses, 0 failed responses, and 246 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 ns3.cleartechnologies.net.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

246 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

40.119.49.201

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns3.cleartechnologies.net

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:49 639232545839529039
259 ms 40.119.49.201
32 2026-08-25 11:31 639232535349285207
261 ms 40.119.49.201
31 2026-08-25 11:14 639232524938080723
258 ms 40.119.49.201
30 2026-08-25 10:20 639232492740373468
260 ms 40.119.49.201
29 2026-08-25 10:03 639232482235303141
261 ms 40.119.49.201
28 2026-08-25 09:45 639232471861770303
267 ms 40.119.49.201
27 2026-08-25 09:28 639232461630217327
266 ms 40.119.49.201
26 2026-08-25 09:11 639232451282965990
258 ms 40.119.49.201
25 2026-08-25 08:54 639232440814614938
263 ms 40.119.49.201
24 2026-08-25 08:36 639232430410720425
263 ms 40.119.49.201
23 2026-08-25 08:19 639232420003096185
254 ms 40.119.49.201
22 2026-08-25 08:02 639232409467287444
259 ms 40.119.49.201
21 2026-08-25 07:44 639232399077195997
257 ms 40.119.49.201
20 2026-08-25 07:27 639232388731528337
253 ms 40.119.49.201
19 2026-08-25 07:09 639232378288598612
266 ms 40.119.49.201
18 2026-08-25 06:16 639232346196373643
260 ms 40.119.49.201
17 2026-08-25 05:59 639232336112370741
260 ms 40.119.49.201
16 2026-08-25 05:42 639232326146508970
4 ms 40.119.49.201
15 2026-08-25 05:26 639232316189381720
262 ms 40.119.49.201
14 2026-08-25 05:09 639232306217998913
269 ms 40.119.49.201
13 2026-08-25 04:53 639232296255744174
254 ms 40.119.49.201
12 2026-08-25 04:36 639232286095760789
259 ms 40.119.49.201
11 2026-08-25 04:19 639232276086186273
260 ms 40.119.49.201
10 2026-08-25 04:02 639232265900986425
274 ms 40.119.49.201
9 2026-08-25 03:45 639232255723518075
257 ms 40.119.49.201
8 2026-08-25 03:28 639232245484452890
258 ms 40.119.49.201
7 2026-08-25 03:11 639232235157175331
268 ms 40.119.49.201
6 2026-08-25 02:18 639232203197189095
261 ms 40.119.49.201
5 2026-08-25 02:01 639232192844564298
264 ms 40.119.49.201
4 2026-08-25 01:43 639232182496008942
258 ms 40.119.49.201
3 2026-08-25 01:26 639232172197053132
257 ms 40.119.49.201
2 2026-08-25 00:33 639232140250307418
291 ms 40.119.49.201
1 2026-08-25 00:16 639232129927860324
2 ms 40.119.49.201