Stripe's status page logged one incident on 25 September 2026: elevated error rates and response times for payments made with Klarna. The fault sat with Stripe's acquirers and payment methods component and lasted 1h 20m, and it was Stripe's to fix, not yours.
Started
06:23 UTC
Duration
Lasted 1h 20m
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, Global payments
What happened?
Stripe opened an investigation at 06:23 UTC, saying it was looking into elevated error rates and response times with payments. At 07:42 UTC it posted a resolution, which narrowed the problem down: from 06:03 to 06:26 UTC, payments made using Klarna saw elevated errors and response times. That means the window Stripe actually confirms as broken, 06:03 to 06:26, is shorter than the 1h 20m the incident stayed open on the status page. Two components were listed against this incident: acquirers and payment methods, and global payments. Only two updates were filed in total, the opening note and the resolution, so there is no further detail on what caused the Klarna errors or why they cleared. No user reports came in during this window. Stripe's status page does not say why Klarna specifically was affected rather than other payment methods. Over the past 90 days Stripe has logged 26 incidents with a median duration of 1 hour 14 minutes, so this one ran close to typical length for them. Across all time, Stripe averages 3.7 incidents a month over 236 total, so a single Klarna-specific errors incident is not unusual for their track record.
Learning
UptimeRobot's own probes, which check Stripe's API from the EU and North America every 60 seconds, read 100% uptime across the last 24 hours, 7 days and 30 days, and this incident is not registered against those checks. That is not a contradiction. The fault was inside Klarna payment processing on Stripe's side, a specific payment method path rather than the core API endpoint your monitoring and UptimeRobot's probes are built to test. If your product only checks whether Stripe's API answers, you would have seen exactly what UptimeRobot's probes saw: nothing wrong. The actual symptom showed up only to users attempting to pay with Klarna during that 23-minute confirmed window, which is a narrow enough slice that uptime checks on the general API surface would miss it entirely. This is the recurring shape of payment provider incidents: the failure lives in one payment method or acquirer path, not the whole service, so a green API check and a real customer-facing error can both be true at once. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
