Codefresh had 36 outages in the last 2 years totaling 490h 47m of downtime — averaging 1.5 incidents per month.
There were 36 Codefresh outages since June 26, 2024 totaling 490h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.
* BitBucket SSO may be temporarily unavailable. * Classic Builds that are using BitBucket OAuth integrations may be unable to start, or may fail while pulling the code from BitBucket. We are working on resolving the issue as soon as possible.
This incident has been resolved.
We are currently experiencing an issue in which SaaS builds accessing Maven are being rate limited, resulting in 429 errors. Our team is actively working with the vendor to resolve this issue
This incident has been resolved.
We are currently investigating the issue.
We do have steps to help resolve the problem you are currently experiencing with BitBucket. If you are experiencing this issue, please open a ticket with Codefresh Support so we can work with you directly to resolve it.
We are continuing to work on a fix for this issue.
Our team is currently taking steps to mitigate intermittent 429 rate limit errors. In parallel, we are working to resolve the root cause of an issue affecting the OAuth Bitbucket pipeline integration. If you are experiencing these errors and have not yet contacted our support team, please open a ticket. Our team will assist you in applying a temporary workaround while a permanent fix is being developed.
Our team has implemented several mitigations to prevent 429 errors. Our monitoring systems confirm we are no longer experiencing the 429 errors. The team is currently working on fixing the remaining deprecated endpoints.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Codefresh CI Pipeline runs may fail due to image pull issues with our upstream provider (quay.io). Customers may experience intermittent issues with pulling/pushing quay.io-based images while this incident is being addressed.
We are continuing to monitor for any further issues.
Quay.io has restored image pull & push functionality. Codefresh systems should no longer be affected. We are continuing to monitor.
This incident has been resolved.
The Codefresh platform is experiencing some intermittent performance issues which are currently being investigated. We will update as we know more.
This incident has now been resolved. We will conduct further investigations into the load experienced by our backend for specific operations from a small number of customers, and provide details of our findings.
We are currently investigating this issue.
The team has identified the root cause of the issue and is currently working on a solution.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
The issue still partially persists, the team continues to work on a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
As of 20:39 UTC GitHub reported an outage impacting all related git operations. As a result, this will affect the ability to clone/push/pull from GitHub repositories. For more information regarding the GitHub outage, please visit: https://www.githubstatus.com/
It appears that GitHub has shipped a fix, and we're monitoring the recovery now.
Github Git Operations is operating normally as of Nov 18, 2025 - 21:56 UTC
The codefresh.io page and argohub pages are intermittently unreachable for some users. g.codefresh.io remains unaffected. We are currently investigating the issue.
The issue has been identified and is due to a CloudFlare outage. Please follow https://www.cloudflarestatus.com/ for more details The updated list of affected Codefresh systems: - codefresh.io website - docs and marketing content - steps catalog - Argo hub website (for Argo workflow templates)
CloudFlare is continuing to work on restoring services. Please follow https://www.cloudflarestatus.com/ for more details
Most regions are online; however, a few remain unavailable. For the latest news please check https://www.cloudflarestatus.com/
This incident has been resolved.
We are aware of an issue affecting free-tier Codefresh Classic users. While our engineers are working to resolve this, please contact Codefresh support for information on potential workarounds: Codefresh.io/contact-us
We are continuing to investigate this issue.
A fix has been issued. We are continuing to monitor the situation and confirm that users who previously reported the issue are now working as expected.
This incident has been resolved.
We are currently investigating the issue.
A fix has been implemented and we are monitoring the results
This incident has been resolved
The issue has been identified, and the fix is being implemented.
Still waiting for the fix to finish implementing.
A fix has been implemented and we are monitoring the results.
The issue has been resolved.
We are away that there is an incident with quay.io. This affect image pulling for certain steps in codefresh. https://status.redhat.com/incidents/rvtmg00ycbjh You can utilize the Public Marketplace Registry under Account Settings > Pipeline Settings to use a different registry (ex: Dockerhub). https://codefresh.io/docs/docs/pipelines/configuration/pipeline-settings/#advanced-options-for-pipelines
From Quay The 502 issue has been resolved. We'll be extending the maintenance window by 1 hour.
This incident has been resolved.
We are aware of the Google Cloud Platform (GCP) Incident (https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW). The analytics portion of Codefresh is currently experiencing degradation. Build Logs are still operational but rely on GCP services. Builds that utilize GCP integrations may be impacted by this incident.
This incident has been resolved
The problem occurs during the commit phase. Our team is actively working to identify the root cause and resolve the issue. We will provide updates as soon as more information is available.
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.
**Impact:** Git commit operations via GitOps-Runtime were temporarily non-functional. **Detection:** The issue was identified by our internal development team. **Root Cause:** A change in the GitHub API altered a response relied upon by the underlying Git library, causing push actions to fail. **Resolution:** We implemented a temporary fix and provided an upgrade path. GitHub has since resolved the issue on their end, and no action is currently required from users. GitHub's Status Page - \[Retroactive\] Incident with Git Operations: [https://www.githubstatus.com/incidents/tyjjp463pg91](https://www.githubstatus.com/incidents/tyjjp463pg91)
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Some geographical location are unable to connect to g.codefresh.io.
We have identified the issue. There is an issue with our WAF provider for the North America. https://status.imperva.com/incidents/3ffjxyln9pjt
We are continuing to work on a fix for this issue.
Our WAF provided had a brief disruption and their services are getting back to normal across the North America Region. https://status.imperva.com/incidents/3ffjxyln9pjt
Related services should be restored as per our WAF's most recent status update. https://status.imperva.com/incidents/3ffjxyln9pjt
The team has discovered that some hosted GitOps runtimes are missing or no longer visible in the UI. We are currently investigating this issue and will provide an update shortly.
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.
We are currently investigating this issue.
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.
SaaS Builds are currently being stuck on "Validating Connection to Docker Daemon". We have identified the issue and currently working on a solution. Work around would be using the Hybrid Runtime for the builds.
The work around of using Hybrid Runtime is no longer valid. All Builds are now stuck on "Validating Connection to Docker Daemon". We are continuing to work on resolving this issue.
Hybrid Runtimes are now working normally for builds. We are still working on resolving SaaS builds not starting.
We have applied a fix, and builds should resume normal operation. Please allow some time for the retry mechanism to initiate the builds.
This incident has been resolved.
We are currently investigating the issue.
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.
**Impact:** The platform was unavailable for approximately 15 minutes. **Root Cause:** Human error during the execution of a deployment pipeline. **Trigger:** The pipeline was executed with incorrect parameters. **Resolution:** The error was fixed, and the platform was restored **Detection:** The issue was identified internally through monitoring and also reported by our team.
We are currently investigating this issue.
We are continuing to investigate this issue.
The Home Dashboard data related to CI pipelines is only inaccessible for accounts with active GitOps runtimes. CI pipeline-only accounts are not affected.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
We are still continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
**Impact**: The issue affected customers on the CUSTOM plan **Detection** : Internal monitoring system **Root Cause**: Following the release of a new pricing model, a miscommunication between our systems caused the payment plan for some Custom plan accounts to reset to default. **Resolution**: Changes were reverted. Corrupted data was restored from the backup.
We are currently investigating the issue
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.