DNS response history for ns2.alebtekarco.com

ns2.alebtekarco.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 183 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.alebtekarco.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

183 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

54.38.80.123

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.alebtekarco.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:28 639233329214918079
33 ms 54.38.80.123
28 2026-08-26 09:11 639233318749762337
34 ms 54.38.80.123
27 2026-08-26 08:54 639233308387917838
34 ms 54.38.80.123
26 2026-08-26 08:36 639233297961740122
18 ms 54.38.80.123
25 2026-08-26 08:19 639233287487159094
34 ms 54.38.80.123
24 2026-08-26 08:01 639233276995531707
51 ms 54.38.80.123
23 2026-08-26 07:44 639233266521568229
32 ms 54.38.80.123
22 2026-08-26 07:26 639233256081047431
30 ms 54.38.80.123
21 2026-08-26 06:32 639233223620132921
31 ms 54.38.80.123
20 2026-08-26 06:15 639233213287814244
49 ms 54.38.80.123
19 2026-08-26 05:58 639233202925983161
40 ms 54.38.80.123
18 2026-08-26 05:41 639233192644780696
33 ms 54.38.80.123
17 2026-08-26 05:24 639233182401183833
36 ms 54.38.80.123
16 2026-08-26 05:07 639233172074181051
45 ms 54.38.80.123
15 2026-08-26 04:49 639233161808421455
39 ms 54.38.80.123
14 2026-08-26 04:32 639233151357344052
7 ms 54.38.80.123
13 2026-08-26 04:15 639233141034116946
57 ms 54.38.80.123
12 2026-08-26 03:58 639233130828334142
39 ms 54.38.80.123
11 2026-08-26 03:40 639233120373450007
34 ms 54.38.80.123
10 2026-08-26 03:23 639233110066216193
131 ms 54.38.80.123
9 2026-08-26 02:30 639233078065410564
45 ms 54.38.80.123
8 2026-08-26 02:13 639233067787457832
91 ms 54.38.80.123
7 2026-08-26 01:56 639233057501801162
121 ms 54.38.80.123
6 2026-08-26 01:38 639233047089431703
45 ms 54.38.80.123
5 2026-08-26 01:21 639233036754790688
28 ms 54.38.80.123
4 2026-08-26 01:04 639233026412602472
32 ms 54.38.80.123
3 2026-08-26 00:46 639233016064066127
2028 ms 54.38.80.123
2 2026-08-26 00:29 639233005922655772
37 ms 54.38.80.123
1 2026-08-26 00:12 639232995672256907
2086 ms 54.38.80.123