Live  /  Stripe  /  Incident

Stripe: Elevated Blik errors

Stripe · stripe.comResolved2026-10-24 19:02 UTC
Public — what happened

Summary

Stripe reported a partial disruption affecting payments made with Blik, which led to more transaction errors than usual. The company said the problem began at 17:12 UTC on 2026-10-24 and described it as external to Stripe. Stripe posted its first update at 18:02 UTC saying it was investigating and monitoring, and the incident is now marked resolved as of 19:02.

Affected

Acquirers and payment methods

As listed on Stripe’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Stripe against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Stripe: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Stripe report →

More from Stripe

Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.

The full archive is on the Stripe status & history page.

Related: Stripe status & history. SquidGrid is not affiliated with Stripe.