Users may be unable to make or receive calls using SIP devices.
- Status
- Service degradation
- Feature
- Calling
- Region
- Not specified (all regions)
- Started
- Oct 21, 2026, 22:15 CEST
- Duration
- 12 h 40 min
- Last update
- Oct 22, 2026, 09:50 CEST
- Next update
- Oct 22, 2026, 14:00 CEST
Current status
Our fix is progressing through validation, alongside additional measures to support a safe and stable recovery. Once validation is complete, we'll deploy the fix to the affected infrastructure to begin restoring the affected functionality.
More info
Users may be unable to sign in to their SIP devices or encounter "Service Unavailable" errors.
Once a SIP device attempts to perform its next synchronization, the device will disconnect. Users will be unable to log back into those devices and therefore can't make or receive calls using those SIP devices.
Calling functionality using the Microsoft Teams web and desktop clients, or Teams Phone Devices are not impacted.
Scope of impact
Any user attempting to make or receive calls using SIP devices is impacted by this event.
Timeline
Every update Microsoft posted for this issue, newest first.
- Oct 22, 2026, 09:50 CEST
Our fix is progressing through validation, alongside additional measures to support a safe and stable recovery. Once validation is complete, we'll deploy the fix to the affected infrastructure to begin restoring the affected functionality.
- Oct 22, 2026, 04:58 CEST
We're continuing to validate our fix and the recovery of SIP devices within our internal environment. We're also validating additional protective measures before restoring the affected functionality. Once we've confirmed these changes are operating as expected, we'll begin our restoration actions and monitor affected SIP devices as they recover.
- Oct 22, 2026, 00:52 CEST
We’re validating a fix within our internal environments and monitoring how SIP devices recover after the fix is applied. This validation is also helping us determine how long affected devices may take to return to normal functionality once the fix is applied. Once validation is complete, we’ll use the results to guide our remediation and restoration actions.
- Oct 21, 2026, 22:20 CEST
We’ve identified the underlying root cause and we are working on developing a fix.