DNS response history for dc2.rapidoservers.com

dc2.rapidoservers.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, 35 successful responses, 0 failed responses, and 93 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 dc2.rapidoservers.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

93 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.55.235.92

Most recently resolved hosting IP on selected date

Successful Responses

35

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 dc2.rapidoservers.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 15:05 639231797631669865
43 ms 162.55.235.92
34 2026-08-24 14:11 639231765923559455
55 ms 162.55.235.92
33 2026-08-24 13:55 639231755868832964
37 ms 162.55.235.92
32 2026-08-24 13:38 639231745628278877
40 ms 162.55.235.92
31 2026-08-24 13:21 639231735407682062
46 ms 162.55.235.92
30 2026-08-24 12:28 639231703815441688
24 ms 162.55.235.92
29 2026-08-24 12:11 639231693747052549
51 ms 162.55.235.92
28 2026-08-24 11:54 639231683712487276
46 ms 162.55.235.92
27 2026-08-24 11:38 639231673513573868
47 ms 162.55.235.92
26 2026-08-24 10:44 639231641791249939
44 ms 162.55.235.92
25 2026-08-24 10:28 639231631866211033
51 ms 162.55.235.92
24 2026-08-24 10:11 639231621644955316
45 ms 162.55.235.92
23 2026-08-24 09:54 639231611478799259
54 ms 162.55.235.92
22 2026-08-24 09:01 639231579923718211
49 ms 162.55.235.92
21 2026-08-24 08:45 639231569810702936
5 ms 162.55.235.92
20 2026-08-24 08:28 639231559762411619
30 ms 162.55.235.92
19 2026-08-24 08:11 639231549663595407
21 ms 162.55.235.92
18 2026-08-24 07:18 639231518076817246
59 ms 162.55.235.92
17 2026-08-24 07:02 639231508078650885
3 ms 162.55.235.92
16 2026-08-24 06:45 639231498210697093
27 ms 162.55.235.92
15 2026-08-24 06:29 639231488109699360
53 ms 162.55.235.92
14 2026-08-24 05:36 639231456772510692
40 ms 162.55.235.92
13 2026-08-24 05:20 639231447084631185
5 ms 162.55.235.92
12 2026-08-24 05:03 639231437208519473
2 ms 162.55.235.92
11 2026-08-24 04:47 639231427209627490
48 ms 162.55.235.92
10 2026-08-24 03:54 639231395791246644
2 ms 162.55.235.92
9 2026-08-24 03:38 639231386075551458
3 ms 162.55.235.92
8 2026-08-24 03:22 639231376208713791
51 ms 162.55.235.92
7 2026-08-24 03:05 639231366170589276
51 ms 162.55.235.92
6 2026-08-24 02:13 639231334732159368
4 ms 162.55.235.92
5 2026-08-24 01:56 639231325035670078
46 ms 162.55.235.92
4 2026-08-24 01:40 639231315132253837
44 ms 162.55.235.92
3 2026-08-24 01:23 639231305014280808
51 ms 162.55.235.92
2 2026-08-24 00:31 639231273779380675
50 ms 162.55.235.92
1 2026-08-24 00:15 639231264180839154
2017 ms 162.55.235.92