DNS response history for ns2.sabilaw.org

ns2.sabilaw.org 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 34 DNS check records, 34 successful responses, 0 failed responses, and 95 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.sabilaw.org.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

95 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.50.89.165

Most recently resolved hosting IP on selected date

Successful Responses

34

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.sabilaw.org

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
34 2026-08-26 10:46 639233370841350248
4 ms 74.50.89.165
33 2026-08-26 10:29 639233360361507238
264 ms 74.50.89.165
32 2026-08-26 10:12 639233350067824371
258 ms 74.50.89.165
31 2026-08-26 09:54 639233339545274518
4 ms 74.50.89.165
30 2026-08-26 09:37 639233329214918079
530 ms 74.50.89.165
29 2026-08-26 09:20 639233318749762337
145 ms 74.50.89.165
28 2026-08-26 09:02 639233308387917838
6 ms 74.50.89.165
27 2026-08-26 08:45 639233297961740122
5 ms 74.50.89.165
26 2026-08-26 08:28 639233287487159094
262 ms 74.50.89.165
25 2026-08-26 08:10 639233276995531707
4 ms 74.50.89.165
24 2026-08-26 07:53 639233266521568229
266 ms 74.50.89.165
23 2026-08-26 07:35 639233256081047431
431 ms 74.50.89.165
22 2026-08-26 06:41 639233223620132921
5 ms 74.50.89.165
21 2026-08-26 06:24 639233213287814244
6 ms 74.50.89.165
20 2026-08-26 06:06 639233202925983161
6 ms 74.50.89.165
19 2026-08-26 05:49 639233192644780696
138 ms 74.50.89.165
18 2026-08-26 05:32 639233182401183833
5 ms 74.50.89.165
17 2026-08-26 05:15 639233172074181051
3 ms 74.50.89.165
16 2026-08-26 04:58 639233161808421455
4 ms 74.50.89.165
15 2026-08-26 04:41 639233151357344052
4 ms 74.50.89.165
14 2026-08-26 04:23 639233141034116946
4 ms 74.50.89.165
13 2026-08-26 04:06 639233130828334142
375 ms 74.50.89.165
12 2026-08-26 03:49 639233120373450007
17 ms 74.50.89.165
11 2026-08-26 03:32 639233110066216193
3 ms 74.50.89.165
10 2026-08-26 02:38 639233078065410564
147 ms 74.50.89.165
9 2026-08-26 02:21 639233067787457832
7 ms 74.50.89.165
8 2026-08-26 02:04 639233057501801162
3 ms 74.50.89.165
7 2026-08-26 01:47 639233047089431703
4 ms 74.50.89.165
6 2026-08-26 01:29 639233036754790688
142 ms 74.50.89.165
5 2026-08-26 01:12 639233026412602472
154 ms 74.50.89.165
4 2026-08-26 00:55 639233016064066127
4 ms 74.50.89.165
3 2026-08-26 00:38 639233005922655772
5 ms 74.50.89.165
2 2026-08-26 00:21 639232995672256907
4 ms 74.50.89.165
1 2026-08-26 00:04 639232985300872416
3 ms 74.50.89.165