Replicated had 40 outages in the last 2 years totaling 30h 10m of downtime — averaging 1.6 incidents per month.
There were 40 Replicated outages since June 17, 2024 totaling 30h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating issues with provisioning k3s CMX clusters leading to timeouts
This issue is likely impacting kind cluster creation as well
We are seeing k3s and kind CMX clusters spinning up successfully at this time without timing out. We are continuing to monitor this situation.
This incident has been resolved.
We are currently investigating issues with name resolution in some containers in OpenShift clusters, in Compatibility Matrix
We have run diagnostics across the OpenShift cluster and found the source of the report, however it appears that the limitation is built into OpenShift by design and working as intended.
We are currently investigating this issue
We are continuing to investigate this issue.
We are continuing to investigate this issue.
We believe we have identified the cause of these issues and are working to remediate them.
We have deployed changes to help mitigate issues creating k3s, kind, kURL, and Embedded Clusters on CMX. We are currently monitoring these changes.
Our monitoring confirms that remediation efforts are now showing successful k3s, kind, kURL, and Embedded Cluster in CMX.
We have identified the issues causing a higher than expected 5xx rate for the Vendor API. We have mitigated this by rolling back some recent changes and are working on a long-term solution.
A long-term fix for this issue has been released and we are currently monitoring.
This issue should now be resolved
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This issue only impacts EOA distribution of Native applications, KOTS, Helm, kURL, EC distributed applications are not impacted. We are working to address this for impacted vendors.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
This incident has been resolved.
Some applications are unable to access the Embedded Cluster download page. We are currently investigating this issue.
The issue has been identified and we are working on rolling out a fix.
The fix has been released and we are monitoring the results.
The fix has been rolled out and tested. Thanks for your patience.
Beta Feature Functionality Degraded: Embedded Cluster downloads were not available from the Download Portal.
We are investigating issues related to not being able to create clusters through the vendor portal for the compatibility-matrix service
We have identified the source of the issue, we are working to implement a fix now.
We have rolled out a fix for the issue and are monitoring to ensure it is fully resolved.
This incident has been resolved.
We are investigating reports that custom hostnames may not be working for some customers. We are currently working to restore this functionality for those affected.
We have restored this functionality for customers and are monitoring at this time
This incident has been resolved.
We are currently investigating reports of issues creating Kots releases in the Vendor Portal
We are working to roll back changes that may be contributing to this issue
We have rolled back changes that have contributed to this issue. We can confirm that creating Kots releases in Vendor Portal is working as expected at this time. Users affected by this will need to log out and back in.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are monitoring progress on the ongoing incident with Docker Registry as this is impacting customer workloads
Docker is reporting that the incident affecting the Docker Registry has been resolved
We are currently experiencing a system wide outage. Our team is looking into resolving it as soon as possible.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
This incident has been resolved.
Customers are experiencing delays receiving activation code emails
We believe these delays are related to an ongoing incident with our email provider. We are monitoring for resolution on their end at this time.
Our email provider has updated their incident with information that they have identified the cause of delays and are actively working to resolve the issue.
We are continuing to monitor our email provider for improvements to this issue
Our email provider is indicating that they are mitigating the cause of this issue and that emails are beginning to process and send. We continue to monitor for resolution on this issue.
We are continuing to monitor our email provider for resolution to this issue
Our email provider has implemented a fix to resolve email deliverability issues. We continue to monitor for resolution of their incident.
Our email provider has stated the issue is resolved on their platform. We are also seeing successful email delivery at this time.