Live / sipgate / Incident
sipgate: Telefonie für sipgate Kunden, die über MS Teams telefonieren, beeinträchtigt
sipgate · sipgate.deMajor incidentResolved2026-11-11 16:01 UTC
Public — what happened
Summary
sipgate said that customers who make calls through Microsoft Teams using sipgate were again experiencing restrictions, and it began looking into this on 10 November 2026 at 13:01 UTC. Later that day the company said it had found that demand on its system had grown steadily over recent months and had at times reached the system's capacity limits. It said it had moved one server to more powerful hardware, planned to upgrade the second server that evening, and warned of a possible brief interruption during the switch. The incident is now marked resolved, with the end recorded as 11 November at 16:01.
Affected
Telefonie
Timeline
- Started — 2026-11-10 13:01 UTC
- Investigating — 2026-11-10 13:01 UTC
- Identified — 2026-11-10 16:38 UTC
- Resolved — 2026-11-11 16:01 UTC · 27h 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.