DNS response history for ns2.oveoweb.net

ns2.oveoweb.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 28 DNS check records, 28 successful responses, 0 failed responses, and 146 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.oveoweb.net.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

146 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

212.154.38.198

Most recently resolved hosting IP on selected date

Successful Responses

28

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.oveoweb.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
28 2026-08-25 09:38 639232471861770303
85 ms 212.154.38.198
27 2026-08-25 09:21 639232461630217327
94 ms 212.154.38.198
26 2026-08-25 09:04 639232451282965990
56 ms 212.154.38.198
25 2026-08-25 08:47 639232440814614938
83 ms 212.154.38.198
24 2026-08-25 08:29 639232430410720425
79 ms 212.154.38.198
23 2026-08-25 08:12 639232420003096185
52 ms 212.154.38.198
22 2026-08-25 07:55 639232409467287444
93 ms 212.154.38.198
21 2026-08-25 07:37 639232399077195997
62 ms 212.154.38.198
20 2026-08-25 07:20 639232388731528337
65 ms 212.154.38.198
19 2026-08-25 07:03 639232378288598612
73 ms 212.154.38.198
18 2026-08-25 06:09 639232346196373643
94 ms 212.154.38.198
17 2026-08-25 05:52 639232336112370741
79 ms 212.154.38.198
16 2026-08-25 05:36 639232326146508970
78 ms 212.154.38.198
15 2026-08-25 05:19 639232316189381720
74 ms 212.154.38.198
14 2026-08-25 05:03 639232306217998913
97 ms 212.154.38.198
13 2026-08-25 04:46 639232296255744174
2045 ms 212.154.38.198
12 2026-08-25 04:29 639232286095760789
93 ms 212.154.38.198
11 2026-08-25 04:12 639232276086186273
59 ms 212.154.38.198
10 2026-08-25 03:55 639232265900986425
74 ms 212.154.38.198
9 2026-08-25 03:38 639232255723518075
80 ms 212.154.38.198
8 2026-08-25 03:21 639232245484452890
73 ms 212.154.38.198
7 2026-08-25 03:04 639232235157175331
55 ms 212.154.38.198
6 2026-08-25 02:11 639232203197189095
112 ms 212.154.38.198
5 2026-08-25 01:54 639232192844564298
73 ms 212.154.38.198
4 2026-08-25 01:36 639232182496008942
74 ms 212.154.38.198
3 2026-08-25 01:19 639232172197053132
55 ms 212.154.38.198
2 2026-08-25 00:26 639232140250307418
76 ms 212.154.38.198
1 2026-08-25 00:09 639232129927860324
44 ms 212.154.38.198