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

As listed on Sangoma’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Sangoma status & history page.

Related: Sangoma status & history. SquidGrid is not affiliated with Sangoma.