DNS response history for ns1.enube.top

ns1.enube.top 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 36 DNS check records, 36 successful responses, 0 failed responses, and 419 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 ns1.enube.top.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

419 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

216.126.233.130

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 ns1.enube.top

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
36 2026-08-26 12:11 639233424567558554
31 ms 216.126.233.130
35 2026-08-26 11:53 639233414056832719
2234 ms 216.126.233.130
34 2026-08-26 11:36 639233403515141099
168 ms 216.126.233.130
33 2026-08-26 10:41 639233370841350248
180 ms 216.126.233.130
32 2026-08-26 10:24 639233360361507238
338 ms 216.126.233.130
31 2026-08-26 10:07 639233350067824371
347 ms 216.126.233.130
30 2026-08-26 09:49 639233339545274518
11 ms 216.126.233.130
29 2026-08-26 09:32 639233329214918079
240 ms 216.126.233.130
28 2026-08-26 09:15 639233318749762337
161 ms 216.126.233.130
27 2026-08-26 08:57 639233308387917838
340 ms 216.126.233.130
26 2026-08-26 08:40 639233297961740122
157 ms 216.126.233.130
25 2026-08-26 08:22 639233287487159094
328 ms 216.126.233.130
24 2026-08-26 08:05 639233276995531707
388 ms 216.126.233.130
23 2026-08-26 07:47 639233266521568229
2168 ms 216.126.233.130
22 2026-08-26 07:30 639233256081047431
330 ms 216.126.233.130
21 2026-08-26 06:36 639233223620132921
358 ms 216.126.233.130
20 2026-08-26 06:19 639233213287814244
174 ms 216.126.233.130
19 2026-08-26 06:01 639233202925983161
261 ms 216.126.233.130
18 2026-08-26 05:44 639233192644780696
364 ms 216.126.233.130
17 2026-08-26 05:27 639233182401183833
326 ms 216.126.233.130
16 2026-08-26 05:10 639233172074181051
2168 ms 216.126.233.130
15 2026-08-26 04:53 639233161808421455
343 ms 216.126.233.130
14 2026-08-26 04:36 639233151357344052
165 ms 216.126.233.130
13 2026-08-26 04:18 639233141034116946
356 ms 216.126.233.130
12 2026-08-26 04:01 639233130828334142
356 ms 216.126.233.130
11 2026-08-26 03:44 639233120373450007
368 ms 216.126.233.130
10 2026-08-26 03:27 639233110066216193
234 ms 216.126.233.130
9 2026-08-26 02:33 639233078065410564
163 ms 216.126.233.130
8 2026-08-26 02:16 639233067787457832
154 ms 216.126.233.130
7 2026-08-26 01:59 639233057501801162
350 ms 216.126.233.130
6 2026-08-26 01:42 639233047089431703
338 ms 216.126.233.130
5 2026-08-26 01:25 639233036754790688
342 ms 216.126.233.130
4 2026-08-26 01:07 639233026412602472
361 ms 216.126.233.130
3 2026-08-26 00:50 639233016064066127
9 ms 216.126.233.130
2 2026-08-26 00:33 639233005922655772
254 ms 216.126.233.130
1 2026-08-26 00:16 639232995672256907
236 ms 216.126.233.130