Stripe Status · History · Incident #4320
RESOLVEDElevated declines on Cartes Bancaires
Minor · Started Jun 5, 2026 · 5:33 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Stripe Status · History · Incident #4320
RESOLVEDMinor · Started Jun 5, 2026 · 5:33 AM
Duration
9h 8m
Severity
Minor
Detection lead
—
User reports
—
Summary
Between 07:23 UTC on June 4th and 13:51 UTC on June 5th, we saw elevated error rates and response times with some Cartes Bancaires payments. This is now resolved.
Started
Jun 5, 2026 · 5:33 AM
Resolved
Jun 5, 2026 · 2:41 PM
Duration
9h 8m
Severity
None
Event timeline
Identified
Jun 5 · 5:33 AM StripeWe’re currently seeing elevated error rates and response times with some Cartes Bancaires payments due to an issuer-side degradation starting 07:23 UTC June 4th. We believe this outage is outside of Stripe's infrastructure. This is likely impacting a number of payment processors. We’re continuing to monitor and will post further updates.
Identified
Jun 5 · 12:22 PM StripeWe are continuing to see elevated error rates and response times with some Cartes Bancaires payments due to an issuer-side degradation starting 07:23 UTC June 4th. We are actively monitoring and will provide a further update as more information becomes available.
Resolved
Jun 5 · 2:41 PM StripeBetween 07:23 UTC on June 4th and 13:51 UTC on June 5th, we saw elevated error rates and response times with some Cartes Bancaires payments. This is now resolved.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026