Stripe Outage History

Stripe experienced a brief minor outage affecting the Acquirers and payment methods component. The incident began at 8:29 PM UTC when the component was downgraded to a degraded state, potentially causing intermittent payment processing issues for about five minutes. The problem was resolved by 8:34 PM UTC and the component returned to normal. The Stripe status page issued 2 updates during the incident, detailing the degraded performance and subsequent recovery.

The outage began at 12:04 PM UTC when Stripe's status page listed Partially Degraded Service for Stripe core components, and it was resolved by 12:54 PM UTC, for a total duration of about 50 minutes. Stripe provided two status updates documenting the degradation and subsequent recovery. The impact was limited to Stripe core components, with users potentially experiencing degraded performance or intermittent issues during the window.

Stripe experienced partial degradation affecting two key areas: Stripe core components and Acquirers and payment methods. The issue led to intermittent payment processing for merchants and customers. The incident began at May 5, 2025 3:14 PM UTC and persisted into May 6, 2025 8:49 PM UTC, lasting roughly 29 hours and 35 minutes. The impact and duration were reflected in the service's ability to reliably process transactions across affected pathways.

A brief minor outage impacted Stripe's Acquirers and payment methods, causing intermittent payment processing issues for about 1 hour and 15 minutes. The incident began at 10:59 AM UTC and was resolved by 12:14 PM UTC. Stripe posted two status updates during the incident as teams worked to restore services.

Stripe reported Partially Degraded Service for Acquirers and payment methods starting at Apr 23, 2025 7:54 PM UTC. Payment processing and card authorizations were intermittently impacted, affecting merchants relying on Stripe for transactions. The incident lasted until Apr 24, 2025 6:19 AM UTC, roughly 10 hours and 25 minutes.

Stripe core components experienced a minor outage starting Apr 16, 2025 5:09 PM UTC, resulting in degraded performance across Stripe's core APIs and related services used by developers and merchants.

The outage lasted approximately 30 hours and 40 minutes and was resolved by Apr 17, 2025 11:49 PM UTC when Stripe core components returned to normal operation.

During the incident, the Stripe status page posted two updates outlining the issue and its resolution, with impact centered on the core components.

Stripe core components experienced partial degradation, affecting services for about 1 hour and 40 minutes. The outage began on 12:04 PM UTC and was resolved by 1:44 PM UTC. Stripe issued 2 status updates during the incident as engineers investigated and worked to restore full functionality, with services returning to normal by the end of the period.

Stripe experienced a partial degradation affecting Acquirers and payment methods, potentially impacting some users' ability to process payments during the incident window. The issue began on 3:59 PM UTC and was resolved by 5:19 PM UTC.

Stripe's status page listed Acquirers and payment methods as affected and communicated remediation as services returned to normal. The incident lasted roughly 1 hour 20 minutes and included 2 official status updates as the situation progressed.

Stripe reported a brief degradation of its core components starting at Apr 8, 2025 6:59 AM UTC and resolving by Apr 8, 2025 7:04 AM UTC, with the status page transitioning from normal operation to a degraded state and back within a short window. The incident was addressed quickly, and the status page noted a return to normal after a brief disruption. The provider issued two status updates during the event.

Stripe experienced a partial degraded service affecting core payment processing and related settlements. Users reported issues such as payments failing and settlement reliability problems, with feedback from Dallas, Texas and Tokyo indicating disruptions in processing transactions. The incident reflected degraded functionality across payment flows for several days as Stripe communicated about the issue.