DNS response history for ns2.royalzar.com

ns2.royalzar.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 29 DNS check records, 29 successful responses, 0 failed responses, and 336 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.royalzar.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

336 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.129.168.114

Most recently resolved hosting IP on selected date

Successful Responses

29

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.royalzar.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
29 2026-08-26 09:31 639233329214918079
180 ms 185.129.168.114
28 2026-08-26 09:14 639233318749762337
186 ms 185.129.168.114
27 2026-08-26 08:57 639233308387917838
178 ms 185.129.168.114
26 2026-08-26 08:39 639233297961740122
200 ms 185.129.168.114
25 2026-08-26 08:22 639233287487159094
2189 ms 185.129.168.114
24 2026-08-26 08:04 639233276995531707
201 ms 185.129.168.114
23 2026-08-26 07:47 639233266521568229
183 ms 185.129.168.114
22 2026-08-26 07:29 639233256081047431
179 ms 185.129.168.114
21 2026-08-26 06:35 639233223620132921
2140 ms 185.129.168.114
20 2026-08-26 06:18 639233213287814244
99 ms 185.129.168.114
19 2026-08-26 06:01 639233202925983161
80 ms 185.129.168.114
18 2026-08-26 05:43 639233192644780696
4 ms 185.129.168.114
17 2026-08-26 05:26 639233182401183833
178 ms 185.129.168.114
16 2026-08-26 05:09 639233172074181051
174 ms 185.129.168.114
15 2026-08-26 04:52 639233161808421455
3 ms 185.129.168.114
14 2026-08-26 04:35 639233151357344052
3 ms 185.129.168.114
13 2026-08-26 04:18 639233141034116946
91 ms 185.129.168.114
12 2026-08-26 04:00 639233130828334142
3 ms 185.129.168.114
11 2026-08-26 03:43 639233120373450007
179 ms 185.129.168.114
10 2026-08-26 03:26 639233110066216193
180 ms 185.129.168.114
9 2026-08-26 02:33 639233078065410564
175 ms 185.129.168.114
8 2026-08-26 02:15 639233067787457832
163 ms 185.129.168.114
7 2026-08-26 01:58 639233057501801162
2100 ms 185.129.168.114
6 2026-08-26 01:41 639233047089431703
94 ms 185.129.168.114
5 2026-08-26 01:24 639233036754790688
183 ms 185.129.168.114
4 2026-08-26 01:07 639233026412602472
197 ms 185.129.168.114
3 2026-08-26 00:49 639233016064066127
21 ms 185.129.168.114
2 2026-08-26 00:32 639233005922655772
32 ms 185.129.168.114
1 2026-08-26 00:15 639232995672256907
141 ms 185.129.168.114