DNS response history for com2.solocdn.cn

com2.solocdn.cn 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 27 DNS check records, 27 successful responses, 0 failed responses, and 410 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 com2.solocdn.cn.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

410 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 08:53

All timestamps shown in UTC

Latest Resolved IP on Selected Date

58.221.77.135

Most recently resolved hosting IP on selected date

Successful Responses

27

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 com2.solocdn.cn

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
27 2026-08-27 08:53 639234170713214496
238 ms 58.221.77.135
26 2026-08-27 08:36 639234160341037652
190 ms 58.221.77.135
25 2026-08-27 08:18 639234149799404224
219 ms 58.221.77.135
24 2026-08-27 08:01 639234139553286469
254 ms 58.221.77.135
23 2026-08-27 07:07 639234107183588293
594 ms 58.221.77.135
22 2026-08-27 06:50 639234096905435724
728 ms 58.221.77.135
21 2026-08-27 06:33 639234086579410775
640 ms 58.221.77.135
20 2026-08-27 06:16 639234076291157956
758 ms 58.221.77.135
19 2026-08-27 05:59 639234065981939454
2012 ms 58.221.77.135
18 2026-08-27 05:41 639234055548642997
664 ms 58.221.77.135
17 2026-08-27 05:24 639234045267979603
222 ms 58.221.77.135
16 2026-08-27 05:07 639234034999717463
232 ms 58.221.77.135
15 2026-08-27 04:50 639234024739225358
199 ms 58.221.77.135
14 2026-08-27 04:33 639234014311170162
252 ms 58.221.77.135
13 2026-08-27 04:15 639234003806017640
365 ms 58.221.77.135
12 2026-08-27 03:57 639233993356203030
624 ms 58.221.77.135
11 2026-08-27 03:04 639233961301716608
164 ms 58.221.77.135
10 2026-08-27 02:47 639233950834200647
471 ms 58.221.77.135
9 2026-08-27 02:29 639233940431849026
216 ms 58.221.77.135
8 2026-08-27 02:12 639233930110596398
341 ms 58.221.77.135
7 2026-08-27 01:55 639233919705434540
194 ms 58.221.77.135
6 2026-08-27 01:38 639233909452807845
297 ms 58.221.77.135
5 2026-08-27 01:20 639233899096420820
266 ms 58.221.77.135
4 2026-08-27 01:03 639233888707824939
223 ms 58.221.77.135
3 2026-08-27 00:46 639233878461203802
296 ms 58.221.77.135
2 2026-08-27 00:29 639233868060868209
217 ms 58.221.77.135
1 2026-08-27 00:11 639233857450922991
190 ms 58.221.77.135