DNS response history for ns3.ebox.net

ns3.ebox.net 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 30 DNS check records, 30 successful responses, 0 failed responses, and 241 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 ns3.ebox.net.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

241 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

96.127.255.8

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns3.ebox.net

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
30 2026-08-26 09:49 639233339545274518
2016 ms 96.127.255.8
29 2026-08-26 09:31 639233329214918079
218 ms 96.127.255.8
28 2026-08-26 09:14 639233318749762337
227 ms 96.127.255.8
27 2026-08-26 08:56 639233308387917838
220 ms 96.127.255.8
26 2026-08-26 08:39 639233297961740122
111 ms 96.127.255.8
25 2026-08-26 08:22 639233287487159094
119 ms 96.127.255.8
24 2026-08-26 08:04 639233276995531707
810 ms 96.127.255.8
23 2026-08-26 07:47 639233266521568229
110 ms 96.127.255.8
22 2026-08-26 07:29 639233256081047431
119 ms 96.127.255.8
21 2026-08-26 06:35 639233223620132921
257 ms 96.127.255.8
20 2026-08-26 06:18 639233213287814244
113 ms 96.127.255.8
19 2026-08-26 06:01 639233202925983161
218 ms 96.127.255.8
18 2026-08-26 05:43 639233192644780696
124 ms 96.127.255.8
17 2026-08-26 05:26 639233182401183833
7 ms 96.127.255.8
16 2026-08-26 05:09 639233172074181051
258 ms 96.127.255.8
15 2026-08-26 04:52 639233161808421455
126 ms 96.127.255.8
14 2026-08-26 04:35 639233151357344052
117 ms 96.127.255.8
13 2026-08-26 04:17 639233141034116946
118 ms 96.127.255.8
12 2026-08-26 04:00 639233130828334142
122 ms 96.127.255.8
11 2026-08-26 03:43 639233120373450007
9 ms 96.127.255.8
10 2026-08-26 03:26 639233110066216193
117 ms 96.127.255.8
9 2026-08-26 02:33 639233078065410564
228 ms 96.127.255.8
8 2026-08-26 02:15 639233067787457832
235 ms 96.127.255.8
7 2026-08-26 01:58 639233057501801162
234 ms 96.127.255.8
6 2026-08-26 01:41 639233047089431703
117 ms 96.127.255.8
5 2026-08-26 01:24 639233036754790688
102 ms 96.127.255.8
4 2026-08-26 01:07 639233026412602472
111 ms 96.127.255.8
3 2026-08-26 00:49 639233016064066127
155 ms 96.127.255.8
2 2026-08-26 00:32 639233005922655772
259 ms 96.127.255.8
1 2026-08-26 00:15 639232995672256907
243 ms 96.127.255.8