DNS response history for ns2.alomary.sa

ns2.alomary.sa 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, 28 successful responses, 1 failed responses, and 304 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.alomary.sa.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

304 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

168.119.164.156

Most recently resolved hosting IP on selected date

Successful Responses

28

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.alomary.sa

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:28 639233329214918079
32 ms 168.119.164.156
28 2026-08-26 09:11 639233318749762337
52 ms 168.119.164.156
27 2026-08-26 08:54 639233308387917838
8 ms 168.119.164.156
26 2026-08-26 08:36 639233297961740122
1604 ms 168.119.164.156
25 2026-08-26 08:19 639233287487159094
128 ms 168.119.164.156
24 2026-08-26 08:01 639233276995531707
94 ms 168.119.164.156
23 2026-08-26 07:44 639233266521568229
57 ms 168.119.164.156
22 2026-08-26 07:27 639233256081047431
66 ms 168.119.164.156
21 2026-08-26 06:33 639233223620132921
40 ms 168.119.164.156
20 2026-08-26 06:15 639233213287814244
-
19 2026-08-26 05:58 639233202925983161
44 ms 168.119.164.156
18 2026-08-26 05:41 639233192644780696
120 ms 168.119.164.156
17 2026-08-26 05:24 639233182401183833
2214 ms 168.119.164.156
16 2026-08-26 05:07 639233172074181051
109 ms 168.119.164.156
15 2026-08-26 04:50 639233161808421455
52 ms 168.119.164.156
14 2026-08-26 04:32 639233151357344052
59 ms 168.119.164.156
13 2026-08-26 04:15 639233141034116946
26 ms 168.119.164.156
12 2026-08-26 03:58 639233130828334142
44 ms 168.119.164.156
11 2026-08-26 03:40 639233120373450007
810 ms 168.119.164.156
10 2026-08-26 03:23 639233110066216193
9 ms 168.119.164.156
9 2026-08-26 02:30 639233078065410564
41 ms 168.119.164.156
8 2026-08-26 02:13 639233067787457832
125 ms 168.119.164.156
7 2026-08-26 01:56 639233057501801162
2288 ms 168.119.164.156
6 2026-08-26 01:38 639233047089431703
112 ms 168.119.164.156
5 2026-08-26 01:21 639233036754790688
54 ms 168.119.164.156
4 2026-08-26 01:04 639233026412602472
37 ms 168.119.164.156
3 2026-08-26 00:47 639233016064066127
55 ms 168.119.164.156
2 2026-08-26 00:30 639233005922655772
113 ms 168.119.164.156
1 2026-08-26 00:13 639232995672256907
106 ms 168.119.164.156