Live / Broadvoice / Incident
Broadvoice: Issues with GoContact Analytics
Broadvoice · broadvoice.comMinor incidentResolved2026-10-02 18:43 UTC
Public — what happened
Summary
Broadvoice reported a minor problem affecting its GoContact Analytics service, first posted on October 1, 2026 at 21:25 UTC. The company said at that point that it had already pinpointed the problem and was working on a fix, though it did not describe the cause or say which customers were affected. A fix was in place by 15:21 UTC on October 2, after which Broadvoice watched for further trouble before marking the incident resolved at 18:43 that day.
Timeline
- Started — 2026-10-01 21:25 UTC
- Identified — 2026-10-01 21:25 UTC
- Monitoring — 2026-10-02 15:21 UTC (2 updates)
- Resolved — 2026-10-02 18:43 UTC · 21h 18m 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 Broadvoice 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 Broadvoice: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Broadvoice report →
More from Broadvoice
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.