DNS response history for ns2.eleggans.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

244 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

63.250.41.113

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 ns2.eleggans.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
36 2026-08-25 12:26 639232566381512620
308 ms 63.250.41.113
35 2026-08-25 12:08 639232556111768563
318 ms 63.250.41.113
34 2026-08-25 11:51 639232545839529039
153 ms 63.250.41.113
33 2026-08-25 11:34 639232535349285207
162 ms 63.250.41.113
32 2026-08-25 11:17 639232524938080723
157 ms 63.250.41.113
31 2026-08-25 10:23 639232492740373468
306 ms 63.250.41.113
30 2026-08-25 10:06 639232482235303141
153 ms 63.250.41.113
29 2026-08-25 09:48 639232471861770303
164 ms 63.250.41.113
28 2026-08-25 09:31 639232461630217327
308 ms 63.250.41.113
27 2026-08-25 09:14 639232451282965990
317 ms 63.250.41.113
26 2026-08-25 08:56 639232440814614938
141 ms 63.250.41.113
25 2026-08-25 08:39 639232430410720425
283 ms 63.250.41.113
24 2026-08-25 08:22 639232420003096185
174 ms 63.250.41.113
23 2026-08-25 08:04 639232409467287444
145 ms 63.250.41.113
22 2026-08-25 07:47 639232399077195997
313 ms 63.250.41.113
21 2026-08-25 07:29 639232388731528337
328 ms 63.250.41.113
20 2026-08-25 07:12 639232378288598612
144 ms 63.250.41.113
19 2026-08-25 06:18 639232346196373643
323 ms 63.250.41.113
18 2026-08-25 06:01 639232336112370741
3 ms 63.250.41.113
17 2026-08-25 05:45 639232326146508970
297 ms 63.250.41.113
16 2026-08-25 05:28 639232316189381720
292 ms 63.250.41.113
15 2026-08-25 05:12 639232306217998913
416 ms 63.250.41.113
14 2026-08-25 04:55 639232296255744174
150 ms 63.250.41.113
13 2026-08-25 04:38 639232286095760789
355 ms 63.250.41.113
12 2026-08-25 04:21 639232276086186273
162 ms 63.250.41.113
11 2026-08-25 04:05 639232265900986425
298 ms 63.250.41.113
10 2026-08-25 03:48 639232255723518075
304 ms 63.250.41.113
9 2026-08-25 03:31 639232245484452890
308 ms 63.250.41.113
8 2026-08-25 03:14 639232235157175331
143 ms 63.250.41.113
7 2026-08-25 02:20 639232203197189095
314 ms 63.250.41.113
6 2026-08-25 02:03 639232192844564298
300 ms 63.250.41.113
5 2026-08-25 01:46 639232182496008942
309 ms 63.250.41.113
4 2026-08-25 01:28 639232172197053132
311 ms 63.250.41.113
3 2026-08-25 00:35 639232140250307418
307 ms 63.250.41.113
2 2026-08-25 00:18 639232129927860324
156 ms 63.250.41.113
1 2026-08-25 00:01 639232119551972438
157 ms 63.250.41.113