DNS response history for ns2.royal-opalo.com

ns2.royal-opalo.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-26. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 235 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.royal-opalo.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

235 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:55

All timestamps shown in UTC

Latest Resolved IP on Selected Date

80.71.157.99

Most recently resolved hosting IP on selected date

Successful Responses

36

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.royal-opalo.com

Showing DNS history for 2026-08-26 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
36 2026-08-26 11:55 639233414056832719
26 ms 80.71.157.99
35 2026-08-26 11:37 639233403515141099
37 ms 80.71.157.99
34 2026-08-26 10:43 639233370841350248
2028 ms 80.71.157.99
33 2026-08-26 10:26 639233360361507238
33 ms 80.71.157.99
32 2026-08-26 10:08 639233350067824371
34 ms 80.71.157.99
31 2026-08-26 09:51 639233339545274518
2030 ms 80.71.157.99
30 2026-08-26 09:33 639233329214918079
14 ms 80.71.157.99
29 2026-08-26 09:16 639233318749762337
31 ms 80.71.157.99
28 2026-08-26 08:59 639233308387917838
14 ms 80.71.157.99
27 2026-08-26 08:41 639233297961740122
22 ms 80.71.157.99
26 2026-08-26 08:24 639233287487159094
14 ms 80.71.157.99
25 2026-08-26 08:07 639233276995531707
29 ms 80.71.157.99
24 2026-08-26 07:49 639233266521568229
27 ms 80.71.157.99
23 2026-08-26 07:31 639233256081047431
24 ms 80.71.157.99
22 2026-08-26 06:38 639233223620132921
20 ms 80.71.157.99
21 2026-08-26 06:20 639233213287814244
20 ms 80.71.157.99
20 2026-08-26 06:03 639233202925983161
19 ms 80.71.157.99
19 2026-08-26 05:46 639233192644780696
17 ms 80.71.157.99
18 2026-08-26 05:29 639233182401183833
26 ms 80.71.157.99
17 2026-08-26 05:12 639233172074181051
15 ms 80.71.157.99
16 2026-08-26 04:54 639233161808421455
27 ms 80.71.157.99
15 2026-08-26 04:37 639233151357344052
26 ms 80.71.157.99
14 2026-08-26 04:20 639233141034116946
1522 ms 80.71.157.99
13 2026-08-26 04:03 639233130828334142
29 ms 80.71.157.99
12 2026-08-26 03:45 639233120373450007
21 ms 80.71.157.99
11 2026-08-26 03:28 639233110066216193
23 ms 80.71.157.99
10 2026-08-26 02:35 639233078065410564
10 ms 80.71.157.99
9 2026-08-26 02:18 639233067787457832
26 ms 80.71.157.99
8 2026-08-26 02:00 639233057501801162
14 ms 80.71.157.99
7 2026-08-26 01:43 639233047089431703
37 ms 80.71.157.99
6 2026-08-26 01:26 639233036754790688
10 ms 80.71.157.99
5 2026-08-26 01:09 639233026412602472
17 ms 80.71.157.99
4 2026-08-26 00:51 639233016064066127
19 ms 80.71.157.99
3 2026-08-26 00:34 639233005922655772
165 ms 80.71.157.99
2 2026-08-26 00:17 639232995672256907
2021 ms 80.71.157.99
1 2026-08-26 00:00 639232985300872416
27 ms 80.71.157.99