DNS response history for ns1.onlink.net

ns1.onlink.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 30 DNS check records, 30 successful responses, 0 failed responses, and 513 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 ns1.onlink.net.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

513 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

206.108.253.70

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 ns1.onlink.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
30 2026-08-25 10:17 639232492740373468
112 ms 206.108.253.70
29 2026-08-25 10:00 639232482235303141
123 ms 206.108.253.70
28 2026-08-25 09:42 639232471861770303
14 ms 206.108.253.70
27 2026-08-25 09:25 639232461630217327
251 ms 206.108.253.70
26 2026-08-25 09:08 639232451282965990
242 ms 206.108.253.70
25 2026-08-25 08:50 639232440814614938
238 ms 206.108.253.70
24 2026-08-25 08:33 639232430410720425
4145 ms 206.108.253.70
23 2026-08-25 08:16 639232420003096185
7 ms 206.108.253.70
22 2026-08-25 07:58 639232409467287444
245 ms 206.108.253.70
21 2026-08-25 07:41 639232399077195997
233 ms 206.108.253.70
20 2026-08-25 07:23 639232388731528337
2248 ms 206.108.253.70
19 2026-08-25 07:06 639232378288598612
120 ms 206.108.253.70
18 2026-08-25 06:12 639232346196373643
2120 ms 206.108.253.70
17 2026-08-25 05:55 639232336112370741
124 ms 206.108.253.70
16 2026-08-25 05:39 639232326146508970
2008 ms 206.108.253.70
15 2026-08-25 05:22 639232316189381720
246 ms 206.108.253.70
14 2026-08-25 05:06 639232306217998913
122 ms 206.108.253.70
13 2026-08-25 04:49 639232296255744174
264 ms 206.108.253.70
12 2026-08-25 04:32 639232286095760789
244 ms 206.108.253.70
11 2026-08-25 04:15 639232276086186273
177 ms 206.108.253.70
10 2026-08-25 03:59 639232265900986425
122 ms 206.108.253.70
9 2026-08-25 03:42 639232255723518075
248 ms 206.108.253.70
8 2026-08-25 03:25 639232245484452890
252 ms 206.108.253.70
7 2026-08-25 03:07 639232235157175331
247 ms 206.108.253.70
6 2026-08-25 02:14 639232203197189095
242 ms 206.108.253.70
5 2026-08-25 01:57 639232192844564298
127 ms 206.108.253.70
4 2026-08-25 01:40 639232182496008942
130 ms 206.108.253.70
3 2026-08-25 01:22 639232172197053132
253 ms 206.108.253.70
2 2026-08-25 00:29 639232140250307418
241 ms 206.108.253.70
1 2026-08-25 00:12 639232129927860324
244 ms 206.108.253.70