Stripe's API threw elevated errors for 21 minutes on 27 September 2026. Stripe's own status page confirms the fault sat on their side, in the API and core components, not in your integration.
Started
01:03 UTC
Duration
Lasted 21m
Source
IsDown
Next time
Stripe is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Stripe API, Stripe core components
What happened?
Stripe logged one incident on this date, titled "Elevated API Errors", affecting the Stripe API and Stripe core components. Stripe's status page says the problem actually began at 00:05 UTC, though the first update was posted later at 01:03 UTC when Stripe opened the incident as "investigating". That first update reads: "Starting 00:05 UTC, we've seen elevated failures with the API. We're investigating and will post an update as soon as possible." Eighteen minutes later, at 01:21 UTC, Stripe marked it resolved with a second update: "From 00:05 UTC to 01:01 UTC, we saw elevated API errors. This issue is now resolved." That puts the actual error window at roughly 56 minutes, even though Stripe's incident record spans 21 minutes from first post to resolution. Only two updates were filed in total, and both are shown here, so this is the entirety of what Stripe published on the matter. No further detail was given on what caused the elevated failures or how many requests were affected. No user reports were filed during this window. For context, Stripe has logged 26 incidents in the past 90 days with a median duration of 1 hour 14 minutes, and 236 incidents all-time at a rate of about 3.7 a month, so a short API error spell is not unusual for this provider.
Learning
UptimeRobot's own probes against Stripe's API, run from both EU and North American regions every 60 seconds, recorded 100% uptime over the past 24 hours, 7 days and 30 days, with no registration against this particular incident. That is not a contradiction. Stripe's elevated error rate may have affected only a portion of API calls, or a time window that our probe's polling interval simply did not land on, while still causing real failures for requests made during those 56 minutes. External checks like ours confirm whether an endpoint is reachable and responding, they cannot see error rates buried inside otherwise-successful connections. This is the general shape of a partial degradation: the service stays up by every outside measure, but a slice of real traffic through it fails anyway. If your own checks on Stripe looked clean that night, that is consistent with Stripe's own account, not a sign your monitoring missed something. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
