Codefresh incident

g.codefresh.io is down

Major Resolved View vendor source →

Codefresh experienced a major incident on April 8, 2025 affecting Codefresh Classic SLA and Codefresh GitOps SLA and 1 more component, lasting 2h 43m. The incident has been resolved; the full update timeline is below.

Started
Apr 08, 2025, 02:01 PM UTC
Resolved
Apr 08, 2025, 04:44 PM UTC
Duration
2h 43m
Detected by Pingoru
Apr 08, 2025, 02:01 PM UTC

Affected components

Codefresh Classic SLACodefresh GitOps SLAcodefresh.ioCodefresh Classic UICodefresh GitOps UICodefresh Classic Pipeline Engine

Update timeline

  1. investigating Apr 08, 2025, 02:01 PM UTC

    We are currently investigating the issue.

  2. identified Apr 08, 2025, 02:05 PM UTC

    The issue has been identified and a fix is being implemented

  3. monitoring Apr 08, 2025, 02:07 PM UTC

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

  4. resolved Apr 08, 2025, 04:44 PM UTC

    This incident has been resolved.

  5. postmortem Apr 29, 2025, 10:40 AM UTC

    **Impact:** The platform was unavailable for approximately 15 minutes. **Root Cause:** Human error during the execution of a deployment pipeline. **Trigger:** The pipeline was executed with incorrect parameters. **Resolution:** The error was fixed, and the platform was restored **Detection:** The issue was identified internally through monitoring and also reported by our team.