Live  /  Stripe  /  Incident

Stripe: Elevated Swish errors

Stripe · stripe.comResolved2026-10-06 07:04 UTC
Public — what happened

Summary

Stripe reported a rise in errors affecting Swish payments, which it said it first noticed at 00:28 UTC on October 6, 2026, and began investigating at 00:30 UTC. The company did not share a cause in its update. The incident was marked resolved at 07:04 the same day.

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 42, 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.