DNS response history for ns2.elbahr.com

ns2.elbahr.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-25. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 594 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.elbahr.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

594 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.235.166.254

Most recently resolved hosting IP on selected date

Successful Responses

36

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.elbahr.com

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
36 2026-08-25 12:36 639232576780683689
2200 ms 91.235.166.254
35 2026-08-25 12:19 639232566381512620
211 ms 91.235.166.254
34 2026-08-25 12:01 639232556111768563
2236 ms 91.235.166.254
33 2026-08-25 11:44 639232545839529039
209 ms 91.235.166.254
32 2026-08-25 11:27 639232535349285207
108 ms 91.235.166.254
31 2026-08-25 11:09 639232524938080723
70 ms 91.235.166.254
30 2026-08-25 10:16 639232492740373468
229 ms 91.235.166.254
29 2026-08-25 09:59 639232482235303141
2210 ms 91.235.166.254
28 2026-08-25 09:41 639232471861770303
2220 ms 91.235.166.254
27 2026-08-25 09:24 639232461630217327
202 ms 91.235.166.254
26 2026-08-25 09:07 639232451282965990
64 ms 91.235.166.254
25 2026-08-25 08:49 639232440814614938
69 ms 91.235.166.254
24 2026-08-25 08:32 639232430410720425
68 ms 91.235.166.254
23 2026-08-25 08:15 639232420003096185
65 ms 91.235.166.254
22 2026-08-25 07:57 639232409467287444
73 ms 91.235.166.254
21 2026-08-25 07:40 639232399077195997
62 ms 91.235.166.254
20 2026-08-25 07:22 639232388731528337
233 ms 91.235.166.254
19 2026-08-25 07:05 639232378288598612
2231 ms 91.235.166.254
18 2026-08-25 06:12 639232346196373643
2102 ms 91.235.166.254
17 2026-08-25 05:55 639232336112370741
211 ms 91.235.166.254
16 2026-08-25 05:38 639232326146508970
62 ms 91.235.166.254
15 2026-08-25 05:21 639232316189381720
62 ms 91.235.166.254
14 2026-08-25 05:05 639232306217998913
2208 ms 91.235.166.254
13 2026-08-25 04:48 639232296255744174
74 ms 91.235.166.254
12 2026-08-25 04:31 639232286095760789
71 ms 91.235.166.254
11 2026-08-25 04:14 639232276086186273
229 ms 91.235.166.254
10 2026-08-25 03:58 639232265900986425
206 ms 91.235.166.254
9 2026-08-25 03:41 639232255723518075
2201 ms 91.235.166.254
8 2026-08-25 03:24 639232245484452890
243 ms 91.235.166.254
7 2026-08-25 03:06 639232235157175331
236 ms 91.235.166.254
6 2026-08-25 02:13 639232203197189095
36 ms 91.235.166.254
5 2026-08-25 01:56 639232192844564298
207 ms 91.235.166.254
4 2026-08-25 01:39 639232182496008942
227 ms 91.235.166.254
3 2026-08-25 01:21 639232172197053132
34 ms 91.235.166.254
2 2026-08-25 00:28 639232140250307418
61 ms 91.235.166.254
1 2026-08-25 00:11 639232129927860324
141 ms 91.235.166.254