DNS response history for ns2.eelbyte.com

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

38

Historical checks stored for this nameserver on selected date

Average Latency

300 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.254.33.103

Most recently resolved hosting IP on selected date

Successful Responses

38

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.eelbyte.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
38 2026-08-25 13:00 639232587225721862
322 ms 162.254.33.103
37 2026-08-25 12:43 639232576780683689
307 ms 162.254.33.103
36 2026-08-25 12:25 639232566381512620
314 ms 162.254.33.103
35 2026-08-25 12:08 639232556111768563
287 ms 162.254.33.103
34 2026-08-25 11:51 639232545839529039
315 ms 162.254.33.103
33 2026-08-25 11:34 639232535349285207
302 ms 162.254.33.103
32 2026-08-25 11:16 639232524938080723
324 ms 162.254.33.103
31 2026-08-25 10:22 639232492740373468
297 ms 162.254.33.103
30 2026-08-25 10:05 639232482235303141
298 ms 162.254.33.103
29 2026-08-25 09:48 639232471861770303
312 ms 162.254.33.103
28 2026-08-25 09:30 639232461630217327
187 ms 162.254.33.103
27 2026-08-25 09:13 639232451282965990
300 ms 162.254.33.103
26 2026-08-25 08:56 639232440814614938
310 ms 162.254.33.103
25 2026-08-25 08:39 639232430410720425
301 ms 162.254.33.103
24 2026-08-25 08:21 639232420003096185
302 ms 162.254.33.103
23 2026-08-25 08:04 639232409467287444
282 ms 162.254.33.103
22 2026-08-25 07:46 639232399077195997
303 ms 162.254.33.103
21 2026-08-25 07:29 639232388731528337
313 ms 162.254.33.103
20 2026-08-25 07:12 639232378288598612
333 ms 162.254.33.103
19 2026-08-25 06:18 639232346196373643
323 ms 162.254.33.103
18 2026-08-25 06:01 639232336112370741
186 ms 162.254.33.103
17 2026-08-25 05:44 639232326146508970
300 ms 162.254.33.103
16 2026-08-25 05:28 639232316189381720
309 ms 162.254.33.103
15 2026-08-25 05:11 639232306217998913
309 ms 162.254.33.103
14 2026-08-25 04:54 639232296255744174
303 ms 162.254.33.103
13 2026-08-25 04:38 639232286095760789
311 ms 162.254.33.103
12 2026-08-25 04:21 639232276086186273
308 ms 162.254.33.103
11 2026-08-25 04:04 639232265900986425
303 ms 162.254.33.103
10 2026-08-25 03:47 639232255723518075
306 ms 162.254.33.103
9 2026-08-25 03:30 639232245484452890
322 ms 162.254.33.103
8 2026-08-25 03:13 639232235157175331
305 ms 162.254.33.103
7 2026-08-25 02:20 639232203197189095
300 ms 162.254.33.103
6 2026-08-25 02:03 639232192844564298
297 ms 162.254.33.103
5 2026-08-25 01:45 639232182496008942
293 ms 162.254.33.103
4 2026-08-25 01:28 639232172197053132
315 ms 162.254.33.103
3 2026-08-25 00:35 639232140250307418
304 ms 162.254.33.103
2 2026-08-25 00:18 639232129927860324
301 ms 162.254.33.103
1 2026-08-25 00:00 639232119551972438
292 ms 162.254.33.103