DNS response history for auth-velonetar-2.planisys.io

auth-velonetar-2.planisys.io 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 715 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 auth-velonetar-2.planisys.io.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

715 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

131.108.40.201

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 auth-velonetar-2.planisys.io

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:59 639232482235303141
109 ms 131.108.40.201
28 2026-08-25 09:42 639232471861770303
207 ms 131.108.40.201
27 2026-08-25 09:25 639232461630217327
214 ms 131.108.40.201
26 2026-08-25 09:07 639232451282965990
213 ms 131.108.40.201
25 2026-08-25 08:50 639232440814614938
388 ms 131.108.40.201
24 2026-08-25 08:33 639232430410720425
337 ms 131.108.40.201
23 2026-08-25 08:15 639232420003096185
216 ms 131.108.40.201
22 2026-08-25 07:58 639232409467287444
109 ms 131.108.40.201
21 2026-08-25 07:40 639232399077195997
96 ms 131.108.40.201
20 2026-08-25 07:23 639232388731528337
42 ms 131.108.40.201
19 2026-08-25 07:06 639232378288598612
3142 ms 131.108.40.201
18 2026-08-25 06:12 639232346196373643
332 ms 131.108.40.201
17 2026-08-25 05:55 639232336112370741
330 ms 131.108.40.201
16 2026-08-25 05:39 639232326146508970
222 ms 131.108.40.201
15 2026-08-25 05:22 639232316189381720
2193 ms 131.108.40.201
14 2026-08-25 05:06 639232306217998913
223 ms 131.108.40.201
13 2026-08-25 04:49 639232296255744174
2093 ms 131.108.40.201
12 2026-08-25 04:32 639232286095760789
105 ms 131.108.40.201
11 2026-08-25 04:15 639232276086186273
221 ms 131.108.40.201
10 2026-08-25 03:58 639232265900986425
2092 ms 131.108.40.201
9 2026-08-25 03:42 639232255723518075
2141 ms 131.108.40.201
8 2026-08-25 03:24 639232245484452890
484 ms 131.108.40.201
7 2026-08-25 03:07 639232235157175331
205 ms 131.108.40.201
6 2026-08-25 02:14 639232203197189095
114 ms 131.108.40.201
5 2026-08-25 01:57 639232192844564298
138 ms 131.108.40.201
4 2026-08-25 01:39 639232182496008942
106 ms 131.108.40.201
3 2026-08-25 01:22 639232172197053132
4218 ms 131.108.40.201
2 2026-08-25 00:29 639232140250307418
213 ms 131.108.40.201
1 2026-08-25 00:12 639232129927860324
239 ms 131.108.40.201