DNS response history for ns2.solvewins.com

ns2.solvewins.com 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 26 DNS check records, 26 successful responses, 0 failed responses, and 316 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.solvewins.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

316 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 08:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.186.185.145

Most recently resolved hosting IP on selected date

Successful Responses

26

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.solvewins.com

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
26 2026-08-27 08:36 639234160341037652
355 ms 103.186.185.145
25 2026-08-27 08:19 639234149799404224
636 ms 103.186.185.145
24 2026-08-27 08:02 639234139553286469
932 ms 103.186.185.145
23 2026-08-27 07:08 639234107183588293
290 ms 103.186.185.145
22 2026-08-27 06:51 639234096905435724
266 ms 103.186.185.145
21 2026-08-27 06:34 639234086579410775
269 ms 103.186.185.145
20 2026-08-27 06:16 639234076291157956
258 ms 103.186.185.145
19 2026-08-27 05:59 639234065981939454
275 ms 103.186.185.145
18 2026-08-27 05:42 639234055548642997
278 ms 103.186.185.145
17 2026-08-27 05:25 639234045267979603
268 ms 103.186.185.145
16 2026-08-27 05:08 639234034999717463
276 ms 103.186.185.145
15 2026-08-27 04:50 639234024739225358
269 ms 103.186.185.145
14 2026-08-27 04:33 639234014311170162
298 ms 103.186.185.145
13 2026-08-27 04:16 639234003806017640
269 ms 103.186.185.145
12 2026-08-27 03:58 639233993356203030
278 ms 103.186.185.145
11 2026-08-27 03:05 639233961301716608
274 ms 103.186.185.145
10 2026-08-27 02:48 639233950834200647
260 ms 103.186.185.145
9 2026-08-27 02:30 639233940431849026
265 ms 103.186.185.145
8 2026-08-27 02:13 639233930110596398
267 ms 103.186.185.145
7 2026-08-27 01:56 639233919705434540
274 ms 103.186.185.145
6 2026-08-27 01:38 639233909452807845
279 ms 103.186.185.145
5 2026-08-27 01:21 639233899096420820
292 ms 103.186.185.145
4 2026-08-27 01:04 639233888707824939
280 ms 103.186.185.145
3 2026-08-27 00:47 639233878461203802
275 ms 103.186.185.145
2 2026-08-27 00:29 639233868060868209
273 ms 103.186.185.145
1 2026-08-27 00:12 639233857450922991
273 ms 103.186.185.145