Live / Acquia / Incident
Acquia: Acquia has detected a service interruption affecting Acquia Source
Acquia · acquia.comMinor incidentResolved2026-10-09 00:42 UTC
Public — what happened
Summary
Acquia reported a problem with caching in its Source CMS product beginning on October 8, 2026 at 18:04 UTC, which left some customer sites unavailable. About an hour later, Acquia said it had found the cause, though it did not describe it publicly, and began working on a fix. By 23:48 UTC the company said most of the disruption had been addressed while work continued for sites still affected, and the incident was marked resolved at 00:42 on October 9.
Affected
Acquia Source
Timeline
- Started — 2026-10-08 18:04 UTC
- Investigating — 2026-10-08 18:04 UTC
- Identified — 2026-10-08 19:11 UTC (4 updates)
- Resolved — 2026-10-09 00:42 UTC · 6h 38m 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 Acquia 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 Acquia: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Acquia report →
More from Acquia
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.