Live / sipgate / Incident
sipgate: Telefonie für sipgate Kunden, die über MS Teams telefonieren, beeinträchtigt
sipgate · sipgate.deMajor incidentResolved2026-11-09 15:09 UTC
Public — what happened
Summary
sipgate said that customers who make calls through Microsoft Teams via its service experienced restricted telephony starting at 12:41 UTC on 2026-11-09. The company said a component handling these calls had failed, and a backup copy took over automatically, but it was also under heavy load, so some calls were delayed and a few only connected on a second routing attempt. It said calls to and from Teams connected through its session border controller were affected too. sipgate said it reset the failed component, which returned to normal operation by 14:00 UTC, and the incident was marked resolved at 15:09 after a period of monitoring.
Affected
Telefonie
Timeline
- Started — 2026-11-09 12:41 UTC
- Investigating — 2026-11-09 12:41 UTC
- Identified — 2026-11-09 13:58 UTC
- Monitoring — 2026-11-09 14:00 UTC
- Resolved — 2026-11-09 15:09 UTC · 2h 28m 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 sipgate 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 sipgate: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the sipgate report →
More from sipgate
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.