Replicated had 19 outages in the last 2 years totaling 90h 1m of downtime — averaging 0.8 incidents per month.
There were 19 Replicated outages since October 16, 2025 totaling 90h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.
We're investigating issues that are resulting in degraded ability to access Enterprise Portal V1. This is not currently impacting access to Enterprise Portal V2.
At this time we are observing successful behaviors regarding Enterprise Portal V1. We apologize for the inconvenience this may have caused.
We are aware of a recent issue impacting Enterpise Portal sites. Problems with customer invites and magic links were reported. We've identified a likely root cause, have implemented measures to resolve the issue now and moving forward, and are currently monitoring the rollout. We apologize for this inconvenience and will provide updates on progress and resolution.
The application of our measures to mitigate the issues has completed and we are assessing the improvements for these Enterprise Portal sites.
We are observing expected behavior now from the impacted Enterprise Portal sites. At this time the issue is resolved. Thank you for your patience through this and we apologize for the inconvenience.
We are currently investigating this issue.
We are continuing to investigate this issue impacting OpenShift on Compatibility Matrix
We are observing similar failure patterns in OKE as with VM based clusters of OpenShift. Errors indicate issues with image pulls from registry.k8s.io
We are still observing higher than expected rates when provisioning OpenShift and OKE on Compatibility Matrix. We believe this issue is related to a recent update to registry.k8s.io. We have raised an issue with the maintainers and are working on mitigation.
We have rolled out a mitigation for OKD and are observing significantly better success rates for this distribution. We continue to work on mitigations for OKE.
We have rolled forward with OKE updates to mitigate the observed impact from upstream registry changes. Additionally, the upstream registry changes appear to have been independently resolved. OKE is provisioning successfully in Compatibility Matrix at this time. Thank you for your patience with this matter.
We are observing failures to provision AKS 1.35, 1.36 through CMX and are investigating.
This incident has been resolved.
We're observing a higher than expected error rate for requests handled by an upstream networking provider. This may result in a subset of requests being met with high latency and 5xx errors. We are closely monitoring an ongoing incident with the upstream provider at this time for updates and resolution.
We are continuing to monitor updates provided by our upstream networking provider. The immediate impact that we are observing has been significantly reduced in the last 30 minutes. However, the issue is not fully mitigated or resolved in the upstream provider at this time.
At this time we are no longer observing meaningful impact from the upstream incident with Cloudflare.
A fix has been implemented and we are monitoring the results.
We're continuing to monitor upstream notices from Redhat regarding the quay.io incident. Latest messaging is that Pulls are operational.
The upstream incident with Quay.io which saw failures to Push and Pull images from their registry is improving. We're seeing significantly better success rates for pull operations through the Proxy Registry. At this time impact to Replicated appears mitigated.
There are possible delays when provisioning OpenShift on CMX. This relates to an ongoing incident with an upstream dependency. We are closely watching this and will update as conditions improve. Thank you for your patience.
We're observing now that the upstream dependency issue is resolved and that we're seeing significantly better performance when provisioning OpenShit on CMX. Thank you for your patience with this issue.
https://docs.replicated.com is currently impacted by an incident with an upstream provider. We are closely monitoring this issue and will provide updates here. Thank you for your patience in this matter.
We've seen consistent improvement to the loading and rendering of https://docs.replicated.com. Thank you for your patience through this issue.
We are currently investigating this issue.
We are aware of an outage affecting https://kurl.sh, which prevents access to the documentation and the website that allows building installers yaml. Access to existing installer manifests is unaffected.
We are continuing to investigate this issue.
The upstream outage that was affecting this service has been resolved.
We are continuing to investigate this issue.
This incident has been resolved.
We are currently investigating this issue.
The issue looks to be resolved by azure and we're monitoring the issue.
This incident has been resolved.
We are currently investigating this issue
We are continuing to investigate this issue and will provide periodic updates on the incident.
We are continuing to investigate this issue with provisioning kURL on CMX. We appreciate your patience.
We are continuing to investigate this issue with provisioning kURL on CMX. We appreciate your patience.
We have identified the issue impacting kURL on CMX and are working on a fix.
This incident has been resolved. A fix was released to production.
CMX is impacted by an upstream incident for Azure AKS. We apologize for the inconvenience and are monitoring for improvements.
This incident has been resolved.
We are currently investigating this issue.
We believe this relates to a networking issue with an upstream provider which may be transient. We are exercising end to end tests at the moment to observe improvements internally.
Internal end to end testing is showing successful operations with VMs and Clusters on CMX
CMX operations appear to be working as expected. We are continuing to monitor this situation and the upstream provider.
We are seeing no signs of regression in networking performance or operations of CMX VMS and clusters. This incident is resolved.
Replicated platform is currently impacted by ongoing Cloudflare Major Incident (https://www.cloudflarestatus.com/incidents/8gmgl950y3h7)
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We are seeing some recovery from the ongoing Cloudflare incident. We are continuing to monitor.
We are continuing to monitor for any further issues.
Internal testing and evaluation of the Replicated platform components shows are are operational. Cloudflare is additionally noting that they believe the incident is resolved, though they are continuing to monitor. Should issues arise again we will keep our customers informed of conditions.
This incident has been resolved.
We are currently investigating this issue.
We have observed a significant improvement in these resources following actions from an upstream providers networking. This incident is resolved at this time.
We are currently investigating this issue
We have issued a rollback for a recent change for registry.replicated.com and are monitoring for improvement
We are observing healthy responses from registry.replicated.com at this time. We have identified that error responses observed earlier related to unauthenticated pulls with specific versions of Helm. We are iterating on improvements to mitigate the cause of these problems before rolling back forward.
We have tested changes on the roll forward and responses from registry.replicated.com for Helm pulls continue to appear healthy. This incident is resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being deployed.
A fix has been rolled out, and we are monitoring the results. Vendors may need to refresh the webpage.
This incident has been resolved.
We have identified that provisioning new EKS clusters on CMX has a high failure rate. This appears correlate with an ongoing incident impacting multiple services at AWS. We are monitoring this situation closely.
We are beginning to see recovery for EKS on Compatibility Matrix. We will continue to monitor this and update as conditions change.
AWS is stating at this time that their incident affecting us-east-1 is now resolved. Through careful monitoring and testing we observe that EKS on CMX is working once again
We are currently investigating causes of this issue
We believe we have identified the source of the issue and are working to remediate
We've issued a rollback for the affected platform component and are monitoring for full recovery.
Monitoring appears to show impact has been mitigated at this time.