Live / Sangoma / Incident
Sangoma: Call Failure Issue - Fonality
Sangoma · sangoma.comMajor incidentResolved2026-10-16 00:08 UTC
Public — what happened
Summary
Sangoma said that Fonality users in Australia were unable to make or receive calls, starting at 23:55 UTC on 14 October 2026. The company said its engineers investigated through the early hours of 15 October and reported at 11:11 UTC that the problem had been identified and a fix was underway. Sangoma said a fix was put in place at 21:30 UTC that day and it began monitoring the results, and the incident was marked resolved at 00:08 UTC on 16 October.
Affected
Voice Services (Fonality) - Asia-Pacific
Timeline
- Started — 2026-10-14 23:55 UTC
- Investigating — 2026-10-14 23:55 UTC (2 updates)
- Identified — 2026-10-15 11:11 UTC (3 updates)
- Monitoring — 2026-10-15 21:30 UTC
- Resolved — 2026-10-16 00:08 UTC · 24h 13m 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.