DNS response history for ns2.solo-hoy.net

ns2.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-27. For this date, NameServerHistory found 25 DNS check records, 25 successful responses, 0 failed responses, and 437 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.solo-hoy.net.
Records on Selected Date

25

Historical checks stored for this nameserver on selected date

Average Latency

437 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 08:19

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

25

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

Showing DNS history for 2026-08-27 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
25 2026-08-27 08:19 639234149799404224
143 ms 45.61.51.172
24 2026-08-27 08:01 639234139553286469
310 ms 45.61.51.172
23 2026-08-27 07:08 639234107183588293
140 ms 45.61.51.172
22 2026-08-27 06:50 639234096905435724
288 ms 45.61.51.172
21 2026-08-27 06:33 639234086579410775
138 ms 45.61.51.172
20 2026-08-27 06:16 639234076291157956
274 ms 45.61.51.172
19 2026-08-27 05:59 639234065981939454
4281 ms 45.61.51.172
18 2026-08-27 05:42 639234055548642997
275 ms 45.61.51.172
17 2026-08-27 05:24 639234045267979603
273 ms 45.61.51.172
16 2026-08-27 05:07 639234034999717463
145 ms 45.61.51.172
15 2026-08-27 04:50 639234024739225358
2129 ms 45.61.51.172
14 2026-08-27 04:33 639234014311170162
136 ms 45.61.51.172
13 2026-08-27 04:15 639234003806017640
136 ms 45.61.51.172
12 2026-08-27 03:58 639233993356203030
132 ms 45.61.51.172
11 2026-08-27 03:05 639233961301716608
33 ms 45.61.51.172
10 2026-08-27 02:47 639233950834200647
277 ms 45.61.51.172
9 2026-08-27 02:30 639233940431849026
135 ms 45.61.51.172
8 2026-08-27 02:13 639233930110596398
293 ms 45.61.51.172
7 2026-08-27 01:55 639233919705434540
12 ms 45.61.51.172
6 2026-08-27 01:38 639233909452807845
145 ms 45.61.51.172
5 2026-08-27 01:21 639233899096420820
134 ms 45.61.51.172
4 2026-08-27 01:04 639233888707824939
277 ms 45.61.51.172
3 2026-08-27 00:46 639233878461203802
271 ms 45.61.51.172
2 2026-08-27 00:29 639233868060868209
269 ms 45.61.51.172
1 2026-08-27 00:12 639233857450922991
272 ms 45.61.51.172