Sentinel Cloud
Timeline · 2 updates
- investigating Jan 24, 2026, 08:16 AM UTC
We are currently investigating this issue.
- resolved Jan 24, 2026, 09:24 AM UTC
This incident has been resolved.
Sentinel had 15 outages in the last 2 years totaling 174h 34m of downtime — averaging 0.6 incidents per month.
There were 15 Sentinel outages since July 9, 2025 totaling 174h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
This incident has been resolved.
A fault has been identified with electrical works that have taken Salisbury road that has caused a power cut at our office. This has reduced the service we can provide. We apologies for any delays that occur because of this. We are still operational but with reduced service.
Power has been restored to our office. Operation will resume as normal.
The issue has been identified and a fix is being implemented.
Power has been restored.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
An issue has been identified with degraded performance on the Callswitch dashboard and issues with inbound and outbound calls. This is being investigated currently.
Call traffic has been rerouted and are monitoring the results of this.
A fix has been implemented and we are monitoring the results.
Incident has been confirmed resolved.
**Incident Analysis** Following our initial report regarding the incident on January 12, 2026, our Engineering team implemented several emergency infrastructure upgrades. These improvements successfully mitigated the original risk and provided the enhanced visibility required to monitor this segment of our network more closely. On the afternoon of January 14, 2026, the same Memory Cache Layer within a single zone experienced a secondary disruption. This resulted in a 40-minute service outage affecting handsets, mobile applications, and in-call media, for accounts in that zone. Thanks to the telemetry tools installed earlier this week, our team was able to rapidly isolate a specific software bug within this layer. This bug was triggered by recent increases in network traffic. We have since successfully replicated, retested, and deployed a permanent fix across all zones. We will continue to monitor the network closely to ensure continued stabilit
We are currently investigating an issue of reported issues with the Callswitch dashboard and inbound & outbound calls not functioning.
A fix has been implemented and we are beginning to see traffic return to normal and services resuming across the board. We will update again within 15 minutes.
We are continuing to monitor for any further issues.
There is still some reported intermitance with the dashboard and some reports of calls not working but services are restoring, we are continuing to monitor the issue.
This issue is now resolved and all services are now operational. Do let us know if there are any further VoiP issues.
We are currently having licensing communication issues with the Windows servers that is either presenting a warning message that the user will be disconnected after 60 minutes. Some users will not be able to sign in at all. We are investigating the licensing services. Users having the 60 minute disconnect warning should be able to sign in after being disconnecting.
We have identified the a fault which we ran a repair. We have not been able to replicate the error and are now monitoring the issue to be sure licensing is working correctly across all servers.
This issue has been confirmed resolved. If there are any further service issues please get in contact with our support.
We are aware of an issue with the VoIP and are not hearing inbound/outbound calling. We are in contact with the 3rd party to resolve this promptly.
Our supplier has identified the issue and is looking to implement the fix. We will continue to monitor and update through tickets raised through support.
Some customers may experience delays on calls while we clear a backlog of SIP messages.
Some services have been restored and are slowly returning to normal service. We are continuing the status of the phones.
The issue has been resolved, and service is back to normal.
We are currently investigating an issue with VoiP services experiencing degraded performance that is effecting external and internal calling.
This issue has been reported to also affect softphone applications. The issue is still ongoing investigation.
A fault has been identified which is currently being repaired. Services are slowly restoring and service should now be restoring itself.
The ongoing fault is still causing disruption across dashboards, apps, handsets and calls. Efforts to resolve the issue are still ongoing.
We are seeing services return to normal, including dashboard access and calls. Services such as chat and soft phone applications are being restored incrementally, and we expect all services to resume normal operation within the next 20 minutes. Some backend services, such as CRM integrations and voicemail notifications, will be restored later this evening
Update - Services have been restored to handsets, mobile and desktop applications, and we're working on isolated cases of issues with dashboard access.
Dashboard access is also fully operational, and we will continue to monitor this incident for a prolonged period before marking it as resolved.
This issue has been confirmed resolved and all services are now restored. We are awaiting an RFO to provide regarding this outage.
Good Morning, A Global outage which has caused issues with Amazon Web Services (AWS) and its customers, our suppliers, is believed to be resolved, services such as web hosting, DNS, Anti-Virus, connectivity... The outage has caused problems with logging into Windows Devices as well as delays in Windows update services. We believe that the issue has now been resolved, if your still experiencing a problem please restart your machine and then login again, failing that please contact us. Kind regards, Sentinel Support
We are continuing to monitor for any further issues.
We understand that the AWS outage has now been resolved. We can see all service are up and running, we are however aware of some services running slowly as they clear the backlog. For further information please follow the BBC news feed https://www.bbc.co.uk/news/live/c5y8k7k6v1rt
Issues with making outbound calls have been found and are currently under investigation.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
The fault has been identifed and services now are beggining to be restored. This will be monitored until we can confirm the issue is resolved.
All VoiP services should now be restored.
We are aware of an issue with Callswitch and Outbound calls. It's with our Third Party Provider and currently investigating the issue. We will keep you updated on the progress
We are continuing to investigate this issue.
Our supplier has identified the issue and is looking to implement the fix asap
Third Party - We are still working on this issue and have seen calls returning to normal in some cases. We are working on reports of issues with chat via our softphone applications.
We have seen all services return to normal and are actively monitoring the issue.
We are continuing to monitor the situation, but it looks like it has been resolved. If you are still affected, then we would suggest rebooting the app/PC, signing out and back in, while checking the headset connection.
Everything now is resolved
We are currently investigating an global phone issue with calls being silent inbound, outbound and internal calls. This will effect desk and softphones.
Phone traffic is being rerouted and calls should shortly be operational.
Most phone services should now be restored. The situation is being monitored for any continued faults.
Further identified issues have been reported, this is being investigated further.
A fix has been implemented and we are monitoring the situation.
This incident has been confirmed to be resolved and services should now fully resume.