Stripe favicon

Stripe outage on 2026-11-14

stripestatus.com
November 2026 14 Minor incident

Stripe had two separate incidents on 14 November, one hitting the Stripe API and one hitting PayNow payments, together spanning most of the day. Both were Stripe-side faults by Stripe's own account, lasting 4h 48m and 4h 38m respectively.

Started

02:50 UTC

Duration

Lasted 4h 48m

Source

IsDown

Next time

Stripe is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

Affected components: Acquirers and payment methods, Stripe API

What happened?

The first incident started at 02:50 UTC, when Stripe reported elevated rate limits affecting some merchants, then widened that to elevated HTTP processing errors on the Stripe API. By 03:44 Stripe said error rates had returned to normal, giving a window of 02:34 to 03:01 UTC for the actual fault, and moved to monitoring. The final update at 07:35 UTC closed the incident as resolved, still citing the same 02:34 to 03:01 UTC window. That is a four hour and forty eight minute incident on the status page for a twenty seven minute fault, because Stripe kept the incident open to validate before resolving it. The second incident began at 17:46 UTC, reporting elevated errors on PayNow payments as of 17:31 UTC. It resolved at 22:24 UTC with a stated fault window of 16:20 to 21:40 UTC, and Stripe attributed the cause to something external to Stripe itself, without naming what. Two components were affected across the day: Stripe API and Acquirers and payment methods. No user reports were filed during either window on this page. Stripe has not published a post-mortem for either incident, so the API error cause beyond "elevated HTTP processing errors" is not on the record, and the external cause behind the PayNow errors is not detailed either.

Learning

UptimeRobot's own probes against Stripe's API, run from both EU and North America every 60 seconds, show 100% uptime across the 24 hour, 7 day and 30 day windows, with this incident not registered against them. That is not a contradiction. Our probes check that the API endpoint responds, not that every merchant's processing requests clear without error, and a spike in error rates for "some merchants" can sit entirely inside a green uptime number if the endpoint itself stays reachable. The PayNow incident is a clearer example of the same gap: Stripe itself says the fault was external, meaning it likely sat with a payment method provider or acquirer downstream of Stripe's own API, a layer no endpoint check on your side or ours would ever touch. If your own monitoring only watches your integration against Stripe, it will show green through exactly this kind of failure too, because your endpoint is fine, Stripe's endpoint is fine, and the money still fails to move. Over the last 90 days Stripe has logged 30 incidents with a median duration of 1 hour 59 minutes, so elevated error spikes like these are a known pattern for the service rather than a one off. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.