DNS response history for ns2.ovay.net

ns2.ovay.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 318 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.ovay.net.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

318 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

35.230.66.106

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.ovay.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:03 639232482235303141
402 ms 35.230.66.106
28 2026-08-25 09:45 639232471861770303
5 ms 35.230.66.106
27 2026-08-25 09:28 639232461630217327
429 ms 35.230.66.106
26 2026-08-25 09:11 639232451282965990
256 ms 35.230.66.106
25 2026-08-25 08:54 639232440814614938
395 ms 35.230.66.106
24 2026-08-25 08:36 639232430410720425
259 ms 35.230.66.106
23 2026-08-25 08:19 639232420003096185
431 ms 35.230.66.106
22 2026-08-25 08:02 639232409467287444
422 ms 35.230.66.106
21 2026-08-25 07:44 639232399077195997
167 ms 35.230.66.106
20 2026-08-25 07:27 639232388731528337
403 ms 35.230.66.106
19 2026-08-25 07:09 639232378288598612
412 ms 35.230.66.106
18 2026-08-25 06:16 639232346196373643
411 ms 35.230.66.106
17 2026-08-25 05:59 639232336112370741
5 ms 35.230.66.106
16 2026-08-25 05:42 639232326146508970
434 ms 35.230.66.106
15 2026-08-25 05:26 639232316189381720
422 ms 35.230.66.106
14 2026-08-25 05:09 639232306217998913
813 ms 35.230.66.106
13 2026-08-25 04:52 639232296255744174
257 ms 35.230.66.106
12 2026-08-25 04:36 639232286095760789
3 ms 35.230.66.106
11 2026-08-25 04:19 639232276086186273
177 ms 35.230.66.106
10 2026-08-25 04:02 639232265900986425
247 ms 35.230.66.106
9 2026-08-25 03:45 639232255723518075
182 ms 35.230.66.106
8 2026-08-25 03:28 639232245484452890
442 ms 35.230.66.106
7 2026-08-25 03:11 639232235157175331
430 ms 35.230.66.106
6 2026-08-25 02:18 639232203197189095
397 ms 35.230.66.106
5 2026-08-25 02:01 639232192844564298
427 ms 35.230.66.106
4 2026-08-25 01:43 639232182496008942
173 ms 35.230.66.106
3 2026-08-25 01:26 639232172197053132
423 ms 35.230.66.106
2 2026-08-25 00:33 639232140250307418
4 ms 35.230.66.106
1 2026-08-25 00:16 639232129927860324
395 ms 35.230.66.106