DNS response history for ns1.enpl.bet

ns1.enpl.bet 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 325 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.enpl.bet.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

325 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.159.1.229

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.enpl.bet

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:05 639233424567558554
30 ms 162.159.1.229
35 2026-08-26 11:47 639233414056832719
348 ms 162.159.1.229
34 2026-08-26 11:30 639233403515141099
10 ms 162.159.1.229
33 2026-08-26 10:35 639233370841350248
14 ms 162.159.1.229
32 2026-08-26 10:18 639233360361507238
12 ms 162.159.1.229
31 2026-08-26 10:01 639233350067824371
2044 ms 162.159.1.229
30 2026-08-26 09:43 639233339545274518
56 ms 162.159.1.229
29 2026-08-26 09:26 639233329214918079
7 ms 162.159.1.229
28 2026-08-26 09:08 639233318749762337
7 ms 162.159.1.229
27 2026-08-26 08:51 639233308387917838
22 ms 162.159.1.229
26 2026-08-26 08:34 639233297961740122
46 ms 162.159.1.229
25 2026-08-26 08:16 639233287487159094
52 ms 162.159.1.229
24 2026-08-26 07:59 639233276995531707
24 ms 162.159.1.229
23 2026-08-26 07:41 639233266521568229
215 ms 162.159.1.229
22 2026-08-26 07:24 639233256081047431
2022 ms 162.159.1.229
21 2026-08-26 06:30 639233223620132921
30 ms 162.159.1.229
20 2026-08-26 06:13 639233213287814244
30 ms 162.159.1.229
19 2026-08-26 05:55 639233202925983161
26 ms 162.159.1.229
18 2026-08-26 05:38 639233192644780696
13 ms 162.159.1.229
17 2026-08-26 05:21 639233182401183833
56 ms 162.159.1.229
16 2026-08-26 05:04 639233172074181051
26 ms 162.159.1.229
15 2026-08-26 04:47 639233161808421455
4 ms 162.159.1.229
14 2026-08-26 04:29 639233151357344052
5 ms 162.159.1.229
13 2026-08-26 04:12 639233141034116946
415 ms 162.159.1.229
12 2026-08-26 03:55 639233130828334142
7 ms 162.159.1.229
11 2026-08-26 03:38 639233120373450007
4 ms 162.159.1.229
10 2026-08-26 03:21 639233110066216193
2030 ms 162.159.1.229
9 2026-08-26 02:27 639233078065410564
37 ms 162.159.1.229
8 2026-08-26 02:10 639233067787457832
16 ms 162.159.1.229
7 2026-08-26 01:53 639233057501801162
2017 ms 162.159.1.229
6 2026-08-26 01:36 639233047089431703
2010 ms 162.159.1.229
5 2026-08-26 01:18 639233036754790688
15 ms 162.159.1.229
4 2026-08-26 01:01 639233026412602472
14 ms 162.159.1.229
3 2026-08-26 00:44 639233016064066127
12 ms 162.159.1.229
2 2026-08-26 00:27 639233005922655772
13 ms 162.159.1.229
1 2026-08-26 00:10 639232995672256907
19 ms 162.159.1.229