DNS response history for ns2.telekom.com.al

ns2.telekom.com.al 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 37 DNS check records, 35 successful responses, 2 failed responses, and 150 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.telekom.com.al.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

150 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

109.234.236.130

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

5%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.telekom.com.al

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
37 2026-08-26 12:24 639233434974187439
49 ms 109.234.236.130
36 2026-08-26 12:07 639233424567558554
117 ms 109.234.236.130
35 2026-08-26 11:50 639233414056832719
-
34 2026-08-26 11:32 639233403515141099
142 ms 109.234.236.130
33 2026-08-26 10:37 639233370841350248
56 ms 109.234.236.130
32 2026-08-26 10:20 639233360361507238
50 ms 109.234.236.130
31 2026-08-26 10:03 639233350067824371
51 ms 109.234.236.130
30 2026-08-26 09:46 639233339545274518
62 ms 109.234.236.130
29 2026-08-26 09:28 639233329214918079
122 ms 109.234.236.130
28 2026-08-26 09:11 639233318749762337
118 ms 109.234.236.130
27 2026-08-26 08:53 639233308387917838
56 ms 109.234.236.130
26 2026-08-26 08:36 639233297961740122
50 ms 109.234.236.130
25 2026-08-26 08:19 639233287487159094
13 ms 109.234.236.130
24 2026-08-26 08:01 639233276995531707
106 ms 109.234.236.130
23 2026-08-26 07:44 639233266521568229
140 ms 109.234.236.130
22 2026-08-26 07:26 639233256081047431
2046 ms 109.234.236.130
21 2026-08-26 06:32 639233223620132921
159 ms 109.234.236.130
20 2026-08-26 06:15 639233213287814244
117 ms 109.234.236.130
19 2026-08-26 05:58 639233202925983161
92 ms 109.234.236.130
18 2026-08-26 05:40 639233192644780696
-
17 2026-08-26 05:23 639233182401183833
124 ms 109.234.236.130
16 2026-08-26 05:06 639233172074181051
116 ms 109.234.236.130
15 2026-08-26 04:49 639233161808421455
111 ms 109.234.236.130
14 2026-08-26 04:32 639233151357344052
120 ms 109.234.236.130
13 2026-08-26 04:15 639233141034116946
60 ms 109.234.236.130
12 2026-08-26 03:57 639233130828334142
48 ms 109.234.236.130
11 2026-08-26 03:40 639233120373450007
69 ms 109.234.236.130
10 2026-08-26 03:23 639233110066216193
87 ms 109.234.236.130
9 2026-08-26 02:30 639233078065410564
112 ms 109.234.236.130
8 2026-08-26 02:12 639233067787457832
51 ms 109.234.236.130
7 2026-08-26 01:55 639233057501801162
114 ms 109.234.236.130
6 2026-08-26 01:38 639233047089431703
139 ms 109.234.236.130
5 2026-08-26 01:21 639233036754790688
84 ms 109.234.236.130
4 2026-08-26 01:03 639233026412602472
109 ms 109.234.236.130
3 2026-08-26 00:46 639233016064066127
18 ms 109.234.236.130
2 2026-08-26 00:29 639233005922655772
262 ms 109.234.236.130
1 2026-08-26 00:12 639232995672256907
73 ms 109.234.236.130