Live / Sangoma / Incident
Sangoma: Emergency Maintenance - Multiple Portals
Sangoma · sangoma.comMinor incidentResolved2026-11-13 02:31 UTC
Public — what happened
Summary
Sangoma said it began emergency maintenance on November 12, 2026 at 17:29 UTC that affected two of its portals, netops.sangoma.com and ftp.sangoma.com, and that its engineers were investigating. About four hours later it reported that netops.sangoma.com was working again while engineers kept working on ftp.sangoma.com. Sangoma also announced a separate emergency maintenance on PBXact Cloud, starting at 7:15 PM Eastern and expected to last around an hour, with no service interruption expected. The incident is marked resolved as of 02:31 UTC on November 13, and no cause was given in the posted updates.
Affected
Voice Services (PBXact Cloud), NetOps (netops.sangoma.com), ftp.sangoma.com
Timeline
- Started — 2026-11-12 17:29 UTC
- Investigating — 2026-11-12 17:29 UTC (6 updates)
- Resolved — 2026-11-13 02:31 UTC · 9h 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 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 47, 2026, our weekly internet health report.