Historial de interrupciones de Codefresh

1. August 24, 2026 at 3:31 PM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. August 24, 2026 at 4:11 PM UTCinvestigating

   Hemos aplicado una mitigación para la cuestión y seguimos investigandola. El comportamiento de las construcciones debe mejorarse significativamente.

3. August 24, 2026 at 4:46 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. August 24, 2026 at 6:21 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 6, 2026 at 1:22 PM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. July 6, 2026 at 1:29 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. July 6, 2026 at 1:31 PM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

4. July 6, 2026 at 4:33 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 6, 2026 at 12:32 PM UTCinvestigating

   Codefresh Classic SaaS construye puede ser retrasado. Actualmente lo estamos investigando.

2. July 6, 2026 at 1:04 PM UTCinvestigating

   Se ha aplicado mitigación a los clientes de SaaS. Estamos en el estado de vigilancia

3. July 6, 2026 at 1:33 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. July 6, 2026 at 4:32 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 5, 2026 at 8:16 AM 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. June 5, 2026 at 8:49 AM UTCresolved

   This incident has been resolved.

1. May 12, 2026 at 5:34 PM 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. May 12, 2026 at 8:19 PM UTCresolved

   This incident has been resolved.

1. April 21, 2026 at 2:48 PM UTCinvestigating

   We are currently investigating the issue.

2. April 21, 2026 at 3:55 PM 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. April 22, 2026 at 10:15 AM UTCidentified

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

4. April 23, 2026 at 3:32 PM 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. April 24, 2026 at 9:57 AM 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. May 7, 2026 at 5:55 PM UTCresolved

   This incident has been resolved.

1. April 3, 2026 at 4:19 PM UTCinvestigating

   We are currently investigating this issue.

2. April 3, 2026 at 6:04 PM UTCmonitoring

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

3. April 8, 2026 at 7:02 PM UTCresolved

   This incident has been resolved.

1. March 30, 2026 at 9:13 PM 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. March 30, 2026 at 9:17 PM UTCmonitoring

   We are continuing to monitor for any further issues.

3. March 30, 2026 at 11:19 PM UTCmonitoring

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

4. March 31, 2026 at 7:20 AM UTCresolved

   This incident has been resolved.

1. February 16, 2026 at 12:29 AM UTCinvestigating

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

2. February 16, 2026 at 1:44 AM 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. December 29, 2025 at 10:25 AM UTCinvestigating

   We are currently investigating this issue.

2. December 29, 2025 at 11:26 AM UTCinvestigating

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

3. December 29, 2025 at 11:49 AM UTCmonitoring

   We are continuing to monitor for any further issues.

4. December 29, 2025 at 11:56 AM UTCidentified

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

5. December 29, 2025 at 12:34 PM UTCmonitoring

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

6. December 29, 2025 at 2:05 PM UTCresolved

   This incident has been resolved.

1. November 18, 2025 at 9:17 PM 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. November 18, 2025 at 9:37 PM UTCmonitoring

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

3. November 18, 2025 at 9:58 PM UTCresolved

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

1. November 18, 2025 at 12:07 PM 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. November 18, 2025 at 12:21 PM 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. November 18, 2025 at 1:50 PM UTCidentified

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

4. November 18, 2025 at 9:22 PM UTCmonitoring

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

5. November 19, 2025 at 12:42 AM UTCresolved

   This incident has been resolved.

1. November 5, 2025 at 8:00 PM 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. November 5, 2025 at 8:00 PM UTCinvestigating

   We are continuing to investigate this issue.

3. November 5, 2025 at 8:18 PM 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. November 5, 2025 at 9:23 PM UTCresolved

   This incident has been resolved.

1. October 26, 2025 at 10:38 AM UTCinvestigating

   We are currently investigating the issue.

2. October 26, 2025 at 10:54 AM UTCmonitoring

   A fix has been implemented and we are monitoring the results

3. October 26, 2025 at 11:15 AM UTCresolved

   This incident has been resolved

1. October 20, 2025 at 10:12 AM UTCidentified

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

2. October 20, 2025 at 10:27 AM UTCidentified

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

3. October 20, 2025 at 1:41 PM 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. October 20, 2025 at 3:18 PM 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. October 20, 2025 at 3:33 PM 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. October 20, 2025 at 3:58 PM 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. October 20, 2025 at 6:01 PM 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. October 20, 2025 at 6:49 PM UTCmonitoring

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

9. October 20, 2025 at 7:33 PM UTCmonitoring

   We are continuing to monitor for any further issues.

10. October 20, 2025 at 7:49 PM UTCresolved

    This incident has been resolved.

1. October 13, 2025 at 2:10 PM UTCinvestigating

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

2. October 13, 2025 at 4:12 PM UTCidentified

   Still waiting for the fix to finish implementing.

3. October 13, 2025 at 5:25 PM UTCmonitoring

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

4. October 13, 2025 at 6:20 PM UTCresolved

   The issue has been resolved.

1. July 25, 2025 at 4:40 PM 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. July 25, 2025 at 4:51 PM UTCmonitoring

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

3. July 25, 2025 at 5:40 PM UTCresolved

   This incident has been resolved.

1. June 12, 2025 at 8:34 PM 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. June 13, 2025 at 2:35 AM UTCresolved

   This incident has been resolved

1. May 27, 2025 at 10:00 AM 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. May 27, 2025 at 11:40 AM UTCidentified

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

3. May 27, 2025 at 2:01 PM UTCmonitoring

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

4. May 27, 2025 at 2:11 PM UTCresolved

   This incident has been resolved.

5. May 28, 2025 at 12:25 PM 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. May 21, 2025 at 1:58 PM UTCinvestigating

   We are currently investigating this issue.

2. May 21, 2025 at 2:06 PM UTCmonitoring

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

3. May 21, 2025 at 2:31 PM UTCresolved

   This incident has been resolved.