Live / Volusion / Incident
Volusion: 3rd Party API Connection Issues
Volusion · volusion.comMinor incidentResolved2026-10-06 20:17 UTC
Public — what happened
Summary
Volusion reported a minor problem on October 6, 2026, starting at 15:22 UTC, in which outside services using third-party APIs were having trouble connecting to and sending data to Volusion stores. The company began looking into the reports right away and said by 15:53 UTC that it had put a fix in place and was watching how it performed. Volusion did not say what caused the problem, and it marked the incident resolved at 20:17.
Affected
Third-Party Services
Timeline
- Started — 2026-10-06 15:22 UTC
- Investigating — 2026-10-06 15:22 UTC
- Monitoring — 2026-10-06 15:53 UTC
- Resolved — 2026-10-06 20:17 UTC · 4h 55m 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 Volusion 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 Volusion: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Volusion report →
More from Volusion
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.