User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Entertainment
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: FTP Server Issue
Source: the vendor's status page · We are not affiliated with Sangoma.
Estimated fix: Not enough Sangoma history yet; similar Entertainment outages lasted 16 min (median, typically 8 min–24 min; 32 outages).
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Reachable from all 4 regions we check from.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 8 min ago. Last stored result reached it in 96 ms.
Major incident
FTP Server Issue Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 22:15 | 0 | 0.0 | 56 ms | 0 |
| 00:15 | 0 | 0.0 | 361 ms | 0 |
| 02:15 | 0 | 0.0 | 72 ms | 0 |
| 04:15 | 0 | 0.0 | 124 ms | 0 |
| 06:15 | 0 | 0.0 | 94 ms | 0 |
| 08:15 | 0 | 0.0 | 134 ms | 0 |
| 10:30 | 0 | 0.0 | 124 ms | 0 |
| 12:45 | 0 | 0.0 | 87 ms | 0 |
| 15:00 | 0 | 0.0 | 106 ms | 0 |
| 16:15 | 0 | 0.0 | 260 ms | 0 |
| 18:30 | 0 | 0.0 | 96 ms | 0 |
| 20:45 | 0 | 0.0 | 44 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
Atlanta FortiGate FW Upgrade
We'll be performing FortiGate firewall firmware upgrade at Atlanta datacenter. During the maintenance services from the firewall would drop several times up to 5 min each.
Chicago FortiGate FW Upgrade
We'll be performing FortiGate firewall firmware upgrade at Chicago datacenter. During the maintenance services from the firewall would drop several times up to 5 min each.
Los Angeles FortiGate FW Upgrade
We'll be performing FortiGate firewall firmware upgrade at Los Angeles datacenter. During the maintenance services from the firewall would drop several times up to 5 min each.
Switchvox SIP Trunking Maintenance - 11/17/26
During this maintenance window, we will be performing essential updates and improvements to enhance the stability and performance of Switchvox SIP Trunking. As a result, Switchvox Cloud customers and any Prem customers utilizing Switchvox/DCS Trunking may experience temporary downtime or reduced functionality. Maintenance date - 11/17/26 @ 10pm ET thru 11pm ET
Dallas FortiGate FW Upgrade
We'll be performing FortiGate firewall firmware upgrade at Dallas datacenter. During the maintenance services from the firewall would drop several times up to 5 min each.
San Francisco FortiGate FW Upgrade
We'll be performing FortiGate firewall firmware upgrade at San Francisco datacenter. During the maintenance services from the firewall would drop several times up to 5 min each.
Seattle FortiGate FW Upgrade
We will be undergoing scheduled maintenance during this time.
Switchvox SIP Trunking Maintenance - 11/19/26
During this maintenance window, we will be performing essential updates and improvements to enhance the stability and performance of Switchvox SIP Trunking. As a result, Switchvox Cloud customers and any Prem customers utilizing Switchvox/DCS Trunking may experience temporary downtime or reduced functionality. Maintenance date - 11/19/26 @ 10pm ET thru 11pm ET
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for Sangoma yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Sangoma goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
Sangoma, at sangoma.com, is one of the Entertainment services we monitor. Affordable business communications with cloud, hybrid, and on-premises options. Easily integrates voice, video, networking, and security.
Sangoma publishes an official status page at trust.sangoma.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with entertainment services: streams buffering or not starting, playback errors, and app sign-in problems.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 130 ms average, 44–361 ms range across 12 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: FTP Server Issue
We have not recorded a public Sangoma incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
130 ms on average over the last 24 hours (44–361 ms). Latest regional checks: US East 32 ms, US West 38 ms, Europe 54 ms, Asia-Pacific 873 ms.
Yes, at https://trust.sangoma.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For entertainment services, watch for streams buffering or not starting, playback errors, and app sign-in problems. If many people report Sangoma here at once, the problem is on Sangoma's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Sangoma. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.