DNS response history for ns2.ozonenetworks.com

ns2.ozonenetworks.com 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 182 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.ozonenetworks.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

182 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

174.46.240.32

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.ozonenetworks.com

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:35 639232471861770303
53 ms 174.46.240.32
27 2026-08-25 09:18 639232461630217327
12 ms 174.46.240.32
26 2026-08-25 09:00 639232451282965990
55 ms 174.46.240.32
25 2026-08-25 08:43 639232440814614938
44 ms 174.46.240.32
24 2026-08-25 08:26 639232430410720425
18 ms 174.46.240.32
23 2026-08-25 08:08 639232420003096185
12 ms 174.46.240.32
22 2026-08-25 07:51 639232409467287444
17 ms 174.46.240.32
21 2026-08-25 07:33 639232399077195997
31 ms 174.46.240.32
20 2026-08-25 07:16 639232388731528337
32 ms 174.46.240.32
19 2026-08-25 06:59 639232378288598612
2017 ms 174.46.240.32
18 2026-08-25 06:05 639232346196373643
47 ms 174.46.240.32
17 2026-08-25 05:48 639232336112370741
35 ms 174.46.240.32
16 2026-08-25 05:32 639232326146508970
41 ms 174.46.240.32
15 2026-08-25 05:15 639232316189381720
40 ms 174.46.240.32
14 2026-08-25 04:59 639232306217998913
34 ms 174.46.240.32
13 2026-08-25 04:42 639232296255744174
83 ms 174.46.240.32
12 2026-08-25 04:25 639232286095760789
26 ms 174.46.240.32
11 2026-08-25 04:08 639232276086186273
48 ms 174.46.240.32
10 2026-08-25 03:51 639232265900986425
19 ms 174.46.240.32
9 2026-08-25 03:34 639232255723518075
2181 ms 174.46.240.32
8 2026-08-25 03:17 639232245484452890
9 ms 174.46.240.32
7 2026-08-25 03:00 639232235157175331
42 ms 174.46.240.32
6 2026-08-25 02:07 639232203197189095
29 ms 174.46.240.32
5 2026-08-25 01:50 639232192844564298
10 ms 174.46.240.32
4 2026-08-25 01:32 639232182496008942
26 ms 174.46.240.32
3 2026-08-25 01:15 639232172197053132
50 ms 174.46.240.32
2 2026-08-25 00:22 639232140250307418
56 ms 174.46.240.32
1 2026-08-25 00:05 639232129927860324
25 ms 174.46.240.32