On 24 October, Stripe's Blik payment method returned increased error rates for 1h 2m. Stripe says the fault sat outside its own systems, in the Blik network itself.
Started
18:02 UTC
Duration
Lasted 1h 2m
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
What happened?
Stripe opened an incident at 18:02 UTC titled "Elevated Blik errors", though the underlying disruption had actually begun earlier, at 17:12 UTC. The affected component was listed as Acquirers and payment methods, and the specific method named was Blik, a payment option used in Poland. Stripe's first update said the disruption was a partial one and was external to Stripe, meaning the fault originated with a third party in the Blik processing chain rather than in Stripe's own infrastructure. By the time Stripe posted its resolution update at 19:02 UTC, it reported that the actual problem window had run from 17:12 to 17:40 UTC, a narrower span than the hour between the first and last updates on the page. Stripe's language throughout was cautious: "some users may have experienced increased error rates", not a confirmed outage for all Blik transactions. No user reports were filed during this window, so there is no independent account of how the errors felt to anyone processing payments at the time. Stripe published two updates in total for this incident, an opening note and a closing one, with nothing in between. That single pair of filings is the entire public record of what happened. No post-mortem has been published, and Stripe has not said what the external fault actually was. Over the past 90 days Stripe has logged 31 incidents with a median duration of 1 hour 28 minutes, so this one ran shorter than typical. Across all time, Stripe has recorded 246 incidents at a rate of roughly 3.8 per month.
Learning
UptimeRobot's own probes, which check Stripe's API from EU and NA regions every 60 seconds, held 100% uptime across the 24 hour, 7 day and 30 day windows, and this incident was not registered against those checks. That is not a contradiction. The probes watch whether Stripe's API responds, and Stripe's API did respond throughout. The fault sat one layer down, inside a specific payment method's connection to an external network, which is the kind of failure that only shows up when a real transaction using Blik specifically fails to clear. If your product takes payments through Stripe and happened to route Blik transactions during that 17:12 to 18:14 UTC window, your checkout could have thrown errors while every uptime check you run against Stripe's API, and against your own servers, stayed green. This is the general shape worth remembering: payment method failures and API failures are different layers, and a clean API does not guarantee a clean payment. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.