Codefresh incident

Increasing number of delayed builds in some accounts

Minor Resolved View vendor source →

Codefresh experienced a minor incident on February 20, 2025 affecting Codefresh Classic SLA and Codefresh Classic Pipeline Engine, lasting 5h 55m. The incident has been resolved; the full update timeline is below.

Started
Feb 20, 2025, 08:57 AM UTC
Resolved
Feb 20, 2025, 02:53 PM UTC
Duration
5h 55m
Detected by Pingoru
Feb 20, 2025, 08:57 AM UTC

Affected components

Codefresh Classic SLACodefresh Classic Pipeline Engine

Update timeline

  1. investigating Feb 20, 2025, 08:57 AM UTC

    We are currently investigating this issue.

  2. identified Feb 20, 2025, 09:40 AM UTC

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

  3. identified Feb 20, 2025, 10:46 AM UTC

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

  4. identified Feb 20, 2025, 11:42 AM UTC

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

  5. monitoring Feb 20, 2025, 12:24 PM UTC

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

  6. resolved Feb 20, 2025, 02:53 PM UTC

    This incident has been resolved.

  7. postmortem Feb 27, 2025, 01:25 PM UTC

    **Impact**: The issue affected customers on the CUSTOM plan **Detection** : Internal monitoring system **Root Cause**: Following the release of a new pricing model, a miscommunication between our systems caused the payment plan for some Custom plan accounts to reset to default. **Resolution**: Changes were reverted. Corrupted data was restored from the backup.