一部の顧客は、古典的なビルドは保留状態に残ります
Outage重大なインシデント
影響を受けたコンポーネント
Codefresh Classic SLA
- investigating
現在、この問題を調査中です.
- investigating
問題の緩和を実施し、調査を続けております。 ビルドの動作が大幅に改善されるはずです.
- monitoring
修正を実装し、結果を監視しています.
- resolved
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
53 Codefresh incidents · 2023年11月 — official updates, affected components, duration and resolution details.
現在、この問題を調査中です.
問題の緩和を実施し、調査を続けております。 ビルドの動作が大幅に改善されるはずです.
修正を実装し、結果を監視しています.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
現在、この問題を調査中です.
修正を実装し、結果を監視しています.
今後の問題がないか引き続き監視しています。
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
Codefresh Classic SaaSビルドは遅延する場合があります。 現在調査中です.
SaaSのお客様には、マイティグレーションを適用しています。 現在、モニタリング状態にあります
修正を実装し、結果を監視しています.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
* 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.
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
We've started the recovery process after the AWS outage and are performing multiple checks to ensure everything is back to normal
Platform performance remains impacted by the issue, we are continuing to monitor it.
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.
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.
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.
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.
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.
SaaS builds are now operating normally. We are continuing to monitor the situation and the current AWS outage.
We are continuing to monitor for any further issues.
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.