Vendor Status Watch

← all vendors

Codefresh status history

Current state: operational — “All Systems Operational” per http://status.codefresh.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
3incidents, last 90 days
16incidents on record
Incidents per week, last 12 weeks:

How long do Codefresh incidents last?

3.0 hmedian incident duration16 measured
12.6 h90th percentile1 in 10 ran longer
2.8 hmedian, major/critical only3 incidents

From 16 incidents with a vendor-posted start and resolve time. Longest on record: OAuth Bitbucket integrations and triggers are facing rate limit issues — 16.1 days (2026-04-21 14:48 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (16)

StartedIncidentStatusImpactDuration
2026-08-24 15:31 UTCSome customers report classic builds remain in the pending stateresolvedmajor2 h 50 min
2026-07-06 13:22 UTCg.codefresh.io is intermittently unreachable for some usersresolvedminor3 h 11 min
2026-07-06 12:32 UTCCodefresh Classic SaaS builds may be delayedresolvedminor4 h 00 min
2026-06-05 08:16 UTCBitBucket SSO and OAuth integrations: degraded performanceresolvedminor33 min
2026-05-12 17:34 UTCMaven repository rate limit (429 Errors) on SaaS builds.resolvednone2 h 45 min
2026-04-21 14:48 UTCOAuth Bitbucket integrations and triggers are facing rate limit issuesresolvedminor16 d 3 h
2026-04-03 16:19 UTCSome accounts may encounter delays and slow response times when viewing GitOps Dashboards data.resolvedminor2 h 42 min
2026-03-30 21:13 UTCCodefresh CI Pipeline Runs Failing Due to Image Pull Failureresolvedmajor10 h 06 min
2026-02-16 00:29 UTCPerformance issues with the Codefresh platformresolvedminor1 h 15 min
2025-12-29 10:25 UTCSome accounts may experience issues with viewing the audit dataresolvedminor3 h 40 min
2025-11-18 21:17 UTCGitHub upstream outage impacting Classic Pipelines (and other GH dependent services)resolvedmajor40 min
2025-11-18 12:07 UTCcodefresh.io is intermittently unreachable for some usersresolvedminor12 h 35 min
2025-11-05 20:00 UTCFree-tier Codefresh Classic users unable to run classic pipeline builds on SaaS.resolvedminor59 min
2025-10-26 10:38 UTCGitOps UI Slownessresolvedminor36 min
2025-10-20 10:12 UTCAn ongoing AWS US East outage is causing platform degradationresolvedminor9 h 36 min
2025-10-13 14:10 UTCSome degraded performance in the UIresolvedminor4 h 10 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Codefresh with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "codefresh"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}