DNS response history for ns3.linksky.net

ns3.linksky.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-26. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 536 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.linksky.net.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

536 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.69.222.103

Most recently resolved hosting IP on selected date

Successful Responses

38

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.linksky.net

Showing DNS history for 2026-08-26 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
38 2026-08-26 12:30 639233434974187439
229 ms 208.69.222.103
37 2026-08-26 12:12 639233424567558554
2111 ms 208.69.222.103
36 2026-08-26 11:55 639233414056832719
120 ms 208.69.222.103
35 2026-08-26 11:37 639233403515141099
358 ms 208.69.222.103
34 2026-08-26 10:43 639233370841350248
155 ms 208.69.222.103
33 2026-08-26 10:26 639233360361507238
115 ms 208.69.222.103
32 2026-08-26 10:08 639233350067824371
473 ms 208.69.222.103
31 2026-08-26 09:51 639233339545274518
133 ms 208.69.222.103
30 2026-08-26 09:33 639233329214918079
2115 ms 208.69.222.103
29 2026-08-26 09:16 639233318749762337
226 ms 208.69.222.103
28 2026-08-26 08:59 639233308387917838
456 ms 208.69.222.103
27 2026-08-26 08:41 639233297961740122
2114 ms 208.69.222.103
26 2026-08-26 08:24 639233287487159094
124 ms 208.69.222.103
25 2026-08-26 08:07 639233276995531707
348 ms 208.69.222.103
24 2026-08-26 07:49 639233266521568229
2138 ms 208.69.222.103
23 2026-08-26 07:31 639233256081047431
232 ms 208.69.222.103
22 2026-08-26 06:38 639233223620132921
236 ms 208.69.222.103
21 2026-08-26 06:20 639233213287814244
115 ms 208.69.222.103
20 2026-08-26 06:03 639233202925983161
2124 ms 208.69.222.103
19 2026-08-26 05:46 639233192644780696
117 ms 208.69.222.103
18 2026-08-26 05:29 639233182401183833
113 ms 208.69.222.103
17 2026-08-26 05:12 639233172074181051
221 ms 208.69.222.103
16 2026-08-26 04:54 639233161808421455
344 ms 208.69.222.103
15 2026-08-26 04:37 639233151357344052
455 ms 208.69.222.103
14 2026-08-26 04:20 639233141034116946
161 ms 208.69.222.103
13 2026-08-26 04:03 639233130828334142
118 ms 208.69.222.103
12 2026-08-26 03:45 639233120373450007
351 ms 208.69.222.103
11 2026-08-26 03:28 639233110066216193
464 ms 208.69.222.103
10 2026-08-26 02:35 639233078065410564
3 ms 208.69.222.103
9 2026-08-26 02:18 639233067787457832
125 ms 208.69.222.103
8 2026-08-26 02:00 639233057501801162
352 ms 208.69.222.103
7 2026-08-26 01:43 639233047089431703
475 ms 208.69.222.103
6 2026-08-26 01:26 639233036754790688
129 ms 208.69.222.103
5 2026-08-26 01:09 639233026412602472
344 ms 208.69.222.103
4 2026-08-26 00:51 639233016064066127
339 ms 208.69.222.103
3 2026-08-26 00:34 639233005922655772
228 ms 208.69.222.103
2 2026-08-26 00:17 639232995672256907
7 ms 208.69.222.103
1 2026-08-26 00:00 639232985300872416
2108 ms 208.69.222.103