DNS response history for ns3.infosky.net

ns3.infosky.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 2165 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.infosky.net.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

2165 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

195.250.98.23

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 ns3.infosky.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 09:49 639232471861770303
2007 ms 195.250.98.23
28 2026-08-25 09:32 639232461630217327
2009 ms 195.250.98.23
27 2026-08-25 09:15 639232451282965990
2010 ms 195.250.98.23
26 2026-08-25 08:57 639232440814614938
2009 ms 195.250.98.23
25 2026-08-25 08:40 639232430410720425
2049 ms 195.250.98.23
24 2026-08-25 08:23 639232420003096185
2008 ms 195.250.98.23
23 2026-08-25 08:05 639232409467287444
2069 ms 195.250.98.23
22 2026-08-25 07:48 639232399077195997
2010 ms 195.250.98.23
21 2026-08-25 07:30 639232388731528337
2015 ms 195.250.98.23
20 2026-08-25 07:13 639232378288598612
2032 ms 195.250.98.23
19 2026-08-25 06:19 639232346196373643
2050 ms 195.250.98.23
18 2026-08-25 06:02 639232336112370741
2032 ms 195.250.98.23
17 2026-08-25 05:45 639232326146508970
2031 ms 195.250.98.23
16 2026-08-25 05:29 639232316189381720
4045 ms 195.250.98.23
15 2026-08-25 05:12 639232306217998913
2008 ms 195.250.98.23
14 2026-08-25 04:56 639232296255744174
2032 ms 195.250.98.23
13 2026-08-25 04:39 639232286095760789
2011 ms 195.250.98.23
12 2026-08-25 04:22 639232276086186273
4074 ms 195.250.98.23
11 2026-08-25 04:05 639232265900986425
2007 ms 195.250.98.23
10 2026-08-25 03:49 639232255723518075
2035 ms 195.250.98.23
9 2026-08-25 03:31 639232245484452890
2009 ms 195.250.98.23
8 2026-08-25 03:14 639232235157175331
2052 ms 195.250.98.23
7 2026-08-25 02:21 639232203197189095
2009 ms 195.250.98.23
6 2026-08-25 02:04 639232192844564298
2036 ms 195.250.98.23
5 2026-08-25 01:47 639232182496008942
2008 ms 195.250.98.23
4 2026-08-25 01:29 639232172197053132
2044 ms 195.250.98.23
3 2026-08-25 00:36 639232140250307418
2044 ms 195.250.98.23
2 2026-08-25 00:19 639232129927860324
2030 ms 195.250.98.23
1 2026-08-25 00:02 639232119551972438
2008 ms 195.250.98.23