Live / Sangoma / Incident
Sangoma: PBXact Issue - registration failure
Sangoma · sangoma.comMinor incidentResolved2026-10-12 23:47 UTC
Public — what happened
Summary
Sangoma reported a minor problem on October 12, 2026, starting at 16:57 UTC, in which a limited group of PBXact Cloud customers were unable to register their phone connections. By 18:11 UTC the company specified that the failures involved SIP trunk registration, and said its engineers were looking into it. Sangoma said a fix was put in place by 18:58 UTC, and it marked the incident resolved at 23:47 after a period of monitoring. The company did not share a cause.
Affected
Voice Services (PBXact Cloud)
Timeline
- Started — 2026-10-12 16:57 UTC
- Investigating — 2026-10-12 16:57 UTC (3 updates)
- Monitoring — 2026-10-12 18:58 UTC
- Resolved — 2026-10-12 23:47 UTC · 6h 51m 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.