DNS response history for ns2.royaliummultiservices.com

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

27

Historical checks stored for this nameserver on selected date

Average Latency

245 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.235.106.104

Most recently resolved hosting IP on selected date

Successful Responses

27

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.royaliummultiservices.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
27 2026-08-26 08:42 639233297961740122
306 ms 103.235.106.104
26 2026-08-26 08:25 639233287487159094
166 ms 103.235.106.104
25 2026-08-26 08:07 639233276995531707
293 ms 103.235.106.104
24 2026-08-26 07:50 639233266521568229
156 ms 103.235.106.104
23 2026-08-26 07:32 639233256081047431
294 ms 103.235.106.104
22 2026-08-26 06:38 639233223620132921
294 ms 103.235.106.104
21 2026-08-26 06:21 639233213287814244
292 ms 103.235.106.104
20 2026-08-26 06:04 639233202925983161
4 ms 103.235.106.104
19 2026-08-26 05:46 639233192644780696
293 ms 103.235.106.104
18 2026-08-26 05:29 639233182401183833
309 ms 103.235.106.104
17 2026-08-26 05:12 639233172074181051
306 ms 103.235.106.104
16 2026-08-26 04:55 639233161808421455
288 ms 103.235.106.104
15 2026-08-26 04:38 639233151357344052
2 ms 103.235.106.104
14 2026-08-26 04:20 639233141034116946
288 ms 103.235.106.104
13 2026-08-26 04:03 639233130828334142
284 ms 103.235.106.104
12 2026-08-26 03:46 639233120373450007
281 ms 103.235.106.104
11 2026-08-26 03:29 639233110066216193
296 ms 103.235.106.104
10 2026-08-26 02:35 639233078065410564
142 ms 103.235.106.104
9 2026-08-26 02:18 639233067787457832
288 ms 103.235.106.104
8 2026-08-26 02:01 639233057501801162
285 ms 103.235.106.104
7 2026-08-26 01:44 639233047089431703
141 ms 103.235.106.104
6 2026-08-26 01:27 639233036754790688
288 ms 103.235.106.104
5 2026-08-26 01:09 639233026412602472
293 ms 103.235.106.104
4 2026-08-26 00:52 639233016064066127
297 ms 103.235.106.104
3 2026-08-26 00:35 639233005922655772
154 ms 103.235.106.104
2 2026-08-26 00:18 639232995672256907
286 ms 103.235.106.104
1 2026-08-26 00:01 639232985300872416
298 ms 103.235.106.104