Skip to content

Is Stripe down?

Right now

No. Stripe is operational.

No incidents reported.

Read from status.stripe.com · every 60s

For agents

proceed

Proceed.

GET upbutler.com/status/stripe/status.agent.json

MCP: upstream_status {"service":"stripe"}

Payments API, Checkout, webhooks and the Dashboard. A webhook delay looks like "payments work but nothing gets fulfilled".

What Stripe reports

Operational

Taken as is from Stripe's own status page API. Incident titles and component names below are theirs.

Open status.stripe.com

UpButler's independent probe

API edge is answeringHTTP 401 · 133 ms

One request without credentials to api.stripe.com every two minutes. An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.

Checked · up since 2026-10-10 01:24 UTC

Open at Stripe

Text written by Stripe, shown unchanged.

Stripe components

6 operational

  • Stripe APIOperational
  • Global paymentsOperational
  • Revenue and finance automationOperational
  • Banking-as-a-serviceOperational
  • Stripe core componentsOperational
  • Acquirers and payment methodsOperational

Stripe incidents, last 90 days

4 finished incidents seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by Stripe. A typical one lasted 1 h 39 min; the longest 6 h 33 min.

Started (UTC)IncidentImpactLasted
Elevated Swish errorsnone6 h 33 min
Elevated API errorsnone25 min
Visa authorization errorsnone1 h 39 min
Elevated API Errorsmajor19 min

Tell your outage from Stripe's

Declare that your project depends on Stripe. When one of your monitors fails while Stripe has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

upbutler.yaml
# upbutler.yaml
dependencies:
  - stripe
Ask before you retry
curl -s https://upbutler.com/status/stripe/status.agent.json
status.agent.json (live)
{
  "schema": "upbutler.upstream-status/v1",
  "service": "stripe",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": {
    "state": "up",
    "statusCode": 401
  }
}

Questions

Is Stripe down right now?
No. As of 2026-10-10 05:11 UTC, Stripe is operational. This page reads the status again every 60 seconds.
Where does this status come from?
From Stripe's own status page API at https://status.stripe.com. UpButler reads it once for everyone (not once per visitor) every 60 seconds with conditional requests, and shows it unchanged: incident titles and component names are Stripe's words.
What does UpButler's own Stripe check prove?
Every two minutes UpButler sends one request without credentials to the Stripe API edge (api.stripe.com). Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while Stripe reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
How can my agent or app check Stripe status?
Fetch https://upbutler.com/status/stripe/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"stripe"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Stripe's?
Add "stripe" to the dependencies of your UpButler workspace. When one of your monitors fails while Stripe has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in payments and commerce

UpButler is not affiliated with Stripe. Status and incident text belong to Stripe and are read from their public status source; the probe result is UpButler's own measurement.