Störungsverlauf von Codefresh

1. 24. August 2026 um 15:31 UTCinvestigating

   Wir untersuchen derzeit dieses Problem.

2. 24. August 2026 um 16:11 UTCinvestigating

   Wir haben eine Abschwächung für das Problem eingeführt und werden es weiter untersuchen. Das Verhalten der Builds sollte deutlich verbessert werden.

3. 24. August 2026 um 16:46 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 24. August 2026 um 18:21 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 6. Juli 2026 um 13:22 UTCinvestigating

   Wir untersuchen derzeit dieses Problem.

2. 6. Juli 2026 um 13:29 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 6. Juli 2026 um 13:31 UTCmonitoring

   Wir werden weiterhin auf weitere Probleme achten.

4. 6. Juli 2026 um 16:33 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 6. Juli 2026 um 12:32 UTCinvestigating

   Codefresh Classic SaaS Builds können sich verzögern. Wir untersuchen es gerade.

2. 6. Juli 2026 um 13:04 UTCinvestigating

   Mitigation wurde für SaaS-Kunden angewendet. Wir befinden uns derzeit im Überwachungszustand

3. 6. Juli 2026 um 13:33 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 6. Juli 2026 um 16:32 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 5. Juni 2026 um 08: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. 5. Juni 2026 um 08:49 UTCresolved

   This incident has been resolved.

1. 12. Mai 2026 um 17: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. 12. Mai 2026 um 20:19 UTCresolved

   This incident has been resolved.

1. 21. April 2026 um 14:48 UTCinvestigating

   We are currently investigating the issue.

2. 21. April 2026 um 15: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. 22. April 2026 um 10:15 UTCidentified

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

4. 23. April 2026 um 15: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. 24. April 2026 um 09: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. 7. Mai 2026 um 17:55 UTCresolved

   This incident has been resolved.

1. 3. April 2026 um 16:19 UTCinvestigating

   We are currently investigating this issue.

2. 3. April 2026 um 18:04 UTCmonitoring

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

3. 8. April 2026 um 19:02 UTCresolved

   This incident has been resolved.

1. 30. März 2026 um 21: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. 30. März 2026 um 21:17 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 30. März 2026 um 23:19 UTCmonitoring

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

4. 31. März 2026 um 07:20 UTCresolved

   This incident has been resolved.

1. 16. Februar 2026 um 00:29 UTCinvestigating

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

2. 16. Februar 2026 um 01: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. 29. Dezember 2025 um 10:25 UTCinvestigating

   We are currently investigating this issue.

2. 29. Dezember 2025 um 11:26 UTCinvestigating

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

3. 29. Dezember 2025 um 11:49 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 29. Dezember 2025 um 11:56 UTCidentified

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

5. 29. Dezember 2025 um 12:34 UTCmonitoring

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

6. 29. Dezember 2025 um 14:05 UTCresolved

   This incident has been resolved.

1. 18. November 2025 um 21: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. 18. November 2025 um 21:37 UTCmonitoring

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

3. 18. November 2025 um 21:58 UTCresolved

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

1. 18. November 2025 um 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. 18. November 2025 um 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. 18. November 2025 um 13:50 UTCidentified

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

4. 18. November 2025 um 21:22 UTCmonitoring

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

5. 19. November 2025 um 00:42 UTCresolved

   This incident has been resolved.

1. 5. November 2025 um 20: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. 5. November 2025 um 20:00 UTCinvestigating

   We are continuing to investigate this issue.

3. 5. November 2025 um 20: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. 5. November 2025 um 21:23 UTCresolved

   This incident has been resolved.

1. 26. Oktober 2025 um 10:38 UTCinvestigating

   We are currently investigating the issue.

2. 26. Oktober 2025 um 10:54 UTCmonitoring

   A fix has been implemented and we are monitoring the results

3. 26. Oktober 2025 um 11:15 UTCresolved

   This incident has been resolved

1. 20. Oktober 2025 um 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. 20. Oktober 2025 um 10:27 UTCidentified

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

3. 20. Oktober 2025 um 13: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. 20. Oktober 2025 um 15: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. 20. Oktober 2025 um 15: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. 20. Oktober 2025 um 15: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. 20. Oktober 2025 um 18: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. 20. Oktober 2025 um 18:49 UTCmonitoring

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

9. 20. Oktober 2025 um 19:33 UTCmonitoring

   We are continuing to monitor for any further issues.

10. 20. Oktober 2025 um 19:49 UTCresolved

    This incident has been resolved.

1. 13. Oktober 2025 um 14:10 UTCinvestigating

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

2. 13. Oktober 2025 um 16:12 UTCidentified

   Still waiting for the fix to finish implementing.

3. 13. Oktober 2025 um 17:25 UTCmonitoring

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

4. 13. Oktober 2025 um 18:20 UTCresolved

   The issue has been resolved.

1. 25. Juli 2025 um 16: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. 25. Juli 2025 um 16:51 UTCmonitoring

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

3. 25. Juli 2025 um 17:40 UTCresolved

   This incident has been resolved.

1. 12. Juni 2025 um 20: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. 13. Juni 2025 um 02:35 UTCresolved

   This incident has been resolved

1. 27. Mai 2025 um 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. 27. Mai 2025 um 11:40 UTCidentified

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

3. 27. Mai 2025 um 14:01 UTCmonitoring

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

4. 27. Mai 2025 um 14:11 UTCresolved

   This incident has been resolved.

5. 28. Mai 2025 um 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. 21. Mai 2025 um 13:58 UTCinvestigating

   We are currently investigating this issue.

2. 21. Mai 2025 um 14:06 UTCmonitoring

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

3. 21. Mai 2025 um 14:31 UTCresolved

   This incident has been resolved.