DNS response history for ns2.ledabber.com

ns2.ledabber.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 26 DNS check records, 26 successful responses, 0 failed responses, and 129 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.ledabber.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

129 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

94.130.208.194

Most recently resolved hosting IP on selected date

Successful Responses

26

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.ledabber.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
26 2026-08-25 09:05 639232451282965990
2042 ms 94.130.208.194
25 2026-08-25 08:47 639232440814614938
60 ms 94.130.208.194
24 2026-08-25 08:30 639232430410720425
56 ms 94.130.208.194
23 2026-08-25 08:13 639232420003096185
57 ms 94.130.208.194
22 2026-08-25 07:55 639232409467287444
70 ms 94.130.208.194
21 2026-08-25 07:38 639232399077195997
159 ms 94.130.208.194
20 2026-08-25 07:21 639232388731528337
53 ms 94.130.208.194
19 2026-08-25 07:03 639232378288598612
5 ms 94.130.208.194
18 2026-08-25 06:10 639232346196373643
58 ms 94.130.208.194
17 2026-08-25 05:53 639232336112370741
46 ms 94.130.208.194
16 2026-08-25 05:36 639232326146508970
57 ms 94.130.208.194
15 2026-08-25 05:20 639232316189381720
12 ms 94.130.208.194
14 2026-08-25 05:03 639232306217998913
36 ms 94.130.208.194
13 2026-08-25 04:46 639232296255744174
22 ms 94.130.208.194
12 2026-08-25 04:30 639232286095760789
13 ms 94.130.208.194
11 2026-08-25 04:13 639232276086186273
13 ms 94.130.208.194
10 2026-08-25 03:56 639232265900986425
78 ms 94.130.208.194
9 2026-08-25 03:39 639232255723518075
54 ms 94.130.208.194
8 2026-08-25 03:22 639232245484452890
36 ms 94.130.208.194
7 2026-08-25 03:05 639232235157175331
28 ms 94.130.208.194
6 2026-08-25 02:11 639232203197189095
40 ms 94.130.208.194
5 2026-08-25 01:54 639232192844564298
46 ms 94.130.208.194
4 2026-08-25 01:37 639232182496008942
41 ms 94.130.208.194
3 2026-08-25 01:20 639232172197053132
65 ms 94.130.208.194
2 2026-08-25 00:26 639232140250307418
65 ms 94.130.208.194
1 2026-08-25 00:09 639232129927860324
143 ms 94.130.208.194