- Detected by Pingoru
- Oct 14, 2026, 09:09 AM UTC
- Resolved
- Oct 16, 2026, 09:07 AM UTC
- Duration
- 1d 23h
Affected: CloudCover365 Services
Timeline · 4 updates
-
investigating Oct 14, 2026, 09:09 AM UTC
We are currently investigating an issue affecting CloudCover365 SharePoint, OneDrive and Teams backups, where backup jobs are failing with an "Unknown Error" message. Initial investigations suggest the issue may be related to a recent change made by Microsoft. Our engineering team is actively investigating the issue and monitoring developments. We will provide further updates as more information becomes available.
-
investigating Oct 14, 2026, 01:28 PM UTC
We have confirmed that the issue affecting SharePoint, OneDrive and Teams backups, resulting in failures with an "Unknown Error" message, is related to a Microsoft service degradation. Microsoft has acknowledged the issue under Service Health incident SP1503038. We are continuing to monitor the situation and will provide further updates as they become available.
-
monitoring Oct 15, 2026, 02:43 PM UTC
Microsoft has now marked service incident SP1503038 as resolved. We have observed a steady decrease in backup failure rates across affected SharePoint and OneDrive backups, with the majority of affected customers now recovering. We will continue to monitor the service to ensure backup operations return to normal before marking this incident as fully resolved.
-
resolved Oct 16, 2026, 09:07 AM UTC
We have observed a significant reduction in backup error rates following the resolution of Microsoft's service incident SP1503038. Backup operations have now returned to normal, and the issue affecting SharePoint, OneDrive and Teams backup is considered resolved. We will continue to monitor backup operations to ensure service stability.
Read the full incident report →
- Detected by Pingoru
- Sep 14, 2026, 03:54 PM UTC
- Resolved
- Sep 16, 2026, 02:41 PM UTC
- Duration
- 1d 22h
Affected: Hosting Platform
Timeline · 3 updates
-
investigating Sep 14, 2026, 03:54 PM UTC
We are aware of an issue affecting internet connectivity, caused by a routing issue at our internet transit provider's upstream Tier 1 supplier. We are in direct contact with our provider, who are engaging with theirs to investigate and restore service. Customers may experience intermittent or complete loss of internet connectivity to affected services while this is ongoing. We are monitoring the situation closely and will provide further updates as they become available. We apologise for any inconvenience this may cause.
-
monitoring Sep 14, 2026, 04:56 PM UTC
Since our previous update, connectivity has continued to stabilise and a number of affected customer services have now been restored. Our team is continuing to review the remaining incidents and closely monitor the platform to ensure services remain stable. We will continue to monitor the situation and provide further updates as they become available.
-
resolved Sep 16, 2026, 02:41 PM UTC
Following the previous update, we have continued to closely monitor connectivity and service performance over the past 48 hours. Services have remained stable throughout this monitoring period, and we are satisfied that the issue has now been resolved. We will continue to monitor the platform as part of our normal operational processes.
Read the full incident report →
- Detected by Pingoru
- Aug 14, 2026, 08:05 AM UTC
- Resolved
- Aug 14, 2026, 12:14 PM UTC
- Duration
- 4h 8m
Affected: Veeam Cloud Connect Replication Service
Timeline · 3 updates
-
investigating Aug 14, 2026, 08:05 AM UTC
We are aware of issues affecting some customers' Hyper-V replication. We are working to mitigate this problem and will provide updates as our investigations progress.
-
monitoring Aug 14, 2026, 09:07 AM UTC
Engineers have identified the issue and implemented a fix which we believe should resolve the problems experienced. Test jobs are now running and completing successfully. We will continue to closely monitor the platform to ensure customer jobs continue to complete successfully. We will provide a further update once we are satisfied that the platform is operating as expected.
-
resolved Aug 14, 2026, 12:14 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 01:24 PM UTC
- Resolved
- Jul 23, 2026, 01:41 PM UTC
- Duration
- 16m
Affected: CloudCover365 Portal
Timeline · 2 updates
-
investigating Jul 23, 2026, 01:24 PM UTC
We are aware of authentication issues affecting the web portal of CloudCover365. We are investigating this as a matter or urgency. At current this is only affecting the web portal access. Jobs are unaffected and will continue to run.
-
resolved Jul 23, 2026, 01:41 PM UTC
The issue has been identified and resolved now. Authentication is working as expected now.
Read the full incident report →
- Detected by Pingoru
- Jun 19, 2026, 08:21 AM UTC
- Resolved
- Jun 25, 2026, 10:47 AM UTC
- Duration
- 6d 2h
Affected: Veeam Cloud Connect Backup Service
Timeline · 5 updates
-
investigating Jun 19, 2026, 08:21 AM UTC
We are aware of an issue affecting some customers' veeam cloud connect backup jobs this morning. We are actively looking into this and will update once progress is made.
-
identified Jun 19, 2026, 11:02 AM UTC
Our investigation is ongoing and, working alongside the vendor, we believe we have identified the underlying cause of the issue affecting some Veeam Cloud Connect backup jobs. We are currently validating a potential fix within our lab environment and will provide a further update once testing has been completed. Further updates to follow at 14:00
-
identified Jun 19, 2026, 02:22 PM UTC
To minimise disruption while we continue our investigation, affected tenants are being temporarily disabled. During this time, Veeam Cloud Connect backup jobs for affected tenants may fail with the message "Your tenant is disabled". This behaviour is expected and forms part of our mitigation efforts while a permanent resolution is being implemented. We believe we have identified the underlying cause of the issue and are currently validating a potential fix within our lab environment. Testing remains ongoing, and we will provide a further update as soon as validation has been completed.
-
monitoring Jun 19, 2026, 06:39 PM UTC
The fix has now been deployed and successfully validated. Test backup jobs have completed successfully, and affected tenants have been re-enabled. We are continuing to closely monitor the platform to ensure services remain stable and that backup jobs are processing as expected. We will provide a further update should there be any significant developments.
-
resolved Jun 25, 2026, 10:47 AM UTC
We have been monitoring the platform since, and it has been stable and performing as usual. Please reach out to out support team at [email protected] if you have any further issues still ongoing.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 08:51 AM UTC
- Resolved
- May 19, 2026, 03:17 PM UTC
- Duration
- 6h 25m
Affected: Veeam Cloud Connect Backup Service
Timeline · 4 updates
-
investigating May 19, 2026, 08:51 AM UTC
We are aware that some customer jobs pointed towards our VCC platform are failing unexpectedly, Our Team are aware and are currently investigating this issue as a priority.
-
identified May 19, 2026, 09:00 AM UTC
We believe we have determined the possible root cause for these issues and are currently deploying a fix to resolve these errors.
-
monitoring May 19, 2026, 09:35 AM UTC
The fix has now been implemented and we are currently monitoring job pass rates. Affected jobs should retry automatically.
-
resolved May 19, 2026, 03:17 PM UTC
This root cause was a Scale-Out Backup Repository (SOBR) volume on the DCS Veeam Cloud Connect platform reaching full capacity. We have identified a limitation in existing platform monitors which use aggregated monitoring as opposed to individual volumes. This meant an alert was not raised proactively as expected; we are implementing additional monitors to aim at preventing a re-occurrence.
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 12:44 PM UTC
- Resolved
- May 22, 2026, 01:15 PM UTC
- Duration
- 10d
Affected: CloudCover365 PortalCloudCover365 Services
Timeline · 4 updates
-
investigating May 12, 2026, 12:44 PM UTC
We are aware of an issue affecting some restores at the point where you select what items to restore being met with an error message 'Please try again. If the issue persists, contact support'. This seems to have occurred from our latest patch. Our developers are currently looking into this. If you require a restore don't hesitate to reach out to the CloudCover365 team via Live Chat or email and we can manually run this for you.
-
identified May 13, 2026, 03:42 PM UTC
Our developers have written a fix for this which is currently being tested in our lab environment. This will be updated once we have pushed this fix publicly and confirmed working. If you require a restore in the meantime, don't hesitate to reach out to the CloudCover365 team via Live Chat or email and we can manually run this for you.
-
monitoring May 14, 2026, 04:47 PM UTC
A fix has been implemented as part of the latest V26.5 release and we are now monitoring the results.
-
resolved May 22, 2026, 01:15 PM UTC
This is resolved now by our development team. Please contact us via email or live chat if you continue to have any issues.
Read the full incident report →
- Detected by Pingoru
- Mar 27, 2026, 04:29 PM UTC
- Resolved
- Jun 25, 2026, 03:26 PM UTC
- Duration
- 89d 22h
Affected: CloudCover365 Services
Timeline · 11 updates
Read the full incident report →
- Detected by Pingoru
- Mar 23, 2026, 10:29 AM UTC
- Resolved
- Mar 24, 2026, 02:07 PM UTC
- Duration
- 1d 3h
Affected: CloudCover365 PortalCloudCover365 ServicesHosting PlatformVeeam Cloud Connect Backup ServiceVeeam Cloud Connect Replication ServiceObject Storage LeedsObject Storage SloughGeo-Failover ReplicationVeeam Service Provider Console
Timeline · 7 updates
-
investigating Mar 23, 2026, 10:29 AM UTC
We are currently experiencing outage issues across multiple sites. Our engineers are currently looking into this as a P1 issue.
-
investigating Mar 23, 2026, 10:54 AM UTC
Our engineers are continuing to look into this
-
identified Mar 23, 2026, 11:05 AM UTC
We have identified an issue with an upstream network connection. This is not isolated to DCS and is part of a wider problem affecting multiple partners. Our upstream provider is working to stabilise the connection as a priority. We will continue to post updates as soon as more information becomes available.
-
monitoring Mar 23, 2026, 11:27 AM UTC
Our partner appears to have stabilised the connectivity for now. Services should now be back to normal. They are still investigating the root cause and we will update once we hear back from them.
-
monitoring Mar 23, 2026, 11:58 AM UTC
All services look to be operational again, we're still monitoring this and confirming root cause with our provider
-
monitoring Mar 23, 2026, 04:55 PM UTC
This incident has been linked to a fault with one of our provider's upstream network partners, who has acknowledged the issue. As this provider carries a significant volume of internet traffic, impact was widespread, though variable depending on routing paths. Services have remained stable since 11am. We are continuing to monitor.
-
resolved Mar 24, 2026, 11:40 AM UTC
We have been monitoring the platform closely with our service partner, and the network has remained stable since 11:00 on 23/03. As stability has been confirmed, we are now closing this incident. If you are still experiencing any issues, please contact [email protected].
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2026, 10:49 AM UTC
- Resolved
- Mar 17, 2026, 10:24 AM UTC
- Duration
- 18d 23h
Affected: CloudCover365 PortalCloudCover365 Services
Timeline · 5 updates
-
investigating Feb 26, 2026, 10:49 AM UTC
Some exchange restores may provide the error message "Failed to restore folder: The certificate certificate does not have a private key." when attempting to restore to original location. This is being investigated by the team.
-
investigating Feb 27, 2026, 10:39 AM UTC
The team is continuing to investigate this issue as a priority, Customers are encourage to reach out to a member of the team via email ([email protected]) or the live chat function if restores are required.
-
identified Mar 03, 2026, 10:42 AM UTC
A possible root cause has been identified and a fix will be implemented
-
identified Mar 10, 2026, 05:16 PM UTC
A fix has been created and tested and is set to be deployed on the 16th of March 2026 at 6:30AM GMT
-
resolved Mar 17, 2026, 10:24 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 10, 2026, 10:42 AM UTC
- Resolved
- Feb 11, 2026, 09:21 AM UTC
- Duration
- 22h 38m
Affected: CloudCover365 Portal
Timeline · 2 updates
-
monitoring Feb 10, 2026, 10:42 AM UTC
Our team has received reports of users experiencing issues following our most recent updates. After investigation, we identified the root cause as a caching issue. To resolve this, customers should refresh their browser’s local cache. Instructions can be found below: • Google Chrome: https://support.google.com/accounts/answer/32050 • Microsoft Edge: https://www.microsoft.com/en-us/edge/learning-center/how-to-manage-and-clear-your-cache-and-cookies • Mozilla Firefox: https://support.mozilla.org/en-US/kb/how-clear-firefox-cache
-
resolved Feb 11, 2026, 09:21 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 16, 2026, 03:17 PM UTC
- Resolved
- Jan 19, 2026, 09:54 AM UTC
- Duration
- 2d 18h
Affected: Geo-Failover Replication
Timeline · 2 updates
-
investigating Jan 16, 2026, 03:17 PM UTC
Our intersite replication is currently experiencing issues for some customers. We are actively investigating and working to resolve this.
-
resolved Jan 19, 2026, 09:54 AM UTC
This issue has been resolved by our engineers over the weekend
Read the full incident report →
- Detected by Pingoru
- Jan 15, 2026, 09:25 PM UTC
- Resolved
- Jan 15, 2026, 10:40 PM UTC
- Duration
- 1h 15m
Affected: Hosting Platform
Timeline · 2 updates
-
investigating Jan 15, 2026, 09:25 PM UTC
We're aware service interruption that is affecting part of your environment earlier currently. Please accept our apologies for any inconvenience this may have caused. Our engineers are checking the platform currently. We are continuing to investigate the cause and will share any relevant findings.
-
resolved Jan 15, 2026, 10:40 PM UTC
Services have been restored by our engineers. Please accept our apologies for any inconvenience this may have caused. This was identified as one of the underlying host systems experiencing an unexpected issue. This resulted in some hosted servers restarting automatically while the platform recovered. All affected servers are now back online and operating normally. Our engineers have checked the platform and confirmed there is no ongoing impact to your services. We are continuing to investigate the cause. If you notice anything out of the ordinary, or would like support checking application services, please let us know and we’ll be happy to assist.
Read the full incident report →
- Detected by Pingoru
- Jan 06, 2026, 02:03 PM UTC
- Resolved
- Jan 08, 2026, 10:23 AM UTC
- Duration
- 1d 20h
Affected: CloudCover365 PortalCloudCover365 ServicesVeeam Cloud Connect Backup ServiceVeeam Cloud Connect Replication Service
Timeline · 3 updates
-
investigating Jan 06, 2026, 02:03 PM UTC
Our team are aware of some reduced performance and speed with CloudCover365 and Cloud Connect. During this time restores and backup jobs may take longer than usual. Our engineers are investigating this
-
investigating Jan 08, 2026, 10:23 AM UTC
We are continuing to investigate this issue.
-
resolved Jan 08, 2026, 10:23 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 19, 2025, 04:04 PM UTC
- Resolved
- Jan 08, 2026, 10:24 AM UTC
- Duration
- 19d 18h
Affected: Geo-Failover Replication
Timeline · 2 updates
-
investigating Dec 19, 2025, 04:04 PM UTC
The underlying issue from earlier this week that impacted GEO replication has been addressed and we are actively monitoring jobs until they all come back into a stable state.
-
resolved Jan 08, 2026, 10:24 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 18, 2025, 10:20 AM UTC
- Resolved
- Dec 18, 2025, 03:49 PM UTC
- Duration
- 5h 28m
Affected: Veeam Cloud Connect Backup ServiceVeeam Cloud Connect Replication ServiceGeo-Failover Replication
Timeline · 6 updates
-
investigating Dec 18, 2025, 10:20 AM UTC
We are currently looking into intermittent issues with CloudConnect and Geo-Failover Replication. Our engineers are working to identify and resolve these issues
-
investigating Dec 18, 2025, 11:02 AM UTC
We are continuing to investigate these issues. Updates will be posted here as they are made
-
investigating Dec 18, 2025, 12:44 PM UTC
Our engineers are continuing to investigate and are working towards a solution
-
investigating Dec 18, 2025, 02:28 PM UTC
Our engineers continue to look into these issues. Progress will be posted here
-
investigating Dec 18, 2025, 03:10 PM UTC
We're continuing to investigate and are working towards a solution currently
-
resolved Dec 18, 2025, 03:49 PM UTC
These issues have been resolved by our engineers, please log any continued issues as normal with us
Read the full incident report →
- Detected by Pingoru
- Dec 17, 2025, 12:20 PM UTC
- Resolved
- Dec 17, 2025, 05:37 PM UTC
- Duration
- 5h 17m
Affected: CloudCover365 PortalCloudCover365 ServicesHosting PlatformVeeam Cloud Connect Backup ServiceVeeam Cloud Connect Replication ServiceObject Storage LeedsGeo-Failover ReplicationVeeam Service Provider Console
Timeline · 7 updates
-
investigating Dec 17, 2025, 12:20 PM UTC
We are currently investigating this issue. Further updates will be provided as they become available. Next update due at 13:18 hours.
-
investigating Dec 17, 2025, 01:42 PM UTC
General update: Further investigations are ongoing. No further updates at this time
-
investigating Dec 17, 2025, 02:13 PM UTC
We are still actively investigating this. We'll continue to update this page with progress
-
investigating Dec 17, 2025, 03:08 PM UTC
Our operations team are still looking into this as a P1 issue
-
identified Dec 17, 2025, 03:46 PM UTC
We have identified the cause of the connectivity issue impacting services and have successfully isolated it within the affected network segment. Our engineering teams are actively working on remediation actions to restore normal service as quickly and safely as possible. Services may remain intermittent during this period. Further updates will be provided as restoration progresses.
-
identified Dec 17, 2025, 04:58 PM UTC
We are still resolving this issue. Services are intermittent still
-
resolved Dec 17, 2025, 05:37 PM UTC
This issue has been resolved by our operations team, we are investigating to the root cause of the issue
Read the full incident report →
- Detected by Pingoru
- Nov 27, 2025, 12:05 PM UTC
- Resolved
- Nov 27, 2025, 03:12 PM UTC
- Duration
- 3h 6m
Affected: CloudCover365 Services
Timeline · 2 updates
-
investigating Nov 27, 2025, 12:05 PM UTC
We are currently resolving an issue which causes jobs to fail to start on schedule or manually ran.
-
resolved Nov 27, 2025, 03:12 PM UTC
This has been resolved
Read the full incident report →
- Detected by Pingoru
- Nov 25, 2025, 04:51 PM UTC
- Resolved
- Dec 01, 2025, 02:42 PM UTC
- Duration
- 5d 21h
Affected: CloudCover365 Services
Timeline · 2 updates
-
investigating Nov 25, 2025, 04:51 PM UTC
We’re aware of jobs failing with the error “The HTTP request was forbidden with client authentication scheme 'Anonymous'.” We’re investigating this with the vendor.
-
resolved Dec 01, 2025, 02:42 PM UTC
This was identified as a change by Microsoft in what licenses are required to perform CloudCover 365 backup. If you're still seeing this on any mailboxes please confirm that a supported Microsoft 365 plan that includes full Exchange Online and Graph API support is used (e.g., Microsoft 365 Business Standard, E3/E5).
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 12:05 PM UTC
- Resolved
- Nov 18, 2025, 04:00 PM UTC
- Duration
- 3h 54m
Affected: CloudCover365 PortalVeeam Service Provider Console
Timeline · 4 updates
-
monitoring Nov 18, 2025, 12:05 PM UTC
We are currently experiencing intermittent downtime due to a global network issue affecting our Cloud Delivery Network provider (Cloudflare). These errors appear to be transient, and our team is actively monitoring the situation. If the issue persists, we may implement a temporary workaround to minimise impact. We will continue to provide updates as more information becomes available. Thank you for your patience and understanding.
-
monitoring Nov 18, 2025, 12:07 PM UTC
We are continuing to monitor for any further issues.
-
monitoring Nov 18, 2025, 01:09 PM UTC
We are actively attempting to re-route traffic to mitigate the impact; however, our supplier’s service remains difficult to access, which is currently inhibiting this step. Our team continues to monitor the situation closely and will provide further updates as soon as we have more information or successfully implement a workaround. Thank you for your continued patience.
-
resolved Nov 21, 2025, 11:28 AM UTC
This issue has been resolved by our provider Cloudflare now
Read the full incident report →
- Detected by Pingoru
- Sep 03, 2025, 05:01 PM UTC
- Resolved
- Oct 02, 2025, 10:08 AM UTC
- Duration
- 28d 17h
Affected: Hosting Platform
Timeline · 4 updates
-
identified Sep 03, 2025, 05:01 PM UTC
A host has had an issue in our Derby DC and has HA'd some customer VM's to other hosts. Customers affected will be contacted directly. Apologies for any inconvenience.
-
monitoring Sep 03, 2025, 05:01 PM UTC
Hos has been quarantined until an RCA can be completed.
-
monitoring Sep 04, 2025, 05:52 PM UTC
We are continuing to monitor for any further issues.
-
resolved Oct 02, 2025, 10:08 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2025, 11:35 PM UTC
- Resolved
- Apr 22, 2025, 08:59 AM UTC
- Duration
- 6d 9h
Affected: CloudCover365 Services
Timeline · 6 updates
-
investigating Apr 15, 2025, 11:35 PM UTC
We are aware of some performance issues with some customers backup jobs, mainly affecting SharePoint and Team backup jobs. Our engineers are working with our vendors to resolve this issue as soon as possible. Thanks for your patience, updates will follow in due course.
-
investigating Apr 16, 2025, 09:24 AM UTC
We continue to work with the vendor on this issue. Further updates will be shared when we have them.
-
identified Apr 16, 2025, 03:29 PM UTC
The issue has been identified and the vendor is working on a patch to resolve the issue.
-
identified Apr 17, 2025, 04:29 PM UTC
A fix has been supplied and has been tested. We will be rolling out to production shortly.
-
monitoring Apr 17, 2025, 06:03 PM UTC
Patch has been deployed and performance looks to have returned to normal levels
-
resolved Apr 22, 2025, 08:59 AM UTC
All jobs affected by this issue are now running as expected.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2025, 03:00 PM UTC
- Resolved
- Apr 22, 2025, 08:59 AM UTC
- Duration
- 6d 17h
Affected: Geo-Failover Replication
Timeline · 4 updates
-
identified Apr 15, 2025, 03:00 PM UTC
Our intersite replication is currently experiencing issues for some customers. We are engaged with our vendor to find and implement a fix.
-
identified Apr 16, 2025, 09:23 AM UTC
We have identified the issue and an action plan is currently being implemented for the affected jobs.
-
identified Apr 16, 2025, 04:18 PM UTC
Action plan is progressing well and affected customer jobs are stabilising.
-
resolved Apr 22, 2025, 08:59 AM UTC
Issues for affected jobs are resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 26, 2025, 12:00 AM UTC
- Resolved
- Jan 26, 2025, 12:00 AM UTC
- Duration
- –
Timeline · 1 update
-
resolved Jan 26, 2025, 01:13 AM UTC
Core switch issue detected and isolated. Remedial work to be planned shortly.
Read the full incident report →
- Detected by Pingoru
- Jan 23, 2025, 12:26 AM UTC
- Resolved
- Jan 23, 2025, 09:04 AM UTC
- Duration
- 8h 38m
Affected: Hosting Platform
Timeline · 2 updates
-
investigating Jan 23, 2025, 12:26 AM UTC
Our service provider has been carrying out some planned maintenance which has affected connectivity for some customers between 00:00 & 00:15
-
resolved Jan 23, 2025, 09:04 AM UTC
Planned maintenance was completed and no further disruption was noted.
Read the full incident report →
