Is Stripe down right now?

Checking…

Verifying live status…

Our latest checks found Stripe responding normally. Live verification is running now.

Live latency
···
Reports · 5 min
···
Reports · 24 h
···
Verification tier
···
What's not working with Stripe?

Your report feeds the live outage-velocity detector. One click per 30 s.

Live latency (probe round-trip, ms)

User reports, last 24 hours

Outage history

last 30 days

Recent outages and issues we recorded for Stripe, based on our own checks. An episode opens on the second check that finds a problem, since a single adverse reading is not reported, and closes when a check finds the service normal again.

60 days agoToday

No problemsProblemsOutageNot monitored

···Observed uptime, 7 days
···Observed uptime, 30 days
···Episodes, last 30 days

    Comments

    Comments are hosted and moderated via Disqus. Spam is filtered automatically, readers can flag anything, and the thread loads only when you scroll to it so the rest of the page stays fast.

    Jump to comments

    How we check Stripe

    No evidence of problems with Stripe. Our last recorded check found it behaving normally. That does not rule out a fault affecting only some users or regions.

    Every check runs a four-tier cascade and stops at the first tier that gives a clear answer: Stripe's official status feed, then a direct HTTP probe, then an ICMP network ping, and finally reports from visitors. The Verification tier box above tells you which one produced the verdict you are looking at. When enough separate people report a problem for it to be well outside what Stripe normally sees, that counts as evidence too, which is how a partial fault can show here before an operator's own status page catches up.

    Stripe (stripe.com) is re-checked continuously, and this page picks up any change on its own, with no refresh needed.

    Common Stripe problems users report

    • Card charges failing or being declined at checkout
    • Checkout and Stripe.js failing to load on merchant sites
    • API calls returning errors, so orders cannot be taken
    • Webhooks delayed, leaving paid orders unfulfilled

    What to do when Stripe is not working

    First check the banner above. If it shows evidence of problems, the fault is most likely on Stripe's side and waiting is usually the only option. If it shows nothing wrong, read the decline code on the individual payment, which distinguishes insufficient funds and issuer fraud rules from anything on Stripe's side. Then check whether your publishable key, webhook endpoint or pinned API version changed recently.

    About Stripe

    Stripe is the payments infrastructure behind a large share of online checkouts, handling card charges, subscriptions and payouts for millions of businesses. When Stripe has problems the shops built on it stop taking money: cards are declined, checkout pages fail to load, and orders can go unfulfilled when webhooks stop firing.

    Official Stripe resources

    Cross-check an incident with the company's own channels:

    Frequently asked questions

    Is Stripe down right now?

    No. Our checks are finding no problems with Stripe right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Stripe continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

    What usually goes wrong with Stripe?

    The problems visitors report most often on this page are checkout or payment, API errors, webhooks not firing, 5xx error pages, website / app down, can't log in and slow or laggy. Those are the options the report button offers for Stripe, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

    Why is Stripe declining payments for me when this page says it is fine?

    Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Stripe specifically, a payment crosses Stripe, the card network and the customer's issuing bank, and Stripe controls only the first. Most declines come from the bank, and one issuer or one country can be failing while every other payment on your account succeeds. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

    How do I tell whether it is Stripe or my own connection?

    For Stripe, run a test-mode payment and read the decline code in the dashboard. Test mode succeeding while live payments decline points at the card networks or issuers rather than Stripe. One card failing on your site but working elsewhere points at your integration. A problem that follows you across networks and devices is very unlikely to be yours.

    What should I do while Stripe is down?

    If this page shows evidence of problems, the fault is most likely on Stripe's side. Specifically: do not retry a failed charge repeatedly. Repeated attempts on the same card trip the issuer's fraud rules and block your customer for far longer than the incident lasts. If webhooks are delayed, fulfil from the dashboard, because the money may already have been taken. Reporting it here helps other people see they are not alone.

    How does status.buzz check Stripe?

    Continuously, around the clock. Stripe publishes a machine-readable status feed, so our first check reads it directly and reports what Stripe itself says. If that feed is unreachable we fall back to a direct HTTP probe, then an ICMP ping, then reports from visitors. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

    Does Stripe have an official status page?

    Yes, at status.stripe.com, and it is linked further up this page. That is Stripe's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

    Is status.buzz affiliated with Stripe?

    No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Stripe or stripe.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Stripe's own support, not us.