Codefresh incident

An ongoing AWS US East outage is causing platform degradation

Minor Resolved View vendor source →

Codefresh experienced a minor incident on October 20, 2025 affecting codefresh.io and Codefresh Classic UI and 1 more component, lasting 9h 36m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 10:12 AM UTC
Resolved
Oct 20, 2025, 07:49 PM UTC
Duration
9h 36m
Detected by Pingoru
Oct 20, 2025, 10:12 AM UTC

Affected components

codefresh.ioCodefresh Classic UICodefresh GitOps UICodefresh Classic Pipeline EngineCodefresh GitOps Metadata and MetricsCodefresh Classic GitOps Dashboard

Update timeline

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

  2. identified Oct 20, 2025, 10:27 AM UTC

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

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

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

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

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

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

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

  9. monitoring Oct 20, 2025, 07:33 PM UTC

    We are continuing to monitor for any further issues.

  10. resolved Oct 20, 2025, 07:49 PM UTC

    This incident has been resolved.