DNS response history for ns1.solo-hoy.net

ns1.solo-hoy.net 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-26. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 609 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 ns1.solo-hoy.net.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

609 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

45.61.51.172

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns1.solo-hoy.net

Showing DNS history for 2026-08-26 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
33 2026-08-26 10:39 639233370841350248
281 ms 45.61.51.172
32 2026-08-26 10:21 639233360361507238
281 ms 45.61.51.172
31 2026-08-26 10:04 639233350067824371
278 ms 45.61.51.172
30 2026-08-26 09:47 639233339545274518
2145 ms 45.61.51.172
29 2026-08-26 09:29 639233329214918079
287 ms 45.61.51.172
28 2026-08-26 09:12 639233318749762337
280 ms 45.61.51.172
27 2026-08-26 08:55 639233308387917838
288 ms 45.61.51.172
26 2026-08-26 08:37 639233297961740122
277 ms 45.61.51.172
25 2026-08-26 08:20 639233287487159094
281 ms 45.61.51.172
24 2026-08-26 08:03 639233276995531707
277 ms 45.61.51.172
23 2026-08-26 07:45 639233266521568229
169 ms 45.61.51.172
22 2026-08-26 07:28 639233256081047431
277 ms 45.61.51.172
21 2026-08-26 06:34 639233223620132921
272 ms 45.61.51.172
20 2026-08-26 06:16 639233213287814244
278 ms 45.61.51.172
19 2026-08-26 05:59 639233202925983161
290 ms 45.61.51.172
18 2026-08-26 05:42 639233192644780696
275 ms 45.61.51.172
17 2026-08-26 05:25 639233182401183833
2135 ms 45.61.51.172
16 2026-08-26 05:08 639233172074181051
279 ms 45.61.51.172
15 2026-08-26 04:50 639233161808421455
285 ms 45.61.51.172
14 2026-08-26 04:33 639233151357344052
289 ms 45.61.51.172
13 2026-08-26 04:16 639233141034116946
2007 ms 45.61.51.172
12 2026-08-26 03:59 639233130828334142
2235 ms 45.61.51.172
11 2026-08-26 03:42 639233120373450007
275 ms 45.61.51.172
10 2026-08-26 03:24 639233110066216193
276 ms 45.61.51.172
9 2026-08-26 02:31 639233078065410564
295 ms 45.61.51.172
8 2026-08-26 02:14 639233067787457832
2009 ms 45.61.51.172
7 2026-08-26 01:57 639233057501801162
275 ms 45.61.51.172
6 2026-08-26 01:39 639233047089431703
275 ms 45.61.51.172
5 2026-08-26 01:22 639233036754790688
275 ms 45.61.51.172
4 2026-08-26 01:05 639233026412602472
277 ms 45.61.51.172
3 2026-08-26 00:48 639233016064066127
2137 ms 45.61.51.172
2 2026-08-26 00:31 639233005922655772
276 ms 45.61.51.172
1 2026-08-26 00:14 639232995672256907
275 ms 45.61.51.172