DNS response history for ns2.inleads.cloud

ns2.inleads.cloud 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 466 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 ns2.inleads.cloud.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

466 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

72.61.114.2

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 ns2.inleads.cloud

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:19 639232492740373468
329 ms 72.61.114.2
29 2026-08-25 10:02 639232482235303141
10 ms 72.61.114.2
28 2026-08-25 09:44 639232471861770303
26 ms 72.61.114.2
27 2026-08-25 09:27 639232461630217327
338 ms 72.61.114.2
26 2026-08-25 09:10 639232451282965990
321 ms 72.61.114.2
25 2026-08-25 08:52 639232440814614938
174 ms 72.61.114.2
24 2026-08-25 08:35 639232430410720425
162 ms 72.61.114.2
23 2026-08-25 08:18 639232420003096185
228 ms 72.61.114.2
22 2026-08-25 08:00 639232409467287444
326 ms 72.61.114.2
21 2026-08-25 07:43 639232399077195997
161 ms 72.61.114.2
20 2026-08-25 07:25 639232388731528337
159 ms 72.61.114.2
19 2026-08-25 07:08 639232378288598612
2007 ms 72.61.114.2
18 2026-08-25 06:14 639232346196373643
159 ms 72.61.114.2
17 2026-08-25 05:57 639232336112370741
340 ms 72.61.114.2
16 2026-08-25 05:41 639232326146508970
324 ms 72.61.114.2
15 2026-08-25 05:24 639232316189381720
10 ms 72.61.114.2
14 2026-08-25 05:08 639232306217998913
325 ms 72.61.114.2
13 2026-08-25 04:51 639232296255744174
2009 ms 72.61.114.2
12 2026-08-25 04:34 639232286095760789
160 ms 72.61.114.2
11 2026-08-25 04:17 639232276086186273
324 ms 72.61.114.2
10 2026-08-25 04:01 639232265900986425
327 ms 72.61.114.2
9 2026-08-25 03:44 639232255723518075
8 ms 72.61.114.2
8 2026-08-25 03:27 639232245484452890
332 ms 72.61.114.2
7 2026-08-25 03:09 639232235157175331
11 ms 72.61.114.2
6 2026-08-25 02:16 639232203197189095
3 ms 72.61.114.2
5 2026-08-25 01:59 639232192844564298
324 ms 72.61.114.2
4 2026-08-25 01:42 639232182496008942
319 ms 72.61.114.2
3 2026-08-25 01:24 639232172197053132
4276 ms 72.61.114.2
2 2026-08-25 00:31 639232140250307418
169 ms 72.61.114.2
1 2026-08-25 00:14 639232129927860324
320 ms 72.61.114.2