Sentinel Outage History

Sentinel is up right now

Pingoru has recorded 50 incidents for Sentinel: 13 in the last 12 months and 1 in the last 90 days.

Source: status.sentinel-data.co.uk

50incidents recorded
13last 12 months
1last 90 days
25 hourstypical duration
Incidents per month
012MayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%MayJunJulAugSepOct0%
Pingoru began tracking Sentinel in May 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
May 202600 of 744 (0%)
June 20262264 of 720 (37%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202614 of 720 (1%)
October 202600 of 514 (0%)

Incidents, newest first

Minor September 11, 2026 Issues with Inbound & Outbound calls 4h 17m Telephone System, Sentinel Voice

Started Sep 11, 2026, 02:34 PM UTC· resolved Sep 11, 2026, 06:51 PM UTC

  1. identified Sep 11, 2026, 02:34 PM UTC

    Reports are coming in regarding degraded or non-functional inbound and outbound calls. This appears to be a part of an upstream outage and we are currently investigating the issue with our partners. The cause has been identified and patches are being rolled out.

  2. monitoring Sep 11, 2026, 03:53 PM UTC

    Update - We have seen all traffic return to normal and are monitoring all services.

  3. resolved Sep 11, 2026, 06:51 PM UTC

    The VoIP systems are back up and operational following monitoring - this incident has been resolved.

Read the full incident report →

Minor June 24, 2026 Phone issues 16h 12m Telephone System, Sentinel Voice

Started Jun 24, 2026, 03:47 PM UTC· resolved Jun 25, 2026, 07:59 AM UTC

  1. identified Jun 24, 2026, 03:47 PM UTC

    A fix has been implemented and we're seeing services returning to normal. Next update 10 minutes.

  2. monitoring Jun 24, 2026, 03:49 PM UTC

    All services are now running as expected and we are monitoring the results.

  3. monitoring Jun 24, 2026, 03:55 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jun 25, 2026, 07:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 7, 2026 Sentinel Cloud- Hosted Services 10d 7h Sentinel Cloud

Started Jun 07, 2026, 09:14 AM UTC· resolved Jun 17, 2026, 04:59 PM UTC

  1. identified Jun 07, 2026, 09:14 AM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Jun 07, 2026, 06:33 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Jun 07, 2026, 06:33 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Jun 08, 2026, 12:45 PM UTC

    The intermittent connectivity observed over the weekend, 06/06/26 – 07/06/26 which caused some loss of connectivity to the Sentinel Cloud has been confirmed to be a Distributed Denial of Service (DDoS) attack. Fortunately, our Out of Hours team identified the problem quickly and managed to stop the attack. The external attack has come from a foreign nation whose intent is believed to disrupt UK business operations. Our Secure Internet Firewalls managed to fend off the threat until it was understood and suppressed. We’ll continue to monitor environment and provide further updates if necessary. This forms a stern reminder that security must be a priority and not a ‘nice-to-have’. Sentinel maintains our Cyber Essentials Plus certification which ensures that we’re ahead of potential threats. Please speak to your account manager or the Sentinel Support desk for further information.

  5. resolved Jun 17, 2026, 04:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 24, 2026 Sentinel Cloud 1h 7m Sentinel Cloud

Started Jan 24, 2026, 08:16 AM UTC· resolved Jan 24, 2026, 09:24 AM UTC

  1. investigating Jan 24, 2026, 08:16 AM UTC

    We are currently investigating this issue.

  2. resolved Jan 24, 2026, 09:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 22, 2026 Powercut 34m

Started Jan 22, 2026, 03:10 PM UTC· resolved Jan 22, 2026, 03:44 PM UTC

  1. identified Jan 22, 2026, 03:10 PM UTC

    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.

  2. resolved Jan 22, 2026, 03:44 PM UTC

    Power has been restored to our office. Operation will resume as normal.

Read the full incident report →

Notice January 22, 2026 Primary Data Centre Power supply Outage 37m Telephone System, E-mail, UniFi Cloud Controller, Sentinel Cloud and 4 more

Started Jan 22, 2026, 03:07 PM UTC· resolved Jan 22, 2026, 03:45 PM UTC

  1. identified Jan 22, 2026, 03:07 PM UTC

    The issue has been identified and a fix is being implemented.

  2. resolved Jan 22, 2026, 03:45 PM UTC

    Power has been restored.

Read the full incident report →

Notice January 22, 2026 Outage- Go Cardless 1m Direct Debit Payments

Started Jan 22, 2026, 09:26 AM UTC· resolved Jan 22, 2026, 09:27 AM UTC

  1. investigating Jan 22, 2026, 09:26 AM UTC

    We are currently investigating this issue.

  2. investigating Jan 22, 2026, 09:27 AM UTC

    We are continuing to investigate this issue.

  3. resolved Jan 22, 2026, 09:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 14, 2026 Post-dial delay and audio issues on softphones and handsets 17h 5m Telephone System

Started Jan 14, 2026, 04:08 PM UTC· resolved Jan 15, 2026, 09:14 AM UTC

  1. identified Jan 14, 2026, 04:08 PM UTC

    We are investigating an issue with mobile, desktop applications and handsets being unresponsive.

  2. identified Jan 14, 2026, 04:08 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Jan 14, 2026, 04:20 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jan 15, 2026, 09:14 AM UTC

    This incident has been resolved.

  5. postmortem Jan 22, 2026, 12:02 PM UTC

    **Incident Analysis:** At around 11:15am UTC on 12th January, performance of the Memory Cache layer on one of our zones began to degrade, and eventually caused the above services to drop. Dashboard and softphone applications would also have been impacted, as parts of these also pull information such as user availability. As we began to reroute traffic for affected customers into healthy zones, we saw the same issue present itself on a second zone, leaving one healthy zone without any interruption to service. To mitigate the impact, we implemented a forced-flush of the system at around 13:00pm UTC, and managed to restore service to one zone shortly afterward. The second affected zone did not recover with the same method. Our infrastructure team then rolled out a planned upgrade to our SIP proxies to that affected zone, at around 13:30pm, which dramatically reduced the load and allowed all services to resume on the final zones within minutes. We took the decision to wait to implement this same upgrade across the other two healthy zones out of hours, however we unfortunately saw the same issue occur later in the day which caused us to roll this out early to a second zone, at around 15:55pm UTC. The fix was implemented and service restored within 10 minutes of the first report in this instance. Later that evening, we successfully rolled out the upgrade to the remaining zone. Unfortunately, as a result of these upgrades, this caused the BLF indicators on some handsets to become stuck. The following day, on the 13th January at 12:47pm, our team implemented a flush of all active BLF connections, which caused an unforeseen, temporary interruption to those accounts. Service resumed automatically for all handsets at around 12:57pm. **Conclusion and Next Steps** After reviewing the data surrounding this incident, we are confident that the catalyst for the initial degradation on the affected zones is related to the ever-increasing load on the platform. While we have made significant progress in many areas since beginning this overhaul in July 2025, we recognise that there is still some way to go before it can be considered fully complete. At the time of writing, all zones now have the relevant upgrade applied, which gives us a permanent solution to this issue: we have now fully retired the legacy module that caused yesterday’s issues. In addition to this upgrade to our Memory Cache layer, we are in the final stages of QA for an additional major project that involves the complete re-design of our presence infrastructure, again dramatically reducing the load and enabling far greater scalability in future.

Read the full incident report →

Minor January 13, 2026 CallSwitch degraded performance on inbound and outbound calling 3h 13m Telephone System

Started Jan 13, 2026, 12:53 PM UTC· resolved Jan 13, 2026, 04:06 PM UTC

  1. investigating Jan 13, 2026, 12:53 PM UTC

    An issue has been identified with degraded performance on the Callswitch dashboard and issues with inbound and outbound calls. This is being investigated currently.

  2. identified Jan 13, 2026, 01:00 PM UTC

    Call traffic has been rerouted and are monitoring the results of this.

  3. monitoring Jan 13, 2026, 01:02 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jan 13, 2026, 04:06 PM UTC

    Incident has been confirmed resolved.

  5. postmortem Jan 22, 2026, 10:33 AM UTC

    **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

Read the full incident report →

Major January 12, 2026 VoiP service load issue 21h 33m Telephone System

Started Jan 12, 2026, 11:44 AM UTC· resolved Jan 13, 2026, 09:18 AM UTC

  1. investigating Jan 12, 2026, 11:44 AM UTC

    We are currently investigating an issue of reported issues with the Callswitch dashboard and inbound & outbound calls not functioning.

  2. monitoring Jan 12, 2026, 11:52 AM UTC

    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.

  3. monitoring Jan 12, 2026, 11:52 AM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Jan 12, 2026, 12:10 PM UTC

    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.

  5. resolved Jan 13, 2026, 09:18 AM UTC

    This issue is now resolved and all services are now operational. Do let us know if there are any further VoiP issues.

Read the full incident report →

Major December 17, 2025 Server connection 60 minute error message 5h 38m Sentinel Cloud

Started Dec 17, 2025, 09:59 AM UTC· resolved Dec 17, 2025, 03:37 PM UTC

  1. investigating Dec 17, 2025, 09:59 AM UTC

    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.

  2. monitoring Dec 17, 2025, 02:16 PM UTC

    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.

  3. resolved Dec 17, 2025, 03:37 PM UTC

    This issue has been confirmed resolved. If there are any further service issues please get in contact with our support.

Read the full incident report →

Notice November 17, 2025 Viop Issue 3h Telephone System

Started Nov 17, 2025, 10:42 AM UTC· resolved Nov 17, 2025, 01:43 PM UTC

  1. investigating Nov 17, 2025, 10:42 AM UTC

    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.

  2. identified Nov 17, 2025, 10:59 AM UTC

    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.

  3. identified Nov 17, 2025, 11:16 AM UTC

    Some customers may experience delays on calls while we clear a backlog of SIP messages.

  4. monitoring Nov 17, 2025, 11:39 AM UTC

    Some services have been restored and are slowly returning to normal service. We are continuing the status of the phones.

  5. resolved Nov 17, 2025, 01:43 PM UTC

    The issue has been resolved, and service is back to normal.

Read the full incident report →

Minor October 21, 2025 VoiP service issue 23h 15m Telephone System

Started Oct 21, 2025, 10:36 AM UTC· resolved Oct 22, 2025, 09:51 AM UTC

  1. investigating Oct 21, 2025, 10:36 AM UTC

    We are currently investigating an issue with VoiP services experiencing degraded performance that is effecting external and internal calling.

  2. investigating Oct 21, 2025, 11:04 AM UTC

    This issue has been reported to also affect softphone applications. The issue is still ongoing investigation.

  3. identified Oct 21, 2025, 11:40 AM UTC

    A fault has been identified which is currently being repaired. Services are slowly restoring and service should now be restoring itself.

  4. identified Oct 21, 2025, 12:20 PM UTC

    The ongoing fault is still causing disruption across dashboards, apps, handsets and calls. Efforts to resolve the issue are still ongoing.

  5. identified Oct 21, 2025, 02:10 PM UTC

    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

  6. monitoring Oct 22, 2025, 06:29 AM UTC

    Update - Services have been restored to handsets, mobile and desktop applications, and we're working on isolated cases of issues with dashboard access.

  7. monitoring Oct 22, 2025, 06:30 AM UTC

    Dashboard access is also fully operational, and we will continue to monitor this incident for a prolonged period before marking it as resolved.

  8. resolved Oct 22, 2025, 09:51 AM UTC

    This issue has been confirmed resolved and all services are now restored. We are awaiting an RFO to provide regarding this outage.

Read the full incident report →

Minor October 20, 2025 Device Login issues 3h 33m Telephone System, E-mail, Sentinel Data Solutions Website, Sentinel Cloud and 3 more

Started Oct 20, 2025, 10:12 AM UTC· resolved Oct 20, 2025, 01:46 PM UTC

  1. monitoring Oct 20, 2025, 10:12 AM UTC

    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

  2. monitoring Oct 20, 2025, 10:21 AM UTC

    We are continuing to monitor for any further issues.

  3. resolved Oct 20, 2025, 01:46 PM UTC

    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

Read the full incident report →

Minor July 30, 2025 VoiP Outbound calling & load faults 1h 52m Telephone System

Started Jul 30, 2025, 09:58 AM UTC· resolved Jul 30, 2025, 11:51 AM UTC

  1. investigating Jul 30, 2025, 09:58 AM UTC

    Issues with making outbound calls have been found and are currently under investigation.

  2. investigating Jul 30, 2025, 09:59 AM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 30, 2025, 10:01 AM UTC

    We are continuing to investigate this issue.

  4. monitoring Jul 30, 2025, 10:23 AM UTC

    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.

  5. resolved Jul 30, 2025, 11:51 AM UTC

    All VoiP services should now be restored.

Read the full incident report →

Notice July 11, 2025 Callswitch Outbound Calling 2d 19h Telephone System, Sentinel Voice

Started Jul 11, 2025, 11:11 AM UTC· resolved Jul 14, 2025, 07:10 AM UTC

  1. investigating Jul 11, 2025, 11:11 AM UTC

    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

  2. investigating Jul 11, 2025, 11:12 AM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 11, 2025, 11:24 AM UTC

    Our supplier has identified the issue and is looking to implement the fix asap

  4. identified Jul 11, 2025, 11:33 AM UTC

    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.

  5. monitoring Jul 11, 2025, 11:43 AM UTC

    We have seen all services return to normal and are actively monitoring the issue.

  6. monitoring Jul 11, 2025, 02:43 PM UTC

    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.

  7. resolved Jul 14, 2025, 07:10 AM UTC

    Everything now is resolved

Read the full incident report →

Major July 9, 2025 Global Inbound and Outbound Phone issues 22h 32m Telephone System

Started Jul 09, 2025, 10:36 AM UTC· resolved Jul 10, 2025, 09:08 AM UTC

  1. investigating Jul 09, 2025, 10:36 AM UTC

    We are currently investigating an global phone issue with calls being silent inbound, outbound and internal calls. This will effect desk and softphones.

  2. identified Jul 09, 2025, 10:44 AM UTC

    Phone traffic is being rerouted and calls should shortly be operational.

  3. monitoring Jul 09, 2025, 10:55 AM UTC

    Most phone services should now be restored. The situation is being monitored for any continued faults.

  4. identified Jul 09, 2025, 11:51 AM UTC

    Further identified issues have been reported, this is being investigated further.

  5. monitoring Jul 09, 2025, 08:00 PM UTC

    A fix has been implemented and we are monitoring the situation.

  6. resolved Jul 10, 2025, 09:08 AM UTC

    This incident has been confirmed to be resolved and services should now fully resume.

Read the full incident report →

Notice May 7, 2025 Website performance 17h 49m

Started May 07, 2025, 02:13 PM UTC· resolved May 08, 2025, 08:03 AM UTC

  1. identified May 07, 2025, 02:13 PM UTC

    We are aware of problems with website performance and are investigating. The latency issues have been escallated with our upstream provider. Further updates will be made when availabile.

  2. resolved May 08, 2025, 08:03 AM UTC

    There was a problem with our upstream provider. The issue has been resolved. We are reviewing our infrastructure to ensure that this doesn’t happen again.

Read the full incident report →

Notice March 25, 2025 Compromised email 6d 2h

Started Mar 25, 2025, 11:48 AM UTC· resolved Mar 31, 2025, 02:30 PM UTC

  1. identified Mar 25, 2025, 11:48 AM UTC

    We understand that an email has gone out from Matthew with a PDF. Please ignore and delete this email and if you have opened can you get in contact with support.

  2. monitoring Mar 25, 2025, 04:31 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 31, 2025, 02:30 PM UTC

    The offending email has been blocked from all Microsoft tenants and deleted from Outlook.

Read the full incident report →

Minor March 11, 2025 Telephony intermittent outage 1h 46m Telephone System

Started Mar 11, 2025, 10:19 AM UTC· resolved Mar 11, 2025, 12:06 PM UTC

  1. investigating Mar 11, 2025, 10:19 AM UTC

    We're aware of an issue with our upstream provider whereby a caller will continue to hear the telephone ring even when the call has been answered. The recipient of the call can only hear silience. We've raised this with our upstream provider who are investigation. Further updates to follow..

  2. monitoring Mar 11, 2025, 11:29 AM UTC

    Traffic has been returning to normal levels in most areas of our network. We'll continue to monitor and provide further updates within one hour.

  3. resolved Mar 11, 2025, 12:06 PM UTC

    The telephony issue has now been resolved. We'll continue to monitor the service with our upstream provider over the next 24 hours. Sorry for the inconvenience that this may have caused.

Read the full incident report →

Notice January 17, 2025 Microsoft Office Outage 3h 28m Telephone System, E-mail

Started Jan 17, 2025, 08:22 AM UTC· resolved Jan 17, 2025, 11:51 AM UTC

  1. investigating Jan 17, 2025, 08:22 AM UTC

    Good morning, we are aware of an issue with Microsoft Office. We're currently working with Microsoft to find a resolution. Further updates to follow.

  2. investigating Jan 17, 2025, 09:45 AM UTC

    Microsoft have provided a resolution. We're working on deploying the fix.. We'll be in contact shortly..

  3. investigating Jan 17, 2025, 11:43 AM UTC

    We are continuing to investigate this issue.

  4. resolved Jan 17, 2025, 11:51 AM UTC

    The problems with Microsoft Office have been resolved. If your experiencing any further issues, please call 01425 527014

Read the full incident report →

Minor November 22, 2024 CallSwitch Call Dropouts 3h 33m Telephone System, Sentinel Voice

Started Nov 22, 2024, 12:46 PM UTC· resolved Nov 22, 2024, 04:19 PM UTC

  1. investigating Nov 22, 2024, 12:46 PM UTC

    We have had some reports of blank calls and calls dropping out. We are currently investigating this with our upstream providers and will update as soon as possible.

  2. resolved Nov 22, 2024, 04:19 PM UTC

    The issue seemed to affect our internal telephone system primarily. We haven't had any further reports of issues and our calls have returned to normal.

Read the full incident report →