DNS response history for ns2.horal.us

ns2.horal.us 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 37 DNS check records, 37 successful responses, 0 failed responses, and 351 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.horal.us.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

351 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

23.137.104.42

Most recently resolved hosting IP on selected date

Successful Responses

37

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.horal.us

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
37 2026-08-25 12:56 639232587225721862
2131 ms 23.137.104.42
36 2026-08-25 12:39 639232576780683689
261 ms 23.137.104.42
35 2026-08-25 12:22 639232566381512620
306 ms 23.137.104.42
34 2026-08-25 12:04 639232556111768563
272 ms 23.137.104.42
33 2026-08-25 11:47 639232545839529039
273 ms 23.137.104.42
32 2026-08-25 11:30 639232535349285207
266 ms 23.137.104.42
31 2026-08-25 11:12 639232524938080723
269 ms 23.137.104.42
30 2026-08-25 10:19 639232492740373468
2164 ms 23.137.104.42
29 2026-08-25 10:02 639232482235303141
127 ms 23.137.104.42
28 2026-08-25 09:44 639232471861770303
262 ms 23.137.104.42
27 2026-08-25 09:27 639232461630217327
259 ms 23.137.104.42
26 2026-08-25 09:10 639232451282965990
269 ms 23.137.104.42
25 2026-08-25 08:52 639232440814614938
203 ms 23.137.104.42
24 2026-08-25 08:35 639232430410720425
358 ms 23.137.104.42
23 2026-08-25 08:18 639232420003096185
216 ms 23.137.104.42
22 2026-08-25 08:00 639232409467287444
265 ms 23.137.104.42
21 2026-08-25 07:43 639232399077195997
142 ms 23.137.104.42
20 2026-08-25 07:25 639232388731528337
271 ms 23.137.104.42
19 2026-08-25 07:08 639232378288598612
274 ms 23.137.104.42
18 2026-08-25 06:14 639232346196373643
275 ms 23.137.104.42
17 2026-08-25 05:57 639232336112370741
127 ms 23.137.104.42
16 2026-08-25 05:41 639232326146508970
127 ms 23.137.104.42
15 2026-08-25 05:24 639232316189381720
129 ms 23.137.104.42
14 2026-08-25 05:08 639232306217998913
262 ms 23.137.104.42
13 2026-08-25 04:51 639232296255744174
268 ms 23.137.104.42
12 2026-08-25 04:34 639232286095760789
265 ms 23.137.104.42
11 2026-08-25 04:17 639232276086186273
267 ms 23.137.104.42
10 2026-08-25 04:01 639232265900986425
272 ms 23.137.104.42
9 2026-08-25 03:44 639232255723518075
266 ms 23.137.104.42
8 2026-08-25 03:27 639232245484452890
279 ms 23.137.104.42
7 2026-08-25 03:09 639232235157175331
266 ms 23.137.104.42
6 2026-08-25 02:16 639232203197189095
122 ms 23.137.104.42
5 2026-08-25 01:59 639232192844564298
286 ms 23.137.104.42
4 2026-08-25 01:42 639232182496008942
131 ms 23.137.104.42
3 2026-08-25 01:24 639232172197053132
267 ms 23.137.104.42
2 2026-08-25 00:31 639232140250307418
507 ms 23.137.104.42
1 2026-08-25 00:14 639232129927860324
270 ms 23.137.104.42