DNS response history for ns311.solo10.com

ns311.solo10.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-24. For this date, NameServerHistory found 31 DNS check records, 30 successful responses, 1 failed responses, and 457 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 ns311.solo10.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

457 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.126.113.141

Most recently resolved hosting IP on selected date

Successful Responses

30

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns311.solo10.com

Showing DNS history for 2026-08-24 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
31 2026-08-24 13:12 639231735407682062
175 ms 209.126.113.141
30 2026-08-24 12:19 639231703815441688
4 ms 209.126.113.141
29 2026-08-24 12:02 639231693747052549
121 ms 209.126.113.141
28 2026-08-24 11:46 639231683712487276
268 ms 209.126.113.141
27 2026-08-24 11:29 639231673513573868
118 ms 209.126.113.141
26 2026-08-24 10:36 639231641791249939
11 ms 209.126.113.141
25 2026-08-24 10:19 639231631866211033
4125 ms 209.126.113.141
24 2026-08-24 10:02 639231621644955316
233 ms 209.126.113.141
23 2026-08-24 09:45 639231611478799259
229 ms 209.126.113.141
22 2026-08-24 08:53 639231579923718211
147 ms 209.126.113.141
21 2026-08-24 08:36 639231569810702936
8 ms 209.126.113.141
20 2026-08-24 08:19 639231559762411619
115 ms 209.126.113.141
19 2026-08-24 08:02 639231549663595407
117 ms 209.126.113.141
18 2026-08-24 07:10 639231518076817246
2231 ms 209.126.113.141
17 2026-08-24 06:53 639231508078650885
127 ms 209.126.113.141
16 2026-08-24 06:36 639231498210697093
2019 ms 209.126.113.141
15 2026-08-24 06:20 639231488109699360
-
14 2026-08-24 05:27 639231456772510692
233 ms 209.126.113.141
13 2026-08-24 05:11 639231447084631185
115 ms 209.126.113.141
12 2026-08-24 04:55 639231437208519473
117 ms 209.126.113.141
11 2026-08-24 04:38 639231427209627490
130 ms 209.126.113.141
10 2026-08-24 03:46 639231395791246644
117 ms 209.126.113.141
9 2026-08-24 03:30 639231386075551458
166 ms 209.126.113.141
8 2026-08-24 03:13 639231376208713791
119 ms 209.126.113.141
7 2026-08-24 02:56 639231366170589276
122 ms 209.126.113.141
6 2026-08-24 02:04 639231334732159368
129 ms 209.126.113.141
5 2026-08-24 01:48 639231325035670078
8 ms 209.126.113.141
4 2026-08-24 01:31 639231315132253837
121 ms 209.126.113.141
3 2026-08-24 01:14 639231305014280808
142 ms 209.126.113.141
2 2026-08-24 00:22 639231273779380675
130 ms 209.126.113.141
1 2026-08-24 00:06 639231264180839154
2010 ms 209.126.113.141