Codefresh Outage History
Codefresh is up right nowPingoru has recorded 50 incidents for Codefresh: 13 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 228 of 720 (32%) |
| May 2026 | 1 | 111 of 744 (15%) |
| June 2026 | 1 | 1 of 720 (0%) |
| July 2026 | 2 | 4 of 744 (1%) |
| August 2026 | 1 | 3 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 19 (0%) |
Incidents, newest first
Major August 24, 2026 Some customers report classic builds remain in the pending state 2h 50m Codefresh Classic SLA
Started Aug 24, 2026, 03:31 PM UTC· resolved Aug 24, 2026, 06:21 PM UTC
- investigating Aug 24, 2026, 03:31 PM UTC
We are currently investigating this issue.
- investigating Aug 24, 2026, 04:11 PM UTC
We have implemented a mitigation for the issue and are continuing to investigate it. The builds' behavior should be significantly improved.
- monitoring Aug 24, 2026, 04:46 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 24, 2026, 06:21 PM UTC
This incident has been resolved.
Minor July 6, 2026 g.codefresh.io is intermittently unreachable for some users 3h 11m codefresh.io, Codefresh Classic UI, Codefresh GitOps UI, Codefresh API and 2 more
Started Jul 06, 2026, 01:22 PM UTC· resolved Jul 06, 2026, 04:33 PM UTC
- investigating Jul 06, 2026, 01:22 PM UTC
We are currently investigating this issue.
- monitoring Jul 06, 2026, 01:29 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jul 06, 2026, 01:31 PM UTC
We are continuing to monitor for any further issues.
- resolved Jul 06, 2026, 04:33 PM UTC
This incident has been resolved.
Minor July 6, 2026 Codefresh Classic SaaS builds may be delayed 4h Codefresh Classic Pipeline Engine
Started Jul 06, 2026, 12:32 PM UTC· resolved Jul 06, 2026, 04:32 PM UTC
- investigating Jul 06, 2026, 12:32 PM UTC
Codefresh Classic SaaS builds may be delayed. We're currently investigating it.
- investigating Jul 06, 2026, 01:04 PM UTC
Mitigation has been applied for SaaS customers. We're currently in the monitoring state
- monitoring Jul 06, 2026, 01:33 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 06, 2026, 04:32 PM UTC
This incident has been resolved.
Minor June 5, 2026 BitBucket SSO and OAuth integrations: degraded performance 33m Login via BitBucket, Codefresh Classic Pipeline Engine
Started Jun 05, 2026, 08:16 AM UTC· resolved Jun 05, 2026, 08:49 AM UTC
- identified Jun 05, 2026, 08:16 AM UTC
* 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.
- resolved Jun 05, 2026, 08:49 AM UTC
This incident has been resolved.
Notice May 12, 2026 Maven repository rate limit (429 Errors) on SaaS builds. 2h 45m 3rd Party Services that Codefresh does not depend on:
Started May 12, 2026, 05:34 PM UTC· resolved May 12, 2026, 08:19 PM UTC
- identified May 12, 2026, 05:34 PM UTC
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
- resolved May 12, 2026, 08:19 PM UTC
This incident has been resolved.
Minor April 21, 2026 OAuth Bitbucket integrations and triggers are facing rate limit issues 16d 3h Codefresh Classic Pipeline Engine
Started Apr 21, 2026, 02:48 PM UTC· resolved May 07, 2026, 05:55 PM UTC
- investigating Apr 21, 2026, 02:48 PM UTC
We are currently investigating the issue.
- identified Apr 21, 2026, 03:55 PM UTC
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.
- identified Apr 22, 2026, 10:15 AM UTC
We are continuing to work on a fix for this issue.
- identified Apr 23, 2026, 03:32 PM UTC
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.
- identified Apr 24, 2026, 09:57 AM UTC
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.
- resolved May 07, 2026, 05:55 PM UTC
This incident has been resolved.
Minor April 3, 2026 Some accounts may encounter delays and slow response times when viewing GitOps Dashboards data. 2h 42m Codefresh GitOps UI
Started Apr 03, 2026, 04:19 PM UTC· resolved Apr 03, 2026, 07:02 PM UTC
- investigating Apr 03, 2026, 04:19 PM UTC
We are currently investigating this issue.
- monitoring Apr 03, 2026, 06:04 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 03, 2026, 07:02 PM UTC
This incident has been resolved.
Major March 30, 2026 Codefresh CI Pipeline Runs Failing Due to Image Pull Failure 10h 6m Codefresh Classic Steps Marketplace, Codefresh Classic Pipeline Engine
Started Mar 30, 2026, 09:13 PM UTC· resolved Mar 31, 2026, 07:20 AM UTC
- monitoring Mar 30, 2026, 09:13 PM UTC
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.
- monitoring Mar 30, 2026, 09:17 PM UTC
We are continuing to monitor for any further issues.
- monitoring Mar 30, 2026, 11:19 PM UTC
Quay.io has restored image pull & push functionality. Codefresh systems should no longer be affected. We are continuing to monitor.
- resolved Mar 31, 2026, 07:20 AM UTC
This incident has been resolved.
Minor February 16, 2026 Performance issues with the Codefresh platform 1h 15m Codefresh Classic SLA, Codefresh GitOps SLA, codefresh.io, Codefresh Classic UI and 11 more
Started Feb 16, 2026, 12:29 AM UTC· resolved Feb 16, 2026, 01:44 AM UTC
- investigating Feb 16, 2026, 12:29 AM UTC
The Codefresh platform is experiencing some intermittent performance issues which are currently being investigated. We will update as we know more.
- resolved Feb 16, 2026, 01:44 AM UTC
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.
Minor December 29, 2025 Some accounts may experience issues with viewing the audit data 3h 40m Codefresh API
Started Dec 29, 2025, 10:25 AM UTC· resolved Dec 29, 2025, 02:05 PM UTC
- investigating Dec 29, 2025, 10:25 AM UTC
We are currently investigating this issue.
- investigating Dec 29, 2025, 11:26 AM UTC
The team has identified the root cause of the issue and is currently working on a solution.
- monitoring Dec 29, 2025, 11:48 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Dec 29, 2025, 11:49 AM UTC
We are continuing to monitor for any further issues.
- identified Dec 29, 2025, 11:56 AM UTC
The issue still partially persists, the team continues to work on a fix.
- monitoring Dec 29, 2025, 12:34 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 29, 2025, 02:05 PM UTC
This incident has been resolved.
Major November 18, 2025 GitHub upstream outage impacting Classic Pipelines (and other GH dependent services) 40m GitHub, Codefresh Classic Pipeline Engine
Started Nov 18, 2025, 09:17 PM UTC· resolved Nov 18, 2025, 09:58 PM UTC
- identified Nov 18, 2025, 09:17 PM UTC
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/
- monitoring Nov 18, 2025, 09:37 PM UTC
It appears that GitHub has shipped a fix, and we're monitoring the recovery now.
- resolved Nov 18, 2025, 09:58 PM UTC
Github Git Operations is operating normally as of Nov 18, 2025 - 21:56 UTC
Minor November 18, 2025 codefresh.io is intermittently unreachable for some users 12h 35m codefresh.io
Started Nov 18, 2025, 12:07 PM UTC· resolved Nov 19, 2025, 12:42 AM UTC
- investigating Nov 18, 2025, 12:07 PM 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.
- identified Nov 18, 2025, 12:21 PM UTC
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)
- identified Nov 18, 2025, 01:50 PM UTC
CloudFlare is continuing to work on restoring services. Please follow https://www.cloudflarestatus.com/ for more details
- monitoring Nov 18, 2025, 09:22 PM UTC
Most regions are online; however, a few remain unavailable. For the latest news please check https://www.cloudflarestatus.com/
- resolved Nov 19, 2025, 12:42 AM UTC
This incident has been resolved.
Minor November 5, 2025 Free-tier Codefresh Classic users unable to run classic pipeline builds on SaaS. 59m Codefresh Classic Pipeline Engine
Started Nov 05, 2025, 08:00 PM UTC· resolved Nov 05, 2025, 09:00 PM UTC
- investigating Nov 05, 2025, 08:00 PM UTC
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
- investigating Nov 05, 2025, 08:00 PM UTC
We are continuing to investigate this issue.
- monitoring Nov 05, 2025, 08:18 PM UTC
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.
- resolved Nov 05, 2025, 09:00 PM UTC
This incident has been resolved.
Minor October 26, 2025 GitOps UI Slowness 36m Codefresh GitOps UI
Started Oct 26, 2025, 10:38 AM UTC· resolved Oct 26, 2025, 11:15 AM UTC
- investigating Oct 26, 2025, 10:38 AM UTC
We are currently investigating the issue.
- monitoring Oct 26, 2025, 10:54 AM UTC
A fix has been implemented and we are monitoring the results
- resolved Oct 26, 2025, 11:15 AM UTC
This incident has been resolved
Minor October 20, 2025 An ongoing AWS US East outage is causing platform degradation 9h 36m codefresh.io, Codefresh Classic UI, Codefresh GitOps UI, Codefresh Classic Pipeline Engine and 2 more
Started Oct 20, 2025, 10:12 AM UTC· resolved Oct 20, 2025, 07:49 PM UTC
- identified Oct 20, 2025, 10:12 AM UTC
We've started the recovery process after the AWS outage and are performing multiple checks to ensure everything is back to normal
- identified Oct 20, 2025, 10:27 AM UTC
Platform performance remains impacted by the issue, we are continuing to monitor it.
- identified Oct 20, 2025, 01:41 PM UTC
SaaS builds are seeing increased retry rates due to ongoing EC2 issues on AWS. We've applied mitigations to reduce the impact, but some delays may still occur. AWS is still reporting EC2 as affected. We’re monitoring the situation and will update as we have more information.
- identified Oct 20, 2025, 03:18 PM UTC
AWS is still seeing connectivity issues in US-East region. We’re still monitoring the situation and will update as we have more information as it related to the platform.
- identified Oct 20, 2025, 03:33 PM UTC
To mitigate issues around the regional AWS outage, we're working on migrating to an unaffected region. We'll update as the migration progresses and continue to monitor the situation.
- identified Oct 20, 2025, 03:58 PM UTC
We're seeing an increase impact of degreated performance across the platform. We're still working to migrating to another unaffected region at this time.
- identified Oct 20, 2025, 06:01 PM UTC
We are still working on migrating to an unaffected region. For critical pipelines, a workaround is to install a Hybrid Pipeline Runtime in a region unaffected by the AWS outage. Once installed, configure the pipeline to use this Hybrid Runtime.
- monitoring Oct 20, 2025, 06:49 PM UTC
SaaS builds are now operating normally. We are continuing to monitor the situation and the current AWS outage.
- monitoring Oct 20, 2025, 07:33 PM UTC
We are continuing to monitor for any further issues.
- resolved Oct 20, 2025, 07:49 PM UTC
This incident has been resolved.
Minor October 13, 2025 Some degraded performance in the UI 4h 10m codefresh.io, Codefresh GitOps UI
Started Oct 13, 2025, 02:10 PM UTC· resolved Oct 13, 2025, 06:20 PM UTC
- investigating Oct 13, 2025, 02:10 PM UTC
The issue has been identified, and the fix is being implemented.
- identified Oct 13, 2025, 04:12 PM UTC
Still waiting for the fix to finish implementing.
- monitoring Oct 13, 2025, 05:25 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 13, 2025, 06:20 PM UTC
The issue has been resolved.
Minor July 25, 2025 Quay.io Emergency Maintenance 1h
Started Jul 25, 2025, 04:40 PM UTC· resolved Jul 25, 2025, 05:40 PM UTC
- identified Jul 25, 2025, 04:40 PM UTC
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
- monitoring Jul 25, 2025, 04:51 PM UTC
From Quay The 502 issue has been resolved. We'll be extending the maintenance window by 1 hour.
- resolved Jul 25, 2025, 05:40 PM UTC
This incident has been resolved.
Notice June 12, 2025 GCP Incident 6h 1m
Started Jun 12, 2025, 08:34 PM UTC· resolved Jun 13, 2025, 02:35 AM UTC
- monitoring Jun 12, 2025, 08:34 PM UTC
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.
- resolved Jun 13, 2025, 02:35 AM UTC
This incident has been resolved
Minor May 27, 2025 The issue with running promotions & git push operations from the codefresh UI 4h 10m Codefresh GitOps SLA, Codefresh GitOps Metadata and Metrics
Started May 27, 2025, 10:00 AM UTC· resolved May 27, 2025, 02:11 PM UTC
- investigating May 27, 2025, 10:00 AM UTC
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.
- identified May 27, 2025, 11:40 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring May 27, 2025, 02:01 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 27, 2025, 02:11 PM UTC
This incident has been resolved.
- postmortem May 28, 2025, 12:25 PM UTC
**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)
Minor May 21, 2025 Degraded performance on some UI pages and builds 33m Codefresh Classic SLA, codefresh.io, Codefresh Classic UI, Codefresh API and 1 more
Started May 21, 2025, 01:58 PM UTC· resolved May 21, 2025, 02:31 PM UTC
- investigating May 21, 2025, 01:58 PM UTC
We are currently investigating this issue.
- monitoring May 21, 2025, 02:06 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 21, 2025, 02:31 PM UTC
This incident has been resolved.
Major May 14, 2025 g.codefresh.io not available for North America Region 1h 1m codefresh.io
Started May 14, 2025, 04:25 PM UTC· resolved May 14, 2025, 05:27 PM UTC
- investigating May 14, 2025, 04:25 PM UTC
Some geographical location are unable to connect to g.codefresh.io.
- identified May 14, 2025, 04:47 PM UTC
We have identified the issue. There is an issue with our WAF provider for the North America. https://status.imperva.com/incidents/3ffjxyln9pjt
- identified May 14, 2025, 04:55 PM UTC
We are continuing to work on a fix for this issue.
- monitoring May 14, 2025, 05:18 PM UTC
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
- resolved May 14, 2025, 05:27 PM UTC
Related services should be restored as per our WAF's most recent status update. https://status.imperva.com/incidents/3ffjxyln9pjt
Major May 12, 2025 Several hosted GitOps runtimes are unavailable or missing from the UI 1h 49m Codefresh Hosted GitOps Services
Started May 12, 2025, 12:59 PM UTC· resolved May 12, 2025, 02:48 PM UTC
- investigating May 12, 2025, 12:59 PM UTC
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.
- identified May 12, 2025, 01:32 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring May 12, 2025, 02:09 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 12, 2025, 02:48 PM UTC
This incident has been resolved.
Minor April 23, 2025 Some builds fail to start on Codefresh SaaS environment 39m Codefresh Classic SLA, codefresh.io, Codefresh Classic Pipeline Engine
Started Apr 23, 2025, 02:36 PM UTC· resolved Apr 23, 2025, 03:15 PM UTC
- investigating Apr 23, 2025, 02:36 PM UTC
We are currently investigating this issue.
- identified Apr 23, 2025, 02:56 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 23, 2025, 03:00 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 23, 2025, 03:15 PM UTC
This incident has been resolved.
Critical April 18, 2025 Builds stuck on Validating Connection to Docker Daemon 2h 40m Codefresh Classic Pipeline Engine
Started Apr 18, 2025, 07:11 PM UTC· resolved Apr 18, 2025, 09:51 PM UTC
- identified Apr 18, 2025, 07:11 PM UTC
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.
- identified Apr 18, 2025, 08:31 PM UTC
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.
- identified Apr 18, 2025, 08:40 PM UTC
Hybrid Runtimes are now working normally for builds. We are still working on resolving SaaS builds not starting.
- monitoring Apr 18, 2025, 08:51 PM UTC
We have applied a fix, and builds should resume normal operation. Please allow some time for the retry mechanism to initiate the builds.
- resolved Apr 18, 2025, 09:51 PM UTC
This incident has been resolved.
Major April 8, 2025 g.codefresh.io is down 2h 43m Codefresh Classic SLA, Codefresh GitOps SLA, codefresh.io, Codefresh Classic UI and 2 more
Started Apr 08, 2025, 02:01 PM UTC· resolved Apr 08, 2025, 04:44 PM UTC
- investigating Apr 08, 2025, 02:01 PM UTC
We are currently investigating the issue.
- identified Apr 08, 2025, 02:05 PM UTC
The issue has been identified and a fix is being implemented
- monitoring Apr 08, 2025, 02:07 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 08, 2025, 04:44 PM UTC
This incident has been resolved.
- postmortem Apr 29, 2025, 10:40 AM UTC
**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.