Stripe outage history and live incidents

From 00:00–03:00 UTC October 6th, we saw elevated errors on Swish payments as a result of scheduled maintenance. This is now resolved.

From 02:24–02:27 UTC, we saw a brief increase in HTTP 5XX processing errors. This is now resolved.

Sep 30, 03:40 UTC
Resolved - Between 00:42 and 02:24 UTC September 30th, we saw lower authorization rates on Visa network token transactions. This issue is now resolved.

Sep 30, 03:02 UTC
Monitoring - We're seeing improvement with authorization rates on Visa network token transactions, starting 02:24 UTC September 30th. We're continuing to monitor until the issue is fully resolved. We will provide further updates once we have observed sustained recovery.

Sep 30, 02:00 UTC
Identified - Some Visa transactions may experience lower authorization rates due to a network token processing issue, starting 00:53 UTC September 30th. Eligible payments can continue using card-number fallback. We're working to resolve the issue; no action is required.

From 00:05 UTC to 01:01 UTC, we saw elevated API errors. This issue is now resolved.

The partner issue affecting our support systems has been resolved. Stripe's live support channels have been restored and are operating normally. This issue has been resolved.

From 12:46–14:20 UTC, we saw elevated errors on Swish payments due to external impact on the Swish payment processor. This issue is now resolved and has returned to normal.

From 18:53 UTC to 19:18 UTC on 2026-08-29, we saw elevated errors on Swish payments due to a service degradation on the Swish side. This is now resolved. We will continue to monitor for any further issues and will provide updates if needed.

From 21:00 on Aug 16 to 01:50 on Aug 17 UTC, some Bancontact payments experienced elevated processing errors. This issue has now been resolved.

From 12:04 to 12:26 UTC on August 1st, we saw elevated error rates and response times with the Stripe API. The issue is resolved and we will continue to monitor.

From 23:55 July 31st - 00:17 August 1st UTC, we saw elevated error rates and response times with the API. We are now seeing recovery and will continue monitoring.