Codefresh 장애 기록

1. 2026년 8월 24일 오후 3:31 UTCinvestigating

   우리는 현재이 문제를 조사하고 있습니다.

2. 2026년 8월 24일 오후 4:11 UTCinvestigating

   우리는 문제의 완화를 구현하고 조사를 계속합니다. 빌드의 행동은 크게 향상되어야한다.

3. 2026년 8월 24일 오후 4:46 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

4. 2026년 8월 24일 오후 6:21 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 6일 오후 1:22 UTCinvestigating

   우리는 현재이 문제를 조사하고 있습니다.

2. 2026년 7월 6일 오후 1:29 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 7월 6일 오후 1:31 UTCmonitoring

   우리는 더 많은 문제를 모니터링하고 있습니다.

4. 2026년 7월 6일 오후 4:33 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 6일 오후 12:32 UTCinvestigating

   Codefresh Classic SaaS는 지연될 수 있습니다. 현재 투자하고 있습니다.

2. 2026년 7월 6일 오후 1:04 UTCinvestigating

   Mitigation은 SaaS 고객에게 적용되었습니다. 현재 모니터링 상태입니다

3. 2026년 7월 6일 오후 1:33 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

4. 2026년 7월 6일 오후 4:32 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 5일 오전 8:16 UTCidentified

   * 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.

2. 2026년 6월 5일 오전 8:49 UTCresolved

   This incident has been resolved.

1. 2026년 5월 12일 오후 5:34 UTCidentified

   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

2. 2026년 5월 12일 오후 8:19 UTCresolved

   This incident has been resolved.

1. 2026년 4월 21일 오후 2:48 UTCinvestigating

   We are currently investigating the issue.

2. 2026년 4월 21일 오후 3:55 UTCidentified

   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.

3. 2026년 4월 22일 오전 10:15 UTCidentified

   We are continuing to work on a fix for this issue.

4. 2026년 4월 23일 오후 3:32 UTCidentified

   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.

5. 2026년 4월 24일 오전 9:57 UTCidentified

   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.

6. 2026년 5월 7일 오후 5:55 UTCresolved

   This incident has been resolved.

1. 2026년 4월 3일 오후 4:19 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 4월 3일 오후 6:04 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2026년 4월 8일 오후 7:02 UTCresolved

   This incident has been resolved.

1. 2026년 3월 30일 오후 9:13 UTCmonitoring

   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.

2. 2026년 3월 30일 오후 9:17 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 2026년 3월 30일 오후 11:19 UTCmonitoring

   Quay.io has restored image pull & push functionality. Codefresh systems should no longer be affected. We are continuing to monitor.

4. 2026년 3월 31일 오전 7:20 UTCresolved

   This incident has been resolved.

1. 2026년 2월 16일 오전 12:29 UTCinvestigating

   The Codefresh platform is experiencing some intermittent performance issues which are currently being investigated. We will update as we know more.

2. 2026년 2월 16일 오전 1:44 UTCresolved

   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.

1. 2025년 12월 29일 오전 10:25 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 12월 29일 오전 11:26 UTCinvestigating

   The team has identified the root cause of the issue and is currently working on a solution.

3. 2025년 12월 29일 오전 11:49 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2025년 12월 29일 오전 11:56 UTCidentified

   The issue still partially persists, the team continues to work on a fix.

5. 2025년 12월 29일 오후 12:34 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

6. 2025년 12월 29일 오후 2:05 UTCresolved

   This incident has been resolved.

1. 2025년 11월 18일 오후 9:17 UTCidentified

   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/

2. 2025년 11월 18일 오후 9:37 UTCmonitoring

   It appears that GitHub has shipped a fix, and we're monitoring the recovery now.

3. 2025년 11월 18일 오후 9:58 UTCresolved

   Github Git Operations is operating normally as of Nov 18, 2025 - 21:56 UTC

1. 2025년 11월 18일 오후 12:07 UTCinvestigating

   The codefresh.io page and argohub pages are intermittently unreachable for some users. g.codefresh.io remains unaffected. We are currently investigating the issue.

2. 2025년 11월 18일 오후 12:21 UTCidentified

   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)

3. 2025년 11월 18일 오후 1:50 UTCidentified

   CloudFlare is continuing to work on restoring services. Please follow https://www.cloudflarestatus.com/ for more details

4. 2025년 11월 18일 오후 9:22 UTCmonitoring

   Most regions are online; however, a few remain unavailable. For the latest news please check https://www.cloudflarestatus.com/

5. 2025년 11월 19일 오전 12:42 UTCresolved

   This incident has been resolved.

1. 2025년 11월 5일 오후 8:00 UTCinvestigating

   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

2. 2025년 11월 5일 오후 8:00 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 11월 5일 오후 8:18 UTCmonitoring

   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.

4. 2025년 11월 5일 오후 9:23 UTCresolved

   This incident has been resolved.

1. 2025년 10월 26일 오전 10:38 UTCinvestigating

   We are currently investigating the issue.

2. 2025년 10월 26일 오전 10:54 UTCmonitoring

   A fix has been implemented and we are monitoring the results

3. 2025년 10월 26일 오전 11:15 UTCresolved

   This incident has been resolved

1. 2025년 10월 20일 오전 10:12 UTCidentified

   We've started the recovery process after the AWS outage and are performing multiple checks to ensure everything is back to normal

2. 2025년 10월 20일 오전 10:27 UTCidentified

   Platform performance remains impacted by the issue, we are continuing to monitor it.

3. 2025년 10월 20일 오후 1:41 UTCidentified

   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.

4. 2025년 10월 20일 오후 3:18 UTCidentified

   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.

5. 2025년 10월 20일 오후 3:33 UTCidentified

   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.

6. 2025년 10월 20일 오후 3:58 UTCidentified

   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.

7. 2025년 10월 20일 오후 6:01 UTCidentified

   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.

8. 2025년 10월 20일 오후 6:49 UTCmonitoring

   SaaS builds are now operating normally. We are continuing to monitor the situation and the current AWS outage.

9. 2025년 10월 20일 오후 7:33 UTCmonitoring

   We are continuing to monitor for any further issues.

10. 2025년 10월 20일 오후 7:49 UTCresolved

    This incident has been resolved.

1. 2025년 10월 13일 오후 2:10 UTCinvestigating

   The issue has been identified, and the fix is being implemented.

2. 2025년 10월 13일 오후 4:12 UTCidentified

   Still waiting for the fix to finish implementing.

3. 2025년 10월 13일 오후 5:25 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2025년 10월 13일 오후 6:20 UTCresolved

   The issue has been resolved.

1. 2025년 7월 25일 오후 4:40 UTCidentified

   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

2. 2025년 7월 25일 오후 4:51 UTCmonitoring

   From Quay The 502 issue has been resolved. We'll be extending the maintenance window by 1 hour.

3. 2025년 7월 25일 오후 5:40 UTCresolved

   This incident has been resolved.

1. 2025년 6월 12일 오후 8:34 UTCmonitoring

   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.

2. 2025년 6월 13일 오전 2:35 UTCresolved

   This incident has been resolved

1. 2025년 5월 27일 오전 10:00 UTCinvestigating

   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.

2. 2025년 5월 27일 오전 11:40 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2025년 5월 27일 오후 2:01 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2025년 5월 27일 오후 2:11 UTCresolved

   This incident has been resolved.

5. 2025년 5월 28일 오후 12:25 UTCpostmortem

   **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)

1. 2025년 5월 21일 오후 1:58 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 5월 21일 오후 2:06 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2025년 5월 21일 오후 2:31 UTCresolved

   This incident has been resolved.