DNS response history for ns2.toledogroup.com

ns2.toledogroup.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 35 DNS check records, 34 successful responses, 1 failed responses, and 376 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.toledogroup.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

376 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.14.29.220

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns2.toledogroup.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
35 2026-08-24 14:58 639231797631669865
193 ms 108.14.29.220
34 2026-08-24 14:05 639231765923559455
212 ms 108.14.29.220
33 2026-08-24 13:48 639231755868832964
204 ms 108.14.29.220
32 2026-08-24 13:31 639231745628278877
105 ms 108.14.29.220
31 2026-08-24 13:14 639231735407682062
12 ms 108.14.29.220
30 2026-08-24 12:21 639231703815441688
2102 ms 108.14.29.220
29 2026-08-24 12:04 639231693747052549
2145 ms 108.14.29.220
28 2026-08-24 11:48 639231683712487276
212 ms 108.14.29.220
27 2026-08-24 11:31 639231673513573868
5 ms 108.14.29.220
26 2026-08-24 10:38 639231641791249939
214 ms 108.14.29.220
25 2026-08-24 10:21 639231631866211033
107 ms 108.14.29.220
24 2026-08-24 10:04 639231621644955316
112 ms 108.14.29.220
23 2026-08-24 09:47 639231611478799259
207 ms 108.14.29.220
22 2026-08-24 08:55 639231579923718211
-
21 2026-08-24 08:38 639231569810702936
107 ms 108.14.29.220
20 2026-08-24 08:21 639231559762411619
5 ms 108.14.29.220
19 2026-08-24 08:04 639231549663595407
2003 ms 108.14.29.220
18 2026-08-24 07:12 639231518076817246
102 ms 108.14.29.220
17 2026-08-24 06:55 639231508078650885
207 ms 108.14.29.220
16 2026-08-24 06:39 639231498210697093
118 ms 108.14.29.220
15 2026-08-24 06:22 639231488109699360
205 ms 108.14.29.220
14 2026-08-24 05:30 639231456772510692
217 ms 108.14.29.220
13 2026-08-24 05:13 639231447084631185
232 ms 108.14.29.220
12 2026-08-24 04:57 639231437208519473
109 ms 108.14.29.220
11 2026-08-24 04:40 639231427209627490
202 ms 108.14.29.220
10 2026-08-24 03:48 639231395791246644
210 ms 108.14.29.220
9 2026-08-24 03:32 639231386075551458
24 ms 108.14.29.220
8 2026-08-24 03:15 639231376208713791
210 ms 108.14.29.220
7 2026-08-24 02:59 639231366170589276
102 ms 108.14.29.220
6 2026-08-24 02:06 639231334732159368
208 ms 108.14.29.220
5 2026-08-24 01:50 639231325035670078
121 ms 108.14.29.220
4 2026-08-24 01:33 639231315132253837
223 ms 108.14.29.220
3 2026-08-24 01:17 639231305014280808
224 ms 108.14.29.220
2 2026-08-24 00:24 639231273779380675
9 ms 108.14.29.220
1 2026-08-24 00:09 639231264180839154
2100 ms 108.14.29.220