Live / FastSpring / Incident
FastSpring: Webhook delivery
FastSpring · fastspring.comMinor incidentResolved2026-10-16 00:39 UTC
Public — what happened
Summary
FastSpring reported a minor issue affecting webhook delivery, the automatic notifications it sends to sellers, which began at 23:50 UTC on 2026-10-15. The company said only some sellers might be affected and that it was investigating. It said any webhooks that failed to arrive would be retried under its normal retry process once the problem was fixed. FastSpring marked the incident resolved at 00:39 on 2026-10-16, and its posted text did not name a cause.
Affected
FastSpring System
Timeline
- Started — 2026-10-15 23:50 UTC
- Investigating — 2026-10-15 23:50 UTC
- Resolved — 2026-10-16 00:39 UTC · 49 min after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach FastSpring against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for FastSpring: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the FastSpring report →
More from FastSpring
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.