DNS response history for ns2.elbaasy.org

ns2.elbaasy.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-25. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 270 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.elbaasy.org.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

270 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

195.38.164.50

Most recently resolved hosting IP on selected date

Successful Responses

38

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

Showing DNS history for 2026-08-25 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
38 2026-08-25 13:13 639232597643611557
241 ms 195.38.164.50
37 2026-08-25 12:55 639232587225721862
449 ms 195.38.164.50
36 2026-08-25 12:38 639232576780683689
252 ms 195.38.164.50
35 2026-08-25 12:21 639232566381512620
236 ms 195.38.164.50
34 2026-08-25 12:03 639232556111768563
225 ms 195.38.164.50
33 2026-08-25 11:46 639232545839529039
107 ms 195.38.164.50
32 2026-08-25 11:29 639232535349285207
222 ms 195.38.164.50
31 2026-08-25 11:11 639232524938080723
104 ms 195.38.164.50
30 2026-08-25 10:18 639232492740373468
423 ms 195.38.164.50
29 2026-08-25 10:01 639232482235303141
215 ms 195.38.164.50
28 2026-08-25 09:43 639232471861770303
232 ms 195.38.164.50
27 2026-08-25 09:26 639232461630217327
235 ms 195.38.164.50
26 2026-08-25 09:09 639232451282965990
9 ms 195.38.164.50
25 2026-08-25 08:51 639232440814614938
329 ms 195.38.164.50
24 2026-08-25 08:34 639232430410720425
345 ms 195.38.164.50
23 2026-08-25 08:17 639232420003096185
9 ms 195.38.164.50
22 2026-08-25 07:59 639232409467287444
8 ms 195.38.164.50
21 2026-08-25 07:42 639232399077195997
2102 ms 195.38.164.50
20 2026-08-25 07:24 639232388731528337
209 ms 195.38.164.50
19 2026-08-25 07:07 639232378288598612
337 ms 195.38.164.50
18 2026-08-25 06:13 639232346196373643
402 ms 195.38.164.50
17 2026-08-25 05:56 639232336112370741
98 ms 195.38.164.50
16 2026-08-25 05:40 639232326146508970
103 ms 195.38.164.50
15 2026-08-25 05:23 639232316189381720
369 ms 195.38.164.50
14 2026-08-25 05:07 639232306217998913
3 ms 195.38.164.50
13 2026-08-25 04:50 639232296255744174
436 ms 195.38.164.50
12 2026-08-25 04:33 639232286095760789
111 ms 195.38.164.50
11 2026-08-25 04:16 639232276086186273
421 ms 195.38.164.50
10 2026-08-25 04:00 639232265900986425
201 ms 195.38.164.50
9 2026-08-25 03:43 639232255723518075
188 ms 195.38.164.50
8 2026-08-25 03:26 639232245484452890
378 ms 195.38.164.50
7 2026-08-25 03:08 639232235157175331
466 ms 195.38.164.50
6 2026-08-25 02:15 639232203197189095
351 ms 195.38.164.50
5 2026-08-25 01:58 639232192844564298
98 ms 195.38.164.50
4 2026-08-25 01:41 639232182496008942
231 ms 195.38.164.50
3 2026-08-25 01:23 639232172197053132
9 ms 195.38.164.50
2 2026-08-25 00:30 639232140250307418
3 ms 195.38.164.50
1 2026-08-25 00:13 639232129927860324
117 ms 195.38.164.50