Is Stripe down right now?

Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.

Run the live check at the top of this page - it tests stripe.com from HostTracker's 300+ monitoring locations at once and tells you within seconds whether Stripe is reachable for everyone or only failing for you.

Run the live check at the top of this page - it tests stripe.com from HostTracker's 300+ monitoring locations at once and tells you within seconds whether Stripe is reachable for everyone or only failing for you.

Yes, and it's an important distinction to understand about Stripe specifically. The Dashboard at stripe.com and the live payments API at api.stripe.com that actually processes a checkout are separate systems, so the Dashboard can render fine, showing past transactions and settings without any issue, while the API path that handles a new charge right now is degraded or erroring. Checking api.stripe.com's own reachability, rather than judging by the Dashboard, is the more direct signal when checkouts themselves are the problem.

Almost certainly not. A decline is a response from the customer's card network or issuing bank, not from Stripe, and it happens after Stripe has already correctly forwarded the transaction for a decision - insufficient funds, a fraud flag, an expired card, and dozens of other bank-side reasons can all produce a decline with nothing wrong at Stripe. A genuine Stripe-side problem looks more like consistent errors or timeouts across many unrelated transactions and payment methods at once, not an individual decline.

It can be a delivery delay rather than a full failure, and it's worth checking both sides. Stripe sends webhook events to a URL a business's own server hosts, and a backlog or delay in that delivery pipeline can leave events arriving late without the underlying charges having failed at all. It's also worth confirming your own endpoint is reachable and responding correctly, since a receiving-side problem produces the identical symptom of missing events.

Not usually. Regional payment methods (bank transfers, local wallets, and similar options specific to one country or currency) can have incidents scoped narrowly to that method and region, while standard card payments and every other market continue processing normally through the same account. If only one payment method in one region is affected, that points at a regional incident rather than a platform-wide one.