Loading status…
Stripe status · Payments & Finance · checked (2s ago)
Also searched as Stripe API, Stripe Checkout, Stripe Connect.
No — Stripe is not down. All Stripe systems are reported operational.
According to Stripe's official status page, Stripe was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Stripe's feed reported no outage in 100.00% of our checks.
Everything above is read from Stripe's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Stripe in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Stripe processes payments for a very large share of the internet — Checkout, the payments API, subscriptions and billing, Connect for marketplaces, and the dashboard. When Stripe is impaired, other companies' checkouts fail, which is why a Stripe incident is felt far beyond Stripe.
Stripe's status page separates the API from the dashboard, from Stripe.js and Checkout in the browser, and from webhook delivery. Webhooks are the component worth watching: Stripe retries failed deliveries for days, so a webhook incident delays fulfilment rather than losing it, and your system will catch up rather than needing a manual repair.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Stripe's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Stripe was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 2s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Stripe's status endpoint.
Stripe has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what Stripe posted itself — not every problem users hit.
resolved · Sep 16, 11:33 PM (3d ago)
resolved · Sep 16, 10:05 AM (3d ago)
resolved · Sep 16, 10:05 AM (3d ago)
resolved · Sep 13, 04:45 AM (7d ago)
resolved · Sep 10, 08:53 PM (9d ago)
resolved · Aug 30, 01:16 PM (20d ago)
resolved · Aug 29, 07:28 PM (21d ago)
resolved · Aug 29, 06:45 AM (21d ago)
resolved · Aug 16, 10:39 PM (34d ago)
resolved · Aug 15, 04:49 AM (36d ago)
resolved · Aug 8, 12:03 AM (43d ago)
resolved · Aug 6, 03:52 PM (44d ago)
resolved · Aug 1, 12:45 PM (49d ago)
resolved · Aug 1, 12:16 AM (50d ago)
resolved · Jul 29, 03:18 AM (53d ago)
resolved · Jul 24, 12:00 PM (57d ago)
resolved · Jul 21, 10:26 AM (60d ago)
resolved · Jul 20, 09:42 PM (61d ago)
resolved · Jul 17, 07:56 PM (64d ago)
resolved · Jul 15, 08:06 AM (66d ago)
A declined card is the issuing bank's decision, not a Stripe fault, and no status page will ever show it. Test and live modes are entirely separate — a key from the wrong mode fails in a way that looks systemic. If webhooks are not arriving, check your endpoint is reachable and returning 2xx quickly; Stripe disables endpoints that fail persistently, and that disabling survives the incident that caused it.
