DNS response history for ns2.almazad.net

ns2.almazad.net 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 168 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.almazad.net.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

168 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

15.188.254.105

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.almazad.net

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:49 639233308387917838
12 ms 15.188.254.105
26 2026-08-26 08:32 639233297961740122
12 ms 15.188.254.105
25 2026-08-26 08:14 639233287487159094
27 ms 15.188.254.105
24 2026-08-26 07:57 639233276995531707
34 ms 15.188.254.105
23 2026-08-26 07:39 639233266521568229
2023 ms 15.188.254.105
22 2026-08-26 07:22 639233256081047431
9 ms 15.188.254.105
21 2026-08-26 06:28 639233223620132921
7 ms 15.188.254.105
20 2026-08-26 06:11 639233213287814244
12 ms 15.188.254.105
19 2026-08-26 05:53 639233202925983161
8 ms 15.188.254.105
18 2026-08-26 05:36 639233192644780696
7 ms 15.188.254.105
17 2026-08-26 05:19 639233182401183833
8 ms 15.188.254.105
16 2026-08-26 05:02 639233172074181051
9 ms 15.188.254.105
15 2026-08-26 04:45 639233161808421455
18 ms 15.188.254.105
14 2026-08-26 04:27 639233151357344052
8 ms 15.188.254.105
13 2026-08-26 04:10 639233141034116946
19 ms 15.188.254.105
12 2026-08-26 03:53 639233130828334142
16 ms 15.188.254.105
11 2026-08-26 03:36 639233120373450007
2016 ms 15.188.254.105
10 2026-08-26 03:19 639233110066216193
8 ms 15.188.254.105
9 2026-08-26 02:25 639233078065410564
16 ms 15.188.254.105
8 2026-08-26 02:08 639233067787457832
39 ms 15.188.254.105
7 2026-08-26 01:51 639233057501801162
121 ms 15.188.254.105
6 2026-08-26 01:34 639233047089431703
9 ms 15.188.254.105
5 2026-08-26 01:17 639233036754790688
9 ms 15.188.254.105
4 2026-08-26 00:59 639233026412602472
18 ms 15.188.254.105
3 2026-08-26 00:42 639233016064066127
9 ms 15.188.254.105
2 2026-08-26 00:25 639233005922655772
25 ms 15.188.254.105
1 2026-08-26 00:08 639232995672256907
30 ms 15.188.254.105