Replicated had 35 outages in the last 2 years totaling 296h 41m of downtime — averaging 1.4 incidents per month.
There were 35 Replicated outages since October 21, 2024 totaling 296h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.
AKS instance types Standard_D2S_v5, Standard_D4S_v5, Standard_D8S_v5, Standard_D16S_v5, Standard_D32S_v5, and Standard_D48S_v5 are currently unavailable. We are working with Azure to correct this issue.
The incident has been resolved
We are aware of upstream issues with Google Cloud Platform. This is presently impacting GKE components of our Compatibility Matrix product, and upstream GCR registries with our Replicated Registry. We are monitoring our cloud providers for updates.
We are continuing to monitor upstream issues with Google Cloud Platform and Cloudflare
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
This incident has been resolved.
We're aware of network issues when creating an RKE2 cluster and are investigating
This incident has been resolved.
We have noticed that GKE 1.32 clusters are not reaching a 'running' state. We are currently investigating this issue.
We have identified an issue with pulling images from Google's registry, and are working with Google to find a resolution.
We have rolled out a fix, pinning GKE 1.32 to version 1.32.2, and are monitoring the results now.
We are continuing to monitor for any further issues.
This incident has been resolved.
Check your spam folder. Our transactional email provider is seeing deliverability problems with gmail. https://status.postmarkapp.com/notices/bt3ky3r8zlaapqlo-increased-gmail-spam-reports
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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