Live  /  Stripe  /  Incident

Stripe: Elevated Issuing errors from 17:13 - 20:41 UTC

Stripe · stripe.comMinor incidentResolved2026-10-28 22:15 UTC
Public — what happened

Summary

Stripe said it saw higher-than-normal error rates on API requests involving Issuing cards, starting around 17:13 UTC on October 28. The company said the problem affected cards that were created or updated in a window of roughly 17:13 to 17:54 UTC, and that it identified the cause and worked to correct the affected card data. In its last update at 21:08 UTC, Stripe said most errors had subsided by 19:32 UTC and that the errors fully ended at 20:41 UTC. Stripe's text describes the issue as resolved, though the status page still lists it as identified.

Affected

Stripe API, Banking-as-a-service

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