Stripe outage history

Stripe Instant Payouts to cards in the US and Canada experienced elevated failure rates due to issuer-bank maintenance affecting payment networks. The incident began around Nov 1, 2026 5:00 AM UTC and led to payout disruptions during the maintenance window. Stripe flagged the issue on its status page at 12:34 PM UTC with Instant Payouts showing elevated issues, followed by a continued warning until the problem was resolved by 2:39 PM UTC as Stripe core components returned to normal. Users likely saw delays or failures when processing Instant Payouts to cards in affected regions during this window.

Stripe Issuing experienced elevated error rates for API requests involving new or updated cards between 5:13 PM UTC and 5:54 PM UTC. The issue impacted the Banking-as-a-service component and could have prevented issuers from creating or updating Issuing cards, causing failures for affected requests during that window. The incident progressed with further context from Stripe’s updates, indicating a fix was identified and work was underway to correct the affected card data.

A partial disruption affecting Blik payments began at 5:12 PM UTC. Stripe noted the issue was external to Stripe and caused elevated error rates for Blik transactions. The disruption impacted the Acquirers and payment methods component, meaning some Blik payments could fail or be delayed for users.

The incident was updated to a partial disruption at 6:04 PM UTC as teams investigated, with ongoing monitoring. By 7:04 PM UTC the issue had been resolved and normal Blik processing resumed, restoring typical payment flow.

Stripe experienced a partial disruption affecting the Bancontact payment method, external to Stripe, leading to elevated error rates for Bancontact transactions. The issue began at 9:03 PM UTC and the affected Acquirers and payment methods component entered a degraded state by 10:24 PM UTC. A small number of user reports described issues processing Bancontact payments, including a Sydney-area report of API connectivity problems at 10:33 PM UTC.

The incident was resolved by 1:59 AM UTC when the component returned to normal and Stripe status moved back to up. The disruption spanned several hours, primarily impacting Bancontact transactions during the window, with no indication of a broader Stripe outage.

Bancontact payments processed through Stripe experienced a partial disruption with elevated error rates beginning at 2:08 PM UTC. Stripe noted the issue was external to Stripe and affected Bancontact transactions, impacting merchants relying on this payment method. The problem fell under the Acquirers and payment methods area, with the scope spanning banks, card networks, and local payments. The incident was resolved by 4:49 PM UTC, roughly two hours and 41 minutes after it began.

The incident began around 7:19 AM UTC when Stripe flagged elevated errors affecting Revolut Pay and 3D Secure authentication for Revolut-issued card transactions. The issue was external to Stripe and primarily affected the Acquirers and payment methods component, causing Revolut Pay payments and Revolut-issued card payments to fail or be declined.

Over the next hours, Stripe updated that the problem persisted with elevated authorization errors and declines for Revolut-issued cards (10:34 AM UTC) and later noted a spike in cancellations and expired errors with PayByBank payments (10:49 AM UTC), attributed to an upstream partner outage and ongoing monitoring for recovery. By 1:09 PM UTC the Acquirers and payment methods component had returned to up, signaling partial recovery of the disruption for Revolut Pay and Revolut-issued card payments.

Stripe users attempting Mastercard payments experienced elevated declines and slower processing beginning around 6:39 PM UTC. The issue affected Mastercard transactions processed through Stripe's Acquirers and payment methods, resulting in failed charges and longer wait times for Mastercard-based payments.

Official updates indicated Mastercard authorization errors had recovered by 6:27 PM UTC, with continued validation to confirm full resolution. The incident was resolved as the Acquirers and payment methods component returned to normal by 8:54 PM UTC.

Stripe reported elevated declines on Visa payments, leading to higher transaction failures and slower processing for Visa cards. The issue affected the Acquirers and payment methods component and could have caused some merchants to experience failed authorizations or delays for Visa transactions.

Status updates showed ongoing investigation and collaboration with a partner to recover. The incident began at Oct 15, 2026 5:09 PM UTC and progressed with follow-up notes at 5:14 PM UTC and 5:24 PM UTC before the issue was resolved by 6:04 PM UTC.

Stripe reported a brief disruption in Amazon Pay payments, with elevated error rates and slower response times affecting checkout attempts that use Amazon Pay. The issue affected Amazon Pay flows and broader global payments processing, potentially causing some transactions to fail or time out. The impacted components were Acquirers and payment methods and Global payments. The incident began at 2:09 AM UTC and was resolved by 2:19 AM UTC, lasting about ten minutes. Stripe's status page noted the investigation into elevated errors and response times and indicated recovery as services returned to normal. Limiting user reports suggest the impact was brief.

Stripe experienced elevated errors on Swish payments affecting users processing transactions through Stripe Acquirers and payment methods. The issue appears to have started around 12:28 AM UTC, with Stripe publicly noting the elevated Swish errors as of Oct 6, 2026 12:34 AM UTC and indicating the team was investigating. As customers encountered failed or delayed Swish transactions, the incident persisted for several hours while the Swish path continued to be assessed. By 7:04 AM UTC, the component returned to normal, and Stripe moved the status back to up, signaling the partial outage had been resolved.