Live / Acoustic / Incident
Acoustic: Connect Issue Under Investigation - All regions
Acoustic · goacoustic.comMajor incidentResolved2026-10-06 08:08 UTC
Public — what happened
Summary
Acoustic said that starting at 08:56 UTC on 2026-10-05, jobs importing reference sets into Acoustic Connect were failing across all regions, leaving no records loaded and no error file. The company reported finding the cause at 09:32 UTC but did not describe it, and said a fix was in place by 12:42 UTC, after which it kept watching the service before closing the incident on 2026-10-06 at 08:08. According to Acoustic, audience imports and other Connect features kept working, scheduled imports would resume on their next run, and customers should manually rerun any one-time or API-triggered imports that failed.
Affected
Data, Data, Data
Timeline
- Started — 2026-10-05 08:56 UTC
- Investigating — 2026-10-05 08:56 UTC
- Identified — 2026-10-05 09:32 UTC
- Monitoring — 2026-10-05 12:42 UTC
- Resolved — 2026-10-06 08:08 UTC · 23h 13m 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 Acoustic 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 Acoustic: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Acoustic report →
More from Acoustic
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.