DNS response history for resolver2.opendns.com

resolver2.opendns.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 36 DNS check records, 36 successful responses, 0 failed responses, and 11 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 resolver2.opendns.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

11 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.67.220.220

Most recently resolved hosting IP on selected date

Successful Responses

36

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 resolver2.opendns.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
36 2026-08-24 15:06 639231807961539652
3 ms 208.67.220.220
35 2026-08-24 14:49 639231797631669865
18 ms 208.67.220.220
34 2026-08-24 13:56 639231765923559455
15 ms 208.67.220.220
33 2026-08-24 13:39 639231755868832964
3 ms 208.67.220.220
32 2026-08-24 13:22 639231745628278877
4 ms 208.67.220.220
31 2026-08-24 13:05 639231735407682062
7 ms 208.67.220.220
30 2026-08-24 12:13 639231703815441688
4 ms 208.67.220.220
29 2026-08-24 11:56 639231693747052549
9 ms 208.67.220.220
28 2026-08-24 11:39 639231683712487276
6 ms 208.67.220.220
27 2026-08-24 11:22 639231673513573868
78 ms 208.67.220.220
26 2026-08-24 10:29 639231641791249939
5 ms 208.67.220.220
25 2026-08-24 10:13 639231631866211033
3 ms 208.67.220.220
24 2026-08-24 09:56 639231621644955316
5 ms 208.67.220.220
23 2026-08-24 09:39 639231611478799259
5 ms 208.67.220.220
22 2026-08-24 08:46 639231579923718211
5 ms 208.67.220.220
21 2026-08-24 08:29 639231569810702936
3 ms 208.67.220.220
20 2026-08-24 08:12 639231559762411619
14 ms 208.67.220.220
19 2026-08-24 07:56 639231549663595407
3 ms 208.67.220.220
18 2026-08-24 07:03 639231518076817246
5 ms 208.67.220.220
17 2026-08-24 06:46 639231508078650885
6 ms 208.67.220.220
16 2026-08-24 06:30 639231498210697093
5 ms 208.67.220.220
15 2026-08-24 06:13 639231488109699360
108 ms 208.67.220.220
14 2026-08-24 05:21 639231456772510692
7 ms 208.67.220.220
13 2026-08-24 05:05 639231447084631185
12 ms 208.67.220.220
12 2026-08-24 04:48 639231437208519473
7 ms 208.67.220.220
11 2026-08-24 04:32 639231427209627490
3 ms 208.67.220.220
10 2026-08-24 03:39 639231395791246644
2 ms 208.67.220.220
9 2026-08-24 03:23 639231386075551458
4 ms 208.67.220.220
8 2026-08-24 03:07 639231376208713791
2 ms 208.67.220.220
7 2026-08-24 02:50 639231366170589276
2 ms 208.67.220.220
6 2026-08-24 01:57 639231334732159368
3 ms 208.67.220.220
5 2026-08-24 01:41 639231325035670078
2 ms 208.67.220.220
4 2026-08-24 01:25 639231315132253837
3 ms 208.67.220.220
3 2026-08-24 01:08 639231305014280808
31 ms 208.67.220.220
2 2026-08-24 00:16 639231273779380675
2 ms 208.67.220.220
1 2026-08-24 00:00 639231264180839154
4 ms 208.67.220.220