Stripe Status
Official status for Stripe APIs, dashboard, and payment services.
Live Domain Check
Check if Stripe is down right now (stripe.com). Run a live multi-region check to see whether Stripe is offline for everyone or just you.
Get official Stripe outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
Stripe incidents can affect payment flows, webhook delivery, and dashboard operations differently. This checker helps distinguish Stripe-wide events from merchant-side integration issues.
For Stripe, incident signals are often feature-specific: Initial page load succeeds, then checkout session completion errors appear. Payment intent confirmation and webhook event delivery drift out of sync under load. If this matches what you see on stripe.com, it usually points to partial degradation instead of a full outage, so confirm with official status updates and a second-network retest.
Use official sources first, then social/community signals to estimate incident scope and speed of recovery.
Official status for Stripe APIs, dashboard, and payment services.
Official support for payments, API, and account operations.
API docs to validate endpoint expectations during incidents.
Real-time posts and official updates related to Stripe incidents.
Official teams often post outage status updates and recovery progress through these social channels.
Recognizing these patterns helps you avoid false assumptions and escalate with better evidence.
Practical steps to follow when stripe.com seems down. Use this checklist to confirm whether Stripe is down for everyone or only for you.
Run stripe.com in WebsiteDown.org first, then open stripe.com in your own browser. If results disagree, the issue is often local rather than global.
Check the official Stripe service status page and compare timestamps with your failed checks.
Test related hosts such as www.stripe.com, support.stripe.com. If they work while stripe.com fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for stripe.com, then share those details with Stripe support for faster triage and recovery.
Use these local troubleshooting steps after the down-check workflow when Stripe seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open stripe.com in your current browser, then test in a private window or second browser. If only one session fails, the issue is usually local cache, cookie, or extension state.
Sign out and sign back in one time, then retry the failing action on stripe.com. Avoid repeated password or security resets until you confirm this is not a broader Stripe issue.
Temporarily disable VPN, proxy, private DNS, and filtering extensions. Then switch between Wi-Fi and mobile data to isolate route-level differences.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Stripe support.
Run the automatic multi-region check on this page for stripe.com. If most regions fail at the same time, Stripe is likely experiencing a broader outage.
If only one or two regions fail, the issue is usually local to your route, resolver, device state, or account session. Recheck after 2 to 5 minutes and compare Wi-Fi with mobile data.
Use this order so you get reliable signal quickly:
Official dashboards are the source of record, but social channels can surface impact faster in the first minutes of an incident.
That usually means a route-specific or client-specific issue instead of full provider downtime. Common reasons:
Try a private window, switch networks, and compare with this page's regional result before making major local changes.
Use this quick triage sequence:
This keeps your troubleshooting efficient and avoids unnecessary account resets during provider-side incidents.