Stripe's Instant Payouts to cards failed at elevated rates for 2 hours and 6 minutes on 1 November 2026, mostly affecting the US and Canada. Stripe attributes the failures to maintenance on the card issuing banks' side, not to its own systems.
Started
12:31 UTC
Duration
Lasted 2h 6m
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 core components
What happened?
Stripe logged a single incident on this day, starting at 12:31 UTC and running to resolution at 14:36 UTC, a total of 2 hours and 6 minutes. The incident title was "Elevated Instant Payouts failures" and it affected what Stripe lists as its core components, with Instant Payouts to cards as the specific feature in trouble. Stripe's first update said it was investigating elevated failure rates for Instant Payouts to cards "in some countries" and noted that, as of 05:00 UTC that day, a significant portion of the failures traced to issuer-bank maintenance on the payment networks. The 12:50 UTC update narrowed the geography to mainly Canada and the US. The resolution notice, posted at 14:36 UTC, gives a window of 05:00 to 14:00 UTC for the underlying issue and states that processing had returned to normal. Note the discrepancy in timestamps: Stripe's own incident clock starts at 12:31 UTC, but the text it published refers to a problem running since 05:00 UTC, well before the incident was opened. No cause beyond "issuer-bank maintenance" is given, and Stripe does not name which banks or networks were involved. No user reports were filed during this window on record. This was Stripe's only incident logged for the day, with one affected component area and three total updates published across the lifecycle.
Learning
Stripe's own API uptime checks from UptimeRobot's probes stayed at 100% across the 24 hour, 7 day and 30 day windows for the api component in both EU and NA regions, and this incident was not registered against those probes. That is consistent with what happened: the fault sat with card issuing banks' maintenance on payment networks, a layer outside Stripe's API availability and outside anything an external HTTP check against Stripe's endpoints would ever see. Your own monitoring of your integration would show the same thing, a working connection to Stripe, while payouts to specific cards in specific countries still failed. This is the shape to watch for with any payments provider: the API can answer every request correctly while a downstream network or bank-side process degrades the real-world outcome. Over the past 90 days Stripe has logged 31 incidents with a median duration of 1 hour 40 minutes, so this kind of partial, network-attributed failure is not rare for this provider. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.