Live / Sangoma / Incident
Sangoma: TeamHub login & accessing issues - TeamHub
Sangoma · sangoma.comMajor incidentResolved2026-10-13 21:32 UTC
Public — what happened
Summary
Sangoma reported a major incident in which users had trouble signing in to and reaching its TeamHub service, beginning at 15:25 UTC on 2026-10-13. By 15:43 UTC, the company said its engineers had found what was behind the problem and put a fix in place, then watched to confirm it held. Sangoma did not describe the cause publicly, and the incident was marked resolved at 21:32 the same day.
Affected
TeamHub Web, TeamHub Desktop
Timeline
- Started — 2026-10-13 15:25 UTC
- Investigating — 2026-10-13 15:25 UTC
- Monitoring — 2026-10-13 15:43 UTC
- Resolved — 2026-10-13 21:32 UTC · 6h 06m 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 Sangoma 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 Sangoma: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Sangoma report →
More from Sangoma
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.