DNS response history for ns2.orvaburn.org

ns2.orvaburn.org 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 602 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.orvaburn.org.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

602 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.38.158.157

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.orvaburn.org

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:14 639232492740373468
2017 ms 51.38.158.157
29 2026-08-25 09:57 639232482235303141
54 ms 51.38.158.157
28 2026-08-25 09:39 639232471861770303
2053 ms 51.38.158.157
27 2026-08-25 09:22 639232461630217327
170 ms 51.38.158.157
26 2026-08-25 09:05 639232451282965990
30 ms 51.38.158.157
25 2026-08-25 08:47 639232440814614938
36 ms 51.38.158.157
24 2026-08-25 08:30 639232430410720425
58 ms 51.38.158.157
23 2026-08-25 08:13 639232420003096185
84 ms 51.38.158.157
22 2026-08-25 07:55 639232409467287444
34 ms 51.38.158.157
21 2026-08-25 07:38 639232399077195997
185 ms 51.38.158.157
20 2026-08-25 07:21 639232388731528337
35 ms 51.38.158.157
19 2026-08-25 07:03 639232378288598612
93 ms 51.38.158.157
18 2026-08-25 06:10 639232346196373643
65 ms 51.38.158.157
17 2026-08-25 05:53 639232336112370741
2024 ms 51.38.158.157
16 2026-08-25 05:36 639232326146508970
177 ms 51.38.158.157
15 2026-08-25 05:20 639232316189381720
2038 ms 51.38.158.157
14 2026-08-25 05:03 639232306217998913
58 ms 51.38.158.157
13 2026-08-25 04:47 639232296255744174
78 ms 51.38.158.157
12 2026-08-25 04:30 639232286095760789
2048 ms 51.38.158.157
11 2026-08-25 04:13 639232276086186273
44 ms 51.38.158.157
10 2026-08-25 03:56 639232265900986425
2154 ms 51.38.158.157
9 2026-08-25 03:39 639232255723518075
31 ms 51.38.158.157
8 2026-08-25 03:22 639232245484452890
94 ms 51.38.158.157
7 2026-08-25 03:05 639232235157175331
69 ms 51.38.158.157
6 2026-08-25 02:11 639232203197189095
2029 ms 51.38.158.157
5 2026-08-25 01:54 639232192844564298
77 ms 51.38.158.157
4 2026-08-25 01:37 639232182496008942
59 ms 51.38.158.157
3 2026-08-25 01:20 639232172197053132
65 ms 51.38.158.157
2 2026-08-25 00:26 639232140250307418
2039 ms 51.38.158.157
1 2026-08-25 00:09 639232129927860324
70 ms 51.38.158.157