Live  /  sipgate  /  Incident

sipgate: Anrufer:innen auf Rufnummern von sipgate Rufnummern, die in das 2G-Netz eingebucht sind, erhalten kein Freizeichen

sipgate · sipgate.deMajor incidentResolved2026-11-12 09:16 UTC
Public — what happened

Summary

sipgate said that people calling sipgate numbers that ring on a mobile phone connected to the older 2G network did not hear a ringing tone, although the phone itself did ring. The company reported this starting at 08:34 UTC on 2026-11-11 and said it was working with its mobile network partner on a fix. Later that day at 15:13 UTC, sipgate said the behavior could no longer be reproduced and that it was monitoring, and the incident was marked resolved on 2026-11-12 at 09:16.

Affected

Mobilfunk

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 47, 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.