Is Stripe Down? How to Monitor Stripe's Status in Real-Time (And Alert Your Team Automatically)

Stripe processes over $1 trillion in payments annually — and like any infrastructure at that scale, it occasionally has incidents. Payment degradations, API slowdowns, webhook delays, checkout disruptions. When these happen, you and your customers notice immediately. But Stripe doesn't email you.

The only official channel is status.stripe.com — a page you have to visit manually and remember to check. This guide covers how to monitor it automatically and build a proper alerting system around Stripe incidents.

How to check if Stripe is down right now

The definitive source is status.stripe.com. Stripe maintains a real-time status page with components including:

• Stripe API
• Stripe Dashboard
• Checkout
• Radar (fraud detection)
• Billing
• Connect
• Webhooks

Stripe uses Atlassian Statuspage (now Atlassian Status) to publish incidents. Each component shows one of four states: Operational, Degraded Performance, Partial Outage, or Major Outage.

The problem with manual checking: by the time you think to check, your customers are already experiencing the issue — and possibly already filing tickets.

How to get automatic Stripe outage alerts

There are three approaches to automatic Stripe status monitoring:

Option 1: Stripe's built-in email subscription (limited)

At the bottom of status.stripe.com, you can subscribe to email updates. Stripe sends emails when incidents are created (typically 15–30 minutes after the incident began), updated, and resolved. This is better than nothing — but there's significant lag between incident start and the first notification.

Option 2: Poll the Statuspage API directly

Stripe's status page exposes a JSON API at https://status.stripe.com/api/v2/status.json and /api/v2/components.json. You can build a cron job that hits this endpoint every 60 seconds and triggers an alert when any component leaves "operational" status.

This is effective but requires:

• Maintaining cron infrastructure (or paying for it)
• Writing and maintaining the alerting code
• Handling edge cases (API rate limits, transient failures, duplicate alerts)

Option 3: Use a dedicated third-party status monitoring tool

Tools like StatusMirror are built specifically for this. They poll Stripe (and 24 other providers) every 60 seconds, de-duplicate alerts, and fire email notifications to your whole team within seconds of a status change. Setup takes 2 minutes.

What to do when Stripe is down

Having a runbook for Stripe incidents prevents chaotic triage. Here's what a good response workflow looks like:

1. Confirm via status.stripe.com — is the component affecting your use case (Checkout? API? Webhooks?) actually degraded?
2. Post a status update to your in-app banner and help center widget so customers see it before filing tickets
3. Alert your support team via Slack/email with the status and a canned response they can use
4. Pause non-critical payment flows if your architecture supports it — retry queues, deferred billing attempts, etc.
5. Monitor the resolution and send a post-incident summary to affected customers

Setting up a Stripe status widget on your help center

The single highest-leverage thing you can do is surface Stripe's live status directly on your help center or support page. When a customer's payment fails and they come to your help center to file a ticket, they immediately see: "Stripe: Degraded performance — we're aware."

Most customers won't file a ticket if they understand the problem is upstream and you're aware of it.

With StatusMirror, adding this to any webpage is two lines:

<div id="status-mirror" data-org="your-org-id"></div>
<script src="https://statusmirror.vercel.app/embed/v1.js" defer></script>

The widget auto-updates every 60 seconds and shows real-time status for all your monitored providers.

Common Stripe incidents and what they mean for your product

API degraded performance: Stripe API calls are slower than usual or intermittently failing. Retry logic on your backend should handle most of this transparently, but checkout conversion rates will drop.

Webhook delivery issues: Stripe webhooks are delayed or missing. This affects post-payment flows: subscription activations, license provisioning, invoice generation. Have a reconciliation job that can reprocess events from Stripe's event log.

Checkout/Payment Links degraded: Stripe-hosted checkout pages are loading slowly or failing. Your conversion rate will be impacted. Consider surfacing an in-app alert for users about to start a purchase flow.

Radar issues: Fraud detection is degraded. Some payments may not be evaluated correctly. Stripe typically fails open (allows more payments) during Radar incidents to minimize false positives.

How often does Stripe go down?

In 2025, Stripe reported approximately 99.97% API uptime — impressive, but at scale that still means roughly 2.5 hours of degraded API availability over the year. More importantly, Stripe distinguishes between "operational" (100%), "degraded performance," and "partial/major outage." There are far more partial degradation events than full outages — and those are the ones most likely to affect your customers silently.

Monitoring Stripe status automatically — and communicating proactively when incidents occur — is one of the highest-ROI operational investments a SaaS team can make.

Set up free Stripe status monitoring →