DNS response history for ns2.rapiddc.net

ns2.rapiddc.net 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-25. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 275 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.rapiddc.net.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

275 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.38.250.203

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 ns2.rapiddc.net

Showing DNS history for 2026-08-25 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-25 09:19 639232461630217327
67 ms 185.38.250.203
26 2026-08-25 09:02 639232451282965990
75 ms 185.38.250.203
25 2026-08-25 08:44 639232440814614938
88 ms 185.38.250.203
24 2026-08-25 08:27 639232430410720425
33 ms 185.38.250.203
23 2026-08-25 08:10 639232420003096185
2014 ms 185.38.250.203
22 2026-08-25 07:52 639232409467287444
38 ms 185.38.250.203
21 2026-08-25 07:35 639232399077195997
94 ms 185.38.250.203
20 2026-08-25 07:17 639232388731528337
70 ms 185.38.250.203
19 2026-08-25 07:00 639232378288598612
43 ms 185.38.250.203
18 2026-08-25 06:07 639232346196373643
69 ms 185.38.250.203
17 2026-08-25 05:50 639232336112370741
68 ms 185.38.250.203
16 2026-08-25 05:33 639232326146508970
42 ms 185.38.250.203
15 2026-08-25 05:17 639232316189381720
3 ms 185.38.250.203
14 2026-08-25 05:00 639232306217998913
3 ms 185.38.250.203
13 2026-08-25 04:43 639232296255744174
34 ms 185.38.250.203
12 2026-08-25 04:26 639232286095760789
5 ms 185.38.250.203
11 2026-08-25 04:10 639232276086186273
75 ms 185.38.250.203
10 2026-08-25 03:53 639232265900986425
99 ms 185.38.250.203
9 2026-08-25 03:36 639232255723518075
45 ms 185.38.250.203
8 2026-08-25 03:19 639232245484452890
63 ms 185.38.250.203
7 2026-08-25 03:02 639232235157175331
68 ms 185.38.250.203
6 2026-08-25 02:08 639232203197189095
71 ms 185.38.250.203
5 2026-08-25 01:51 639232192844564298
49 ms 185.38.250.203
4 2026-08-25 01:34 639232182496008942
39 ms 185.38.250.203
3 2026-08-25 01:17 639232172197053132
4087 ms 185.38.250.203
2 2026-08-25 00:23 639232140250307418
38 ms 185.38.250.203
1 2026-08-25 00:06 639232129927860324
41 ms 185.38.250.203