Live / sipgate / Incident
sipgate: Nachbearbeitungszeit länger als konfiguriert
sipgate · sipgate.deMajor incidentResolved2026-10-12 16:17 UTC
Public — what happened
Summary
sipgate said that starting at 09:20 UTC on 2026-10-12, the after-call wrap-up time set in the sipgate Web-Account was not being applied correctly, so some users stayed unavailable for incoming calls longer than they had configured. As a workaround, the company advised ending the wrap-up period by hand in the sipgate app. An apparent fix around 11:21 UTC did not hold, and the problem returned at 11:45 UTC; by 12:53 UTC sipgate said new calls were no longer affected and it was watching the situation, without naming a cause. The incident was marked resolved later that day.
Affected
Telephony, sipgate Apps, satellite App
Timeline
- Started — 2026-10-12 09:20 UTC
- Investigating — 2026-10-12 09:20 UTC
- Identified — 2026-10-12 11:21 UTC
- Investigating — 2026-10-12 11:45 UTC
- Monitoring — 2026-10-12 12:53 UTC
- Resolved — 2026-10-12 16:17 UTC · 6h 57m 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 43, 2026, our weekly internet health report.