XTIUM incident
Users are not receiving incoming call notifications on their Webex App for mobile
XTIUM experienced a critical incident on August 12, 2026 affecting OBT - Webex, lasting 7h 35m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 12, 2026, 07:48 AM UTC
Our vendor Cisco is investigating an issue impacting the push notification service for Webex. Users of Webex using the Webex App for mobile are not receiving incoming call notifications on their mobile phones. There are no issues with making outbound calls or answering incoming calls on a laptop or desk phone. As a workaround, users can answer calls on their laptop or desk phone, or forward incoming calls to an alternative non-Webex phone number. Our vendor is working to restore services and apologizes for the inconvenience this may cause.
- identified Aug 12, 2026, 08:19 AM UTC
The vendor has identified the issue and is currently working towards service restoration. We will continue to monitor the progress closely and will provide the next update in one hour or sooner if significant progress occurs.
- identified Aug 12, 2026, 09:52 AM UTC
The vendor continues to work towards service restoration. We will provide the next update in an hour or sooner if new information becomes available.
- identified Aug 12, 2026, 10:50 AM UTC
The vendor continues to work towards service restoration. We will provide the next update in an hour or sooner if new information becomes available.
- identified Aug 12, 2026, 11:48 AM UTC
The vendor continues to work towards service restoration. We will provide the next update in an hour or sooner if new information becomes available.
- monitoring Aug 12, 2026, 12:04 PM UTC
The vendor has completed remediation activities, and services are now restored. They have updated the NS records for one of their name servers; please note that it may take 24–48 hours for the new configuration to propagate worldwide. This timeframe is not a limitation of our services, but rather the standard propagation time required by global DNS (GDNS) infrastructure to update across the internet. Consequently, some users may continue to experience this issue until their local GDNS provider picks up the new configuration. We will continue to monitor to ensure service stability.
- resolved Aug 12, 2026, 03:24 PM UTC
Services remain healthy and stable, and the issue is now resolved. We appreciate your patience while we addressed this service incident.