DNS response history for ns2.infocan.net

ns2.infocan.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 29 DNS check records, 29 successful responses, 0 failed responses, and 621 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.infocan.net.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

621 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

20.239.123.16

Most recently resolved hosting IP on selected date

Successful Responses

29

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.infocan.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
29 2026-08-25 10:02 639232482235303141
383 ms 20.239.123.16
28 2026-08-25 09:45 639232471861770303
387 ms 20.239.123.16
27 2026-08-25 09:28 639232461630217327
397 ms 20.239.123.16
26 2026-08-25 09:10 639232451282965990
200 ms 20.239.123.16
25 2026-08-25 08:53 639232440814614938
195 ms 20.239.123.16
24 2026-08-25 08:36 639232430410720425
2295 ms 20.239.123.16
23 2026-08-25 08:18 639232420003096185
15 ms 20.239.123.16
22 2026-08-25 08:01 639232409467287444
389 ms 20.239.123.16
21 2026-08-25 07:43 639232399077195997
226 ms 20.239.123.16
20 2026-08-25 07:26 639232388731528337
381 ms 20.239.123.16
19 2026-08-25 07:09 639232378288598612
386 ms 20.239.123.16
18 2026-08-25 06:15 639232346196373643
392 ms 20.239.123.16
17 2026-08-25 05:58 639232336112370741
386 ms 20.239.123.16
16 2026-08-25 05:42 639232326146508970
4242 ms 20.239.123.16
15 2026-08-25 05:25 639232316189381720
2010 ms 20.239.123.16
14 2026-08-25 05:09 639232306217998913
380 ms 20.239.123.16
13 2026-08-25 04:52 639232296255744174
225 ms 20.239.123.16
12 2026-08-25 04:35 639232286095760789
382 ms 20.239.123.16
11 2026-08-25 04:18 639232276086186273
258 ms 20.239.123.16
10 2026-08-25 04:01 639232265900986425
191 ms 20.239.123.16
9 2026-08-25 03:45 639232255723518075
2239 ms 20.239.123.16
8 2026-08-25 03:27 639232245484452890
33 ms 20.239.123.16
7 2026-08-25 03:10 639232235157175331
382 ms 20.239.123.16
6 2026-08-25 02:17 639232203197189095
31 ms 20.239.123.16
5 2026-08-25 02:00 639232192844564298
245 ms 20.239.123.16
4 2026-08-25 01:43 639232182496008942
388 ms 20.239.123.16
3 2026-08-25 01:25 639232172197053132
381 ms 20.239.123.16
2 2026-08-25 00:32 639232140250307418
395 ms 20.239.123.16
1 2026-08-25 00:15 639232129927860324
193 ms 20.239.123.16