Stripe outage history

Bancontact payments experienced elevated errors beginning at 10:44 PM UTC, prompting Stripe to investigate. A follow-up update at 11:09 PM UTC noted the issue persisted and was traced to an external factor outside Stripe's infrastructure, with impact limited to the Bancontact payment path.

From late 10:44 PM UTC through 6:34 AM UTC, the disruption continued until the Bancontact path returned to normal as the external condition was resolved. The Acquirers and payment methods component transitioned back to up, signaling the resolution after roughly eight hours.

Stripe reported elevated declines and slower response times for Mastercard payments beginning at 4:54 AM UTC, with the Acquirers and payment methods component affected. Mastercard transactions processed through Stripe likely experienced failures or delays during the outage window as Stripe investigated the issue.

The incident progressed with Stripe noting the outage was external to Stripe's infrastructure. By 5:42 AM UTC, elevated error rates and latency started to recover, and Mastercard-related processing returned to normal as the situation stabilized. The service was fully restored by 6:24 AM UTC while Stripe continued monitoring to confirm full resolution.

Users attempting to authorize Stripe Financial Connections encountered errors, causing a brief disruption to the authorization flow. Stripe core components flagged an issue and announced an investigation into increased authorization errors, with impact beginning at 12:04 AM UTC and lasting until 12:44 AM UTC.

By 12:44 AM UTC, Stripe had restored normal operation for the Financial Connections path as the issue was resolved. The disruption was localized to this feature and did not indicate a wider outage.

Stripe Global payments experienced a brief degradation as API errors and higher latency affected payment operations. The issue began around 12:44 AM UTC and was resolved by 12:54 AM UTC, after which Stripe confirmed recovery and ongoing monitoring. The disruption was global in scope but short-lived, with normal operation returning shortly after the incident window.

In Mexico, card payments were disrupted by elevated card authorization errors tied to an issuer in Mexico, affecting card transactions for Stripe users. The issue began around 2:25 AM UTC as Stripe initiated an investigation and the Acquirers and payment methods component was flagged as impacted. By 3:19 AM UTC a degraded payment experience was acknowledged and ongoing validation continued.

By 3:24 AM UTC the elevated errors were reported as recovering, and full resolution followed by 4:24 AM UTC. The disruption spanned roughly two hours, with users in Mexico potentially experiencing failed or delayed card transactions.

Stripe users experienced elevated API errors and slower responses affecting API clients for a short period. The issue involved Stripe core components and began at 12:04 PM UTC, with services returning to normal by 12:19 PM UTC after the status page indicated ongoing investigation and, later, recovery as the core components returned to normal operation.

Users attempting to pay with BLIK saw elevated error rates and slower processing as the BLIK payment pathway degraded. The issue affected the Acquirers and payment methods component and the Global payments component, resulting in partial disruption for those transactions.

Impact began at 9:44 PM UTC and lasted roughly fifty minutes. By 10:14 PM UTC the partner had identified the cause and was applying a fix, and services for the affected components returned to normal by 10:34 PM UTC.

Payments involving Mastercard began encountering elevated 3DS errors around 7:00 AM UTC, affecting Mastercard checkout authentication for some Stripe customers. The incident was tied to the Acquirers and payment methods component, and Stripe engaged with Mastercard to investigate. The status moved to a degraded state at 8:09 AM UTC as the team prepared updates and noted ongoing engagement.

By 9:04 AM UTC, there were signs of improvement while the Mastercard teams continued to work on the issue. The incident was reported as recovering later in the morning, with the status returning to normal at 9:19 AM UTC. Stripe emphasized continued monitoring and Mastercard collaboration through the updates. The impact appeared limited to Mastercard 3DS authentication during payments, with no indication of broader issues affecting other card networks.

Users attempting to pay with WeChat Pay faced elevated errors and failed transactions as Stripe’s Acquirers and payment methods component entered a degraded state starting at 7:10 AM UTC. Stripe noted the issue is external to Stripe and is causing increased error rates for WeChat Pay transactions, potentially impacting merchants relying on this payment method. User reports remained limited during the incident. Over the day, updates indicated progression toward a fix; at Jul 2, 2026 1:39 PM UTC the issue was acknowledged and Stripe said the cause had been identified by partners and a fix was being worked on. Later, at 7:24 PM UTC WeChat Pay confirmed they were addressing the issue and it would take time to implement. The incident was resolved by 3:59 AM UTC when the Acquirers and payment methods component returned to up.

Stripe reported a partial disruption affecting the P24 payment method within the Acquirers and payment methods component, leading to elevated error rates for P24 transactions. The issue was external to Stripe and began at 10:52 AM UTC, with services returning to normal as the disruption was resolved by 11:39 AM UTC.