Sentinel experienced a minor incident on December 13, 2022 affecting Telephone System and Sentinel Voice, lasting 8d 10h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Dec 13, 2022, 10:47 AM UTC
We are currently investigating an issue relating to Inbound calls not always coming through. Update will follow shortly
- identified Dec 13, 2022, 03:00 PM UTC
We have identified the issues with inbound, as well as outbound calling. We are working on implementing a fix to resolve this as soon as possible.
- identified Dec 13, 2022, 08:10 PM UTC
Update - As we continue to address the issue of malicious call traffic, we are currently implementing measures to ringfence numbers identified as most severely impacted by this problem, in order to reduce the overall load on our platform and mitigate the negative effects of the influx of incoming calls. Thank you for your patience as we continue to work to resolve this issue.
- identified Dec 14, 2022, 01:24 PM UTC
Update - We have continue to monitor the malicious traffic on the network and, we have been in contact with the origin carriers for the numbers. The carriers have deemed the traffic to be of a robotic nature, and we have been working closely with getting this resolved. The carriers have initiated the process of blocking the Caller Line Identification (CLI) numbers that are causing the influx of concurrent malicious calls. We are expecting regular updates from the carriers, and we will share these updates as we receive them.
- identified Dec 15, 2022, 05:49 PM UTC
This afternoon mitigating actions were taken by origin carriers via our upstream carrier partners to block malicious voice traffic coming into our network. Following on from this, our internal senior technical service team has been working closely with the Senior Complex Investigations Team at our upstream carriers to proactively monitor traffic. We expect the situation to be contained.
- identified Dec 15, 2022, 05:50 PM UTC
We expect the situation to be contained.
- identified Dec 21, 2022, 09:07 PM UTC
We are continuing to work on a fix for this issue.
- resolved Dec 21, 2022, 09:07 PM UTC
This incident has been resolved.