CheckWebsiteNow

Live status check

Is Stripe down right now?

We check stripe.com from one measurement point when you open this page. This shows what we saw, not a worldwide verdict.

A fresh check of stripe.com runs in your browser. If no result appears, run the check on the start page.

Our last check

Not checked yet — a fresh check starts when you open this page.

About Stripe problems

Stripe problems can affect payments, API requests, the Dashboard, payouts or webhooks. Check the Stripe status page first, which lists the API, Dashboard and other components separately, then look at the request logs in the Stripe Dashboard to see the exact error. A declined card is a decision by the card issuer or by Stripe's fraud screening, not a Stripe outage.

Official information

Stripe official status page (verified )

Our check and Stripe's own status page can disagree. We test from one location and read only the homepage response. The provider reports what it knows about its own systems, such as sign-in, apps or single regions. A site can answer our check while one feature is broken, and a regional problem can affect one location but not another.

Stripe help pages

How this check works

  • One measurement location (single-self-hosted-probe), not a worldwide test.
  • We read only the response headers of the HTTPS homepage; page content and features are not tested.
  • We follow at most 5 HTTPS redirects and check every new address again.
  • The whole check stops after 10 seconds.
  • Results are reused for 60 seconds; this page refreshes its saved check at most every 10 minutes.

Full method and limits

Typical Stripe problems

An editorial list of typical problems, not based on live user reports.

  • Payments are declined Card declines come from the issuing bank or Stripe's fraud checks, so the decline code in the Stripe Dashboard tells you whether the customer should contact their bank.
  • API key is rejected The Stripe API answers 401 when the secret key is missing or wrong, so check that the key matches the mode you use and that test and live keys are not mixed. Guide: 401 Unauthorized
  • Too many API requests Stripe answers 429 when an integration sends too many requests too quickly, so retry with exponential backoff. Guide: 429 Too Many Requests
  • API server errors A 500-range error from the Stripe API points to a problem on Stripe's side, so retry with an idempotency key and check the Stripe status page. Guide: 500 Internal Server Error
  • Webhooks are not received The webhook event deliveries view in Stripe Workbench shows each delivery attempt and the HTTP status your server returned, which reveals timeouts or server errors.

General fixes: Payments

  1. Open the site directly Type the payment service's address yourself instead of following a link in an email or message. This avoids fake sign-in pages.
  2. Read your account notices Limits, security reviews and declined payments are explained in your account notifications. Read them before you contact the shop.
  3. Check activity before paying again If a payment page shows an error, look at your account activity first. A payment can go through even when the page fails.
  4. Developers: read the error code API errors name the problem, such as an invalid key or too many requests. Check the request log in the provider's dashboard before you retry.

Check another website

One measurement point. Results explain what we saw, not a worldwide verdict.