Live / Acoustic / Incident
Acoustic: Connect Issue Under Investigation - US
Acoustic · goacoustic.comMinor incidentResolved2026-11-11 02:03 UTC
Public — what happened
Summary
Acoustic said it began investigating a problem with Acoustic Connect in the US at 19:01 UTC on 2026-11-10, in which imports were slow for some customers. It reported that import jobs could remain in a Running state for longer than normal and that new ones might wait in a queue before starting. By 21:00 UTC the company said contact import processing was back to normal and queued imports were being worked through, though customers with many queued imports might still see some delay. Acoustic said no action or resubmission was needed, did not give a cause in its updates, and the incident is marked resolved as of 02:03 UTC on 2026-11-11.
Affected
Data
Timeline
- Started — 2026-11-10 19:01 UTC
- Investigating — 2026-11-10 19:01 UTC
- Monitoring — 2026-11-10 21:00 UTC (2 updates)
- Resolved — 2026-11-11 02:03 UTC · 7h 02m 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 47, 2026, our weekly internet health report.