DNS response history for ns2.horizon.care

ns2.horizon.care 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 35 DNS check records, 34 successful responses, 1 failed responses, and 173 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.horizon.care.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

173 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

199.244.88.116

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.horizon.care

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
35 2026-08-25 12:08 639232556111768563
218 ms 199.244.88.116
34 2026-08-25 11:51 639232545839529039
220 ms 199.244.88.116
33 2026-08-25 11:34 639232535349285207
212 ms 199.244.88.116
32 2026-08-25 11:16 639232524938080723
227 ms 199.244.88.116
31 2026-08-25 10:23 639232492740373468
229 ms 199.244.88.116
30 2026-08-25 10:06 639232482235303141
225 ms 199.244.88.116
29 2026-08-25 09:48 639232471861770303
217 ms 199.244.88.116
28 2026-08-25 09:31 639232461630217327
227 ms 199.244.88.116
27 2026-08-25 09:14 639232451282965990
120 ms 199.244.88.116
26 2026-08-25 08:56 639232440814614938
214 ms 199.244.88.116
25 2026-08-25 08:39 639232430410720425
213 ms 199.244.88.116
24 2026-08-25 08:22 639232420003096185
296 ms 199.244.88.116
23 2026-08-25 08:04 639232409467287444
222 ms 199.244.88.116
22 2026-08-25 07:47 639232399077195997
220 ms 199.244.88.116
21 2026-08-25 07:29 639232388731528337
124 ms 199.244.88.116
20 2026-08-25 07:12 639232378288598612
213 ms 199.244.88.116
19 2026-08-25 06:18 639232346196373643
15 ms 199.244.88.116
18 2026-08-25 06:01 639232336112370741
7 ms 199.244.88.116
17 2026-08-25 05:45 639232326146508970
221 ms 199.244.88.116
16 2026-08-25 05:28 639232316189381720
19 ms 199.244.88.116
15 2026-08-25 05:11 639232306217998913
105 ms 199.244.88.116
14 2026-08-25 04:55 639232296255744174
106 ms 199.244.88.116
13 2026-08-25 04:38 639232286095760789
8 ms 199.244.88.116
12 2026-08-25 04:21 639232276086186273
107 ms 199.244.88.116
11 2026-08-25 04:04 639232265900986425
223 ms 199.244.88.116
10 2026-08-25 03:48 639232255723518075
433 ms 199.244.88.116
9 2026-08-25 03:31 639232245484452890
222 ms 199.244.88.116
8 2026-08-25 03:14 639232235157175331
-
7 2026-08-25 02:20 639232203197189095
216 ms 199.244.88.116
6 2026-08-25 02:03 639232192844564298
8 ms 199.244.88.116
5 2026-08-25 01:46 639232182496008942
212 ms 199.244.88.116
4 2026-08-25 01:28 639232172197053132
338 ms 199.244.88.116
3 2026-08-25 00:35 639232140250307418
7 ms 199.244.88.116
2 2026-08-25 00:18 639232129927860324
223 ms 199.244.88.116
1 2026-08-25 00:01 639232119551972438
27 ms 199.244.88.116