Live / Acquia / Incident
Acquia: Acquia Source CMS – Configuration Push Failures
Acquia · acquia.comMinor incidentResolved2026-11-13 20:04 UTC
Public — what happened
Summary
Acquia said customers could not push configuration updates to their Source CMS sites, and it began investigating at 15:05 UTC on 2026-11-13. By 19:06 UTC the company said it had found the cause, and at 19:32 UTC it said it had put a fix in place and was watching to confirm updates were going through normally. The incident is marked resolved as of 20:04 UTC, and Acquia rated it minor.
Affected
Acquia Source
Timeline
- Started — 2026-11-13 15:05 UTC
- Investigating — 2026-11-13 15:05 UTC (2 updates)
- Identified — 2026-11-13 19:06 UTC
- Monitoring — 2026-11-13 19:32 UTC
- Resolved — 2026-11-13 20:04 UTC · 5h 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 47, 2026, our weekly internet health report.