DNS response history for ns2.solvepro.net

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

37

Historical checks stored for this nameserver on selected date

Average Latency

216 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.27.79.61

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.solvepro.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
37 2026-08-27 12:27 639234296664302575
220 ms 198.27.79.61
36 2026-08-27 12:10 639234286253196126
226 ms 198.27.79.61
35 2026-08-27 11:16 639234253963286387
113 ms 198.27.79.61
34 2026-08-27 10:59 639234243654907465
107 ms 198.27.79.61
33 2026-08-27 10:42 639234233269654413
218 ms 198.27.79.61
32 2026-08-27 10:25 639234222943951923
107 ms 198.27.79.61
31 2026-08-27 10:07 639234212558002823
224 ms 198.27.79.61
30 2026-08-27 09:50 639234202117531850
218 ms 198.27.79.61
29 2026-08-27 09:33 639234191649612722
3 ms 198.27.79.61
28 2026-08-27 09:15 639234181105879568
220 ms 198.27.79.61
27 2026-08-27 08:58 639234170713214496
227 ms 198.27.79.61
26 2026-08-27 08:40 639234160341037652
212 ms 198.27.79.61
25 2026-08-27 08:23 639234149799404224
110 ms 198.27.79.61
24 2026-08-27 08:05 639234139553286469
226 ms 198.27.79.61
23 2026-08-27 07:12 639234107183588293
111 ms 198.27.79.61
22 2026-08-27 06:54 639234096905435724
225 ms 198.27.79.61
21 2026-08-27 06:37 639234086579410775
216 ms 198.27.79.61
20 2026-08-27 06:20 639234076291157956
223 ms 198.27.79.61
19 2026-08-27 06:03 639234065981939454
218 ms 198.27.79.61
18 2026-08-27 05:46 639234055548642997
4 ms 198.27.79.61
17 2026-08-27 05:28 639234045267979603
223 ms 198.27.79.61
16 2026-08-27 05:11 639234034999717463
219 ms 198.27.79.61
15 2026-08-27 04:54 639234024739225358
111 ms 198.27.79.61
14 2026-08-27 04:37 639234014311170162
107 ms 198.27.79.61
13 2026-08-27 04:19 639234003806017640
109 ms 198.27.79.61
12 2026-08-27 04:02 639233993356203030
214 ms 198.27.79.61
11 2026-08-27 03:09 639233961301716608
110 ms 198.27.79.61
10 2026-08-27 02:51 639233950834200647
219 ms 198.27.79.61
9 2026-08-27 02:34 639233940431849026
208 ms 198.27.79.61
8 2026-08-27 02:17 639233930110596398
109 ms 198.27.79.61
7 2026-08-27 01:59 639233919705434540
1378 ms 198.27.79.61
6 2026-08-27 01:42 639233909452807845
116 ms 198.27.79.61
5 2026-08-27 01:25 639233899096420820
217 ms 198.27.79.61
4 2026-08-27 01:08 639233888707824939
109 ms 198.27.79.61
3 2026-08-27 00:50 639233878461203802
117 ms 198.27.79.61
2 2026-08-27 00:33 639233868060868209
795 ms 198.27.79.61
1 2026-08-27 00:16 639233857450922991
214 ms 198.27.79.61