DNS response history for ns2.royalty247.be

ns2.royalty247.be 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 41 DNS check records, 41 successful responses, 0 failed responses, and 257 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.royalty247.be.
Records on Selected Date

41

Historical checks stored for this nameserver on selected date

Average Latency

257 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 13:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

77.73.96.93

Most recently resolved hosting IP on selected date

Successful Responses

41

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.royalty247.be

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
41 2026-08-26 13:33 639233476455174682
78 ms 77.73.96.93
40 2026-08-26 13:15 639233466171592605
63 ms 77.73.96.93
39 2026-08-26 12:58 639233455747096265
7 ms 77.73.96.93
38 2026-08-26 12:41 639233445367152284
37 ms 77.73.96.93
37 2026-08-26 12:24 639233434974187439
46 ms 77.73.96.93
36 2026-08-26 12:06 639233424567558554
52 ms 77.73.96.93
35 2026-08-26 11:49 639233414056832719
2075 ms 77.73.96.93
34 2026-08-26 11:31 639233403515141099
82 ms 77.73.96.93
33 2026-08-26 10:36 639233370841350248
68 ms 77.73.96.93
32 2026-08-26 10:19 639233360361507238
114 ms 77.73.96.93
31 2026-08-26 10:02 639233350067824371
131 ms 77.73.96.93
30 2026-08-26 09:45 639233339545274518
35 ms 77.73.96.93
29 2026-08-26 09:27 639233329214918079
84 ms 77.73.96.93
28 2026-08-26 09:10 639233318749762337
93 ms 77.73.96.93
27 2026-08-26 08:53 639233308387917838
95 ms 77.73.96.93
26 2026-08-26 08:35 639233297961740122
71 ms 77.73.96.93
25 2026-08-26 08:18 639233287487159094
2009 ms 77.73.96.93
24 2026-08-26 08:00 639233276995531707
10 ms 77.73.96.93
23 2026-08-26 07:43 639233266521568229
123 ms 77.73.96.93
22 2026-08-26 07:25 639233256081047431
55 ms 77.73.96.93
21 2026-08-26 06:31 639233223620132921
49 ms 77.73.96.93
20 2026-08-26 06:14 639233213287814244
86 ms 77.73.96.93
19 2026-08-26 05:57 639233202925983161
48 ms 77.73.96.93
18 2026-08-26 05:40 639233192644780696
47 ms 77.73.96.93
17 2026-08-26 05:22 639233182401183833
92 ms 77.73.96.93
16 2026-08-26 05:05 639233172074181051
90 ms 77.73.96.93
15 2026-08-26 04:48 639233161808421455
44 ms 77.73.96.93
14 2026-08-26 04:31 639233151357344052
75 ms 77.73.96.93
13 2026-08-26 04:14 639233141034116946
88 ms 77.73.96.93
12 2026-08-26 03:57 639233130828334142
68 ms 77.73.96.93
11 2026-08-26 03:39 639233120373450007
8 ms 77.73.96.93
10 2026-08-26 03:22 639233110066216193
93 ms 77.73.96.93
9 2026-08-26 02:29 639233078065410564
49 ms 77.73.96.93
8 2026-08-26 02:12 639233067787457832
4 ms 77.73.96.93
7 2026-08-26 01:55 639233057501801162
49 ms 77.73.96.93
6 2026-08-26 01:37 639233047089431703
4039 ms 77.73.96.93
5 2026-08-26 01:20 639233036754790688
28 ms 77.73.96.93
4 2026-08-26 01:03 639233026412602472
64 ms 77.73.96.93
3 2026-08-26 00:45 639233016064066127
82 ms 77.73.96.93
2 2026-08-26 00:28 639233005922655772
18 ms 77.73.96.93
1 2026-08-26 00:11 639232995672256907
98 ms 77.73.96.93