DNS response history for ns2.otronivelpdx.net

ns2.otronivelpdx.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 349 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.otronivelpdx.net.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

349 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.160.157.7

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 ns2.otronivelpdx.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:16 639232492740373468
167 ms 108.160.157.7
29 2026-08-25 09:59 639232482235303141
226 ms 108.160.157.7
28 2026-08-25 09:41 639232471861770303
109 ms 108.160.157.7
27 2026-08-25 09:24 639232461630217327
31 ms 108.160.157.7
26 2026-08-25 09:07 639232451282965990
2111 ms 108.160.157.7
25 2026-08-25 08:49 639232440814614938
105 ms 108.160.157.7
24 2026-08-25 08:32 639232430410720425
230 ms 108.160.157.7
23 2026-08-25 08:15 639232420003096185
255 ms 108.160.157.7
22 2026-08-25 07:57 639232409467287444
270 ms 108.160.157.7
21 2026-08-25 07:40 639232399077195997
32 ms 108.160.157.7
20 2026-08-25 07:23 639232388731528337
115 ms 108.160.157.7
19 2026-08-25 07:05 639232378288598612
219 ms 108.160.157.7
18 2026-08-25 06:12 639232346196373643
2117 ms 108.160.157.7
17 2026-08-25 05:55 639232336112370741
156 ms 108.160.157.7
16 2026-08-25 05:38 639232326146508970
8 ms 108.160.157.7
15 2026-08-25 05:22 639232316189381720
110 ms 108.160.157.7
14 2026-08-25 05:05 639232306217998913
111 ms 108.160.157.7
13 2026-08-25 04:48 639232296255744174
222 ms 108.160.157.7
12 2026-08-25 04:32 639232286095760789
221 ms 108.160.157.7
11 2026-08-25 04:15 639232276086186273
226 ms 108.160.157.7
10 2026-08-25 03:58 639232265900986425
108 ms 108.160.157.7
9 2026-08-25 03:41 639232255723518075
128 ms 108.160.157.7
8 2026-08-25 03:24 639232245484452890
112 ms 108.160.157.7
7 2026-08-25 03:07 639232235157175331
108 ms 108.160.157.7
6 2026-08-25 02:13 639232203197189095
167 ms 108.160.157.7
5 2026-08-25 01:56 639232192844564298
2118 ms 108.160.157.7
4 2026-08-25 01:39 639232182496008942
118 ms 108.160.157.7
3 2026-08-25 01:22 639232172197053132
119 ms 108.160.157.7
2 2026-08-25 00:28 639232140250307418
238 ms 108.160.157.7
1 2026-08-25 00:11 639232129927860324
220 ms 108.160.157.7