Inaccesible desde las 4 regiones de monitorización
HTTPS · 208 ms
Checked 1s ago·4/4 regions returned data·every 5 min · HTTP probe·direct probe, not crowd-reported
Resultados por región
🇺🇸US EastCAÍDO
—HTTP 503
🇺🇸US WestCAÍDO
—HTTP 503
🇬🇧EuropeCAÍDO
—HTTP 503
🇸🇬AsiaCAÍDO
—HTTP 503
Detalles HTTP
HTTP status
503
Response time
208 ms
Region consensus
0/4 reachable
24h success rate
0% (0/1 probes)
Desglose de tiempos
DNS lookup
87 ms
TCP connect
33 ms
TLS handshake
14 ms
First byte
74 ms
Total
208 ms
Red
Host
rappi.com
Port
443
Transport
HTTPS
Qué significa
Rappi failed in all 4 regions.
This is a confirmed outage. Most users worldwide are affected. Check the provider's status page or socials for an ETA — no client-side fix will help.
Qué hacer ahora
Wait it out
Confirmed outages need fixing on the provider's side. Nothing you do locally will change the result.
Check related
Scroll to related services below to see if the outage is provider-wide.
Re-run
Reload this page to re-probe — we check on-demand as well as on the 5-minute cadence.
FAQ
Why is Rappi down right now?
Outages typically come from CDN/DNS issues, failed deploys, regional routing problems, or DDoS. We can't see Rappi's internal cause — we only confirm reachability from each monitoring region. If all 4 regions failed, it's a confirmed outage on Rappi's side. If only some failed, the impact is regional.
Is Rappi down for everyone or just me?
Look at the per-region grid above. If every region succeeded, the issue is local to your network — flush DNS, switch networks, or disable your VPN. If two or more regions failed, the outage is on Rappi's side.
How often does isitdown.io re-check Rappi?
Every 5 minutes via background HTTP probes from US East, US West, Europe, and Asia. You can also re-run on demand by reloading — the verdict above reflects the latest probe.
Status badge
Embed a live status badge on your site, README, or status page. Updates automatically — same status-aware SVG the rest of isitdown.io uses.
We send a GET request to the target URL from each region and time the full response.
Se considera CAÍDO si
Every region fails the request (connect refused, DNS error, timeout, or HTTP 5xx).
Se considera DEGRADADO si
At least one region succeeds but at least one fails — the outage is partial or regional.
Detalle
Per-region results include HTTP status code, response time, and best-effort DNS / connect / TLS / first-byte phase timings when the Node HTTP client exposes them.
Cadencia
Every 5 minutes, in parallel across 4 monitoring regions (US East Virginia, US West Oregon, Europe London, Asia Singapore).
Objetivos con límite de tasa
If a host returns 429 or consistently drops connections from our IPs, we cap retries at 3 and report the last observed status — we do not flood the target to confirm the outage.
Fuente de datos
Direct probes from our monitoring infrastructure. We do not aggregate crowd reports, Twitter mentions, or DownDetector signals — every result on this page is a live network request.