Codefresh Outage History

15 incidents recorded over the last 365 days, 13 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Codefresh status100.00% uptime history

Every Recorded Codefresh Incident

Codefresh incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 18, 2026Scheduled Maintenance September 18th 0500-1400 UTCThe scheduled maintenance has been completed.9h 0mScheduled
Aug 24, 2026Some customers report classic builds remain in the pending stateThis incident has been resolved.2h 50mResolved
Jul 6, 2026g.codefresh.io is intermittently unreachable for some usersThis incident has been resolved.3h 11mResolved
Jul 6, 2026Codefresh Classic SaaS builds may be delayedThis incident has been resolved.4h 0mResolved
Jun 5, 2026BitBucket SSO and OAuth integrations: degraded performanceThis incident has been resolved.33 minResolved
May 12, 2026Maven repository rate limit (429 Errors) on SaaS builds.This incident has been resolved.2h 45mResolved
Apr 21, 2026OAuth Bitbucket integrations and triggers are facing rate limit issuesThis incident has been resolved.387h 7mResolved
Apr 3, 2026Some accounts may encounter delays and slow response times when viewing GitOps Dashboards data.This incident has been resolved.2h 42mResolved
Mar 30, 2026Codefresh CI Pipeline Runs Failing Due to Image Pull FailureThis incident has been resolved.10h 6mResolved
Feb 16, 2026Performance issues with the Codefresh platformThis 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.1h 15mResolved
Jan 23, 2026Scheduled Maintenance January 23rd 0600-1500 UTCThe scheduled maintenance has been completed.9h 0mScheduled
Dec 29, 2025Some accounts may experience issues with viewing the audit dataThis incident has been resolved.3h 40mResolved
Nov 18, 2025GitHub upstream outage impacting Classic Pipelines (and other GH dependent services)Github Git Operations is operating normally as of Nov 18, 2025 - 21:56 UTC40 minResolved
Nov 18, 2025codefresh.io is intermittently unreachable for some usersThis incident has been resolved.12h 35mResolved
Nov 5, 2025Free-tier Codefresh Classic users unable to run classic pipeline builds on SaaS.This incident has been resolved.59 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Codefresh incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Codefresh Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Codefresh acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Codefresh outage in this window ran 16d 3h, against a mean recovery of 1d 6h. If you depend on Codefresh in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.