Stripe's Issuing API threw elevated errors for 4h 40m on 28 October 2026, affecting cards created or updated in a narrow 41-minute window. The fault sat inside Stripe's own card data, not in your integration.
Started
17:39 UTC
Duration
Lasted 4h 40m
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: Banking-as-a-service, Stripe API
What happened?
Stripe logged one incident on 28 October 2026, affecting the Stripe API and its Banking-as-a-service components. It started at 17:13 UTC and ran until 20:41 UTC, a total of 4h 40m, though Stripe's own update says the majority of errors had subsided by 19:32 UTC. The problem was narrow in scope: elevated API error rates hit Issuing cards that had been created or updated during a specific 41-minute window, 17:13 to 17:54 UTC. Cards outside that window were not implicated, according to Stripe's own updates. Stripe posted four updates over the course of the incident. The first, at 17:39 UTC, simply flagged elevated API errors and promised more soon. By 18:29 UTC Stripe said it had identified the cause and was working on a fix, though it did not publish what that cause was. At 20:13 UTC Stripe said it was correcting the affected card data directly. The final update, at 21:08 UTC, confirmed full resolution at 20:41 UTC and that the affected card data had been corrected. No user reports were filed during the window on this page. Stripe's status history shows 31 incidents in the last 90 days, with a median duration of 1 hour 35 minutes, so this incident ran notably longer than Stripe's recent typical outage.
Learning
UptimeRobot's own probes against Stripe's API, run from EU and NA regions every 60 seconds, logged 100% uptime for the day, the week and the month, and this incident was not registered against those probes. That is not a contradiction. The fault here lived inside Stripe's card data for a specific batch of Issuing cards created in a 41-minute window, not in the API's basic availability, so a synthetic check hitting the API endpoint would see normal responses while your specific Issuing calls failed. This is the shape to watch for with any payments or banking-as-a-service provider: the endpoint is up, but the data behind a subset of requests is broken, and that only shows up when you are actually exercising the affected objects. Watching your own endpoints would not have caught this either, since your integration was correctly calling a Stripe API that was itself returning bad results for a narrow set of cards. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.