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

As listed on sipgate’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 sipgate 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 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.

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

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