Sentinel Outage History

Sentinel is up right now

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.

Source: https://status.sentinel-data.co.uk/

Major January 24, 2026

Sentinel Cloud

Detected by Pingoru
Jan 24, 2026, 08:16 AM UTC
Resolved
Jan 24, 2026, 09:24 AM UTC
Duration
1h 7m
Affected: Sentinel Cloud
Timeline · 2 updates
  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

Detected by Pingoru
Jan 22, 2026, 03:10 PM UTC
Resolved
Jan 22, 2026, 03:44 PM UTC
Duration
34m
Timeline · 2 updates
  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

Detected by Pingoru
Jan 22, 2026, 03:07 PM UTC
Resolved
Jan 22, 2026, 03:45 PM UTC
Duration
37m
Affected: Telephone SystemE-mailUniFi Cloud ControllerSentinel CloudSentinel VoiceVigor ACS 3Automate RMM MonitoringUISP Management System
Timeline · 2 updates
  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

Detected by Pingoru
Jan 22, 2026, 09:26 AM UTC
Resolved
Jan 22, 2026, 09:27 AM UTC
Duration
1m
Affected: Direct Debit Payments
Timeline · 3 updates
  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 →

Notice January 19, 2026

Sentinel Cloud- Hosted Services

Detected by Pingoru
Jan 19, 2026, 07:16 AM UTC
Resolved
Jan 19, 2026, 09:45 AM UTC
Duration
2h 28m
Affected: Sentinel Cloud
Timeline · 5 updates
  1. investigating Jan 19, 2026, 07:16 AM UTC

    We are currently investigating this issue.

  2. investigating Jan 19, 2026, 07:16 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jan 19, 2026, 08:08 AM UTC

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

  4. monitoring Jan 19, 2026, 08:08 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jan 19, 2026, 09:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 13, 2026

CallSwitch degraded performance on inbound and outbound calling

Detected by Pingoru
Jan 13, 2026, 12:53 PM UTC
Resolved
Jan 13, 2026, 04:06 PM UTC
Duration
3h 13m
Affected: Telephone System
Timeline · 5 updates
  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

Detected by Pingoru
Jan 12, 2026, 11:44 AM UTC
Resolved
Jan 13, 2026, 09:18 AM UTC
Duration
21h 33m
Affected: Telephone System
Timeline · 5 updates
  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

Detected by Pingoru
Dec 17, 2025, 09:59 AM UTC
Resolved
Dec 17, 2025, 03:37 PM UTC
Duration
5h 38m
Affected: Sentinel Cloud
Timeline · 3 updates
  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

Detected by Pingoru
Nov 17, 2025, 10:42 AM UTC
Resolved
Nov 17, 2025, 01:43 PM UTC
Duration
3h
Affected: Telephone System
Timeline · 5 updates
  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

Detected by Pingoru
Oct 21, 2025, 10:36 AM UTC
Resolved
Oct 22, 2025, 09:51 AM UTC
Duration
23h 15m
Affected: Telephone System
Timeline · 8 updates
  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

Detected by Pingoru
Oct 20, 2025, 10:12 AM UTC
Resolved
Oct 20, 2025, 01:46 PM UTC
Duration
3h 33m
Affected: Telephone SystemE-mailSentinel Data Solutions WebsiteSentinel CloudDirect Debit PaymentsSentinel VoiceCloudflare Manchester, United Kingdom - (MAN)
Timeline · 3 updates
  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

Detected by Pingoru
Jul 30, 2025, 09:58 AM UTC
Resolved
Jul 30, 2025, 11:51 AM UTC
Duration
1h 52m
Affected: Telephone System
Timeline · 5 updates
  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

Detected by Pingoru
Jul 11, 2025, 11:11 AM UTC
Resolved
Jul 14, 2025, 07:10 AM UTC
Duration
2d 19h
Affected: Telephone SystemSentinel Voice
Timeline · 7 updates
  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

Detected by Pingoru
Jul 09, 2025, 10:36 AM UTC
Resolved
Jul 10, 2025, 09:08 AM UTC
Duration
22h 32m
Affected: Telephone System
Timeline · 6 updates
  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 →