DNS response history for ns2.dandoelpecho.com

ns2.dandoelpecho.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 340 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.dandoelpecho.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

340 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

163.245.198.50

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.dandoelpecho.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:39 639232576780683689
266 ms 163.245.198.50
35 2026-08-25 12:21 639232566381512620
254 ms 163.245.198.50
34 2026-08-25 12:04 639232556111768563
261 ms 163.245.198.50
33 2026-08-25 11:47 639232545839529039
260 ms 163.245.198.50
32 2026-08-25 11:30 639232535349285207
163 ms 163.245.198.50
31 2026-08-25 11:12 639232524938080723
261 ms 163.245.198.50
30 2026-08-25 10:18 639232492740373468
259 ms 163.245.198.50
29 2026-08-25 10:01 639232482235303141
257 ms 163.245.198.50
28 2026-08-25 09:44 639232471861770303
180 ms 163.245.198.50
27 2026-08-25 09:27 639232461630217327
2189 ms 163.245.198.50
26 2026-08-25 09:09 639232451282965990
255 ms 163.245.198.50
25 2026-08-25 08:52 639232440814614938
256 ms 163.245.198.50
24 2026-08-25 08:35 639232430410720425
252 ms 163.245.198.50
23 2026-08-25 08:17 639232420003096185
158 ms 163.245.198.50
22 2026-08-25 08:00 639232409467287444
2169 ms 163.245.198.50
21 2026-08-25 07:42 639232399077195997
260 ms 163.245.198.50
20 2026-08-25 07:25 639232388731528337
259 ms 163.245.198.50
19 2026-08-25 07:08 639232378288598612
129 ms 163.245.198.50
18 2026-08-25 06:14 639232346196373643
249 ms 163.245.198.50
17 2026-08-25 05:57 639232336112370741
253 ms 163.245.198.50
16 2026-08-25 05:41 639232326146508970
265 ms 163.245.198.50
15 2026-08-25 05:24 639232316189381720
250 ms 163.245.198.50
14 2026-08-25 05:07 639232306217998913
253 ms 163.245.198.50
13 2026-08-25 04:51 639232296255744174
151 ms 163.245.198.50
12 2026-08-25 04:34 639232286095760789
251 ms 163.245.198.50
11 2026-08-25 04:17 639232276086186273
139 ms 163.245.198.50
10 2026-08-25 04:00 639232265900986425
261 ms 163.245.198.50
9 2026-08-25 03:43 639232255723518075
133 ms 163.245.198.50
8 2026-08-25 03:26 639232245484452890
256 ms 163.245.198.50
7 2026-08-25 03:09 639232235157175331
254 ms 163.245.198.50
6 2026-08-25 02:16 639232203197189095
250 ms 163.245.198.50
5 2026-08-25 01:59 639232192844564298
249 ms 163.245.198.50
4 2026-08-25 01:41 639232182496008942
250 ms 163.245.198.50
3 2026-08-25 01:24 639232172197053132
247 ms 163.245.198.50
2 2026-08-25 00:31 639232140250307418
178 ms 163.245.198.50
1 2026-08-25 00:14 639232129927860324
255 ms 163.245.198.50