DNS response history for ns2.hoonel.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

250 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

217.144.106.68

Most recently resolved hosting IP on selected date

Successful Responses

34

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.hoonel.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
34 2026-08-25 11:52 639232545839529039
247 ms 217.144.106.68
33 2026-08-25 11:35 639232535349285207
240 ms 217.144.106.68
32 2026-08-25 11:17 639232524938080723
247 ms 217.144.106.68
31 2026-08-25 10:23 639232492740373468
216 ms 217.144.106.68
30 2026-08-25 10:06 639232482235303141
229 ms 217.144.106.68
29 2026-08-25 09:49 639232471861770303
230 ms 217.144.106.68
28 2026-08-25 09:31 639232461630217327
219 ms 217.144.106.68
27 2026-08-25 09:14 639232451282965990
330 ms 217.144.106.68
26 2026-08-25 08:57 639232440814614938
525 ms 217.144.106.68
25 2026-08-25 08:40 639232430410720425
228 ms 217.144.106.68
24 2026-08-25 08:22 639232420003096185
364 ms 217.144.106.68
23 2026-08-25 08:05 639232409467287444
284 ms 217.144.106.68
22 2026-08-25 07:48 639232399077195997
225 ms 217.144.106.68
21 2026-08-25 07:30 639232388731528337
271 ms 217.144.106.68
20 2026-08-25 07:13 639232378288598612
237 ms 217.144.106.68
19 2026-08-25 06:19 639232346196373643
248 ms 217.144.106.68
18 2026-08-25 06:02 639232336112370741
243 ms 217.144.106.68
17 2026-08-25 05:45 639232326146508970
222 ms 217.144.106.68
16 2026-08-25 05:29 639232316189381720
553 ms 217.144.106.68
15 2026-08-25 05:12 639232306217998913
226 ms 217.144.106.68
14 2026-08-25 04:55 639232296255744174
241 ms 217.144.106.68
13 2026-08-25 04:39 639232286095760789
3 ms 217.144.106.68
12 2026-08-25 04:22 639232276086186273
219 ms 217.144.106.68
11 2026-08-25 04:05 639232265900986425
232 ms 217.144.106.68
10 2026-08-25 03:48 639232255723518075
223 ms 217.144.106.68
9 2026-08-25 03:31 639232245484452890
227 ms 217.144.106.68
8 2026-08-25 03:14 639232235157175331
221 ms 217.144.106.68
7 2026-08-25 02:21 639232203197189095
230 ms 217.144.106.68
6 2026-08-25 02:04 639232192844564298
205 ms 217.144.106.68
5 2026-08-25 01:46 639232182496008942
231 ms 217.144.106.68
4 2026-08-25 01:29 639232172197053132
223 ms 217.144.106.68
3 2026-08-25 00:36 639232140250307418
218 ms 217.144.106.68
2 2026-08-25 00:19 639232129927860324
224 ms 217.144.106.68
1 2026-08-25 00:01 639232119551972438
216 ms 217.144.106.68