Skip to main content
Rapid7 logo

Is Rapid7 Down?

No — Rapid7 is up

Reachable from all 8 checked regions

Average response time: 436ms

Last checked · checks run every 6 hours

Official status page: https://status.rapid7.com

Rapid7 uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
540ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 19 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

19-day clean streak
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: no data
Sep 24: no data
Sep 25: 100.00% uptime, 16 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 29 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 31 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
370ms
DNS 81ms TCP 2ms TLS 7ms TTFB 342ms
arn
481ms
DNS 100ms TCP 1ms TLS 5ms TTFB 454ms
cdg
384ms
DNS 31ms TCP 1ms TLS 3ms TTFB 365ms
dfw
366ms
DNS 127ms TCP 1ms TLS 3ms TTFB 315ms
ewr
440ms
DNS 188ms TCP 1ms TLS 4ms TTFB 427ms
fra
307ms
DNS 52ms TCP 1ms TLS 3ms TTFB 272ms
gru
764ms
DNS 291ms TCP 1ms TLS 4ms TTFB 757ms
yyz
379ms
DNS 131ms TCP 8ms TLS 10ms TTFB 340ms

What Rapid7 does

Rapid7 sells security software and managed detection and response. Security teams use its Command Platform for vulnerability management, SIEM, application security, cloud security, attack surface management, automation and threat intelligence, fed by agents and collectors on their own networks. Each customer's data is stored in one region, such as us, us2, eu or me1, and incidents are usually scoped to one product in one region.

What an outage looks like

Command Platform logins fail, or dashboards open but cards spin or never load. In recent incidents Vulnerability Management dashboards and Query Builder returned no data, new Goals, SLAs and Remediation Projects could not be created, and APIv4 answered with 5XX errors. SIEM incidents show up as delayed detections, alerts and investigations, and a faulty collector upgrade in March 2026 left collectors offline in EU and US East 1 for days.

What to do about it

Open any Rapid7 product and read the region code at the front of its URL (us in us.idr.insight.rapid7.com), then check that product's group for your region on status.rapid7.com, where each has a User Interface and a Data Processing row. Rapid7 says other platform components store data while one is unavailable, so do not resend logs. If the support portal is down, Rapid7 has pointed customers to their account team.

Is it down for everyone, or just you?

If this page says Rapid7 is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Tenable
Tenable
Splunk
Splunk
Wiz
Wiz
Sophos
Sophos

Rapid7 outage FAQ

Why does Rapid7 show an incident when my product works?
Because the status page lists every product separately for every region. Status.rapid7.com has groups such as Vulnerability Management (US2), SIEM (EU) and Cloud Security (ME1), each split into a User Interface row and a Data Processing row, and most incidents touch one product in one region. The August 2026 detection-processing incident, for example, affected US-1 only. Match the group to your own product and region code.
Which Rapid7 region is my account in?
The prefix of your product URL tells you. Rapid7's documentation says the region code is the start of the domain, so us.idr.insight.rapid7.com means the us region. The supported codes are us, us2 and us3 for the United States, eu for Europe, ca for Canada, au for Australia, ap for Japan, me1 for the UAE and aps2 for India (Hyderabad). The status page uses the same names in upper case.
What do offline agents mean during a Rapid7 incident?
Offline means an agent has not reported its status to the platform in the last 10 minutes; it is not proof the host is down. Agent Management marks an agent stale after 15 days without contact. Rapid7's documentation says an agent that checks back in later reappears, which is common for assets that spend long periods without internet. Recheck agent counts once the status page reports recovery.
Will Rapid7 lose data during an outage?
Rapid7 designs the platform to hold data while one part is down. Its availability page says that if one component of the Insight platform is unavailable, other components store data until it is available again, and that data is replicated across several data centers within the customer's chosen region. Expect dashboards, alerts and investigations to catch up after recovery rather than resending logs yourself.
Is rapid7.com being down the same as the platform being down?
No. This page checks www.rapid7.com, the company website. The products run at region-specific addresses under insight.rapid7.com, such as us.idr.insight.rapid7.com, and status.rapid7.com does not list the website as a component. The website can load while your product region is degraded, and the reverse, so use the rows for your product and region to judge the platform itself.

How we measure this

  • We request Rapid7's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Rapid7 publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Rapid7 goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required