Chef Outage History
12 incidents recorded over the last 365 days, 6 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.
Every Recorded Chef Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 15, 2026 | Chef 360 Partial Service DisruptionThe issue affecting Chef 360 services has been resolved, and normal service has been restored. We apologise for any inconvenience caused and appreciate your patience while our teams worked to resolve the issue. | 4h 28m | Resolved |
| Aug 12, 2026 | packages.chef.io - maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jul 20, 2026 | Infra UpgradeThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jun 24, 2026 | Supermarket - Issue with sign-inThe issue impacting user sign‑in to the Supermarket has now been resolved, and normal service has been fully restored. Users should now be able to log in without any issues. We sincerely apologise for the inconvenience… | 19h 55m | Resolved |
| Jun 16, 2026 | Issue with supermarketThis incident has been resolved. | 6h 7m | Resolved |
| May 13, 2026 | Issue with supermarketThe issue with supermarket is resolved | 104h 35m | Resolved |
| Mar 18, 2026 | packages.chef.io - maintenanceThe scheduled maintenance has been completed. | 1h 30m | Scheduled |
| Mar 16, 2026 | Infra UpgradeThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Feb 17, 2026 | CDN PerformanceThe status has been resolved. | 23h 32m | Resolved |
| Nov 26, 2025 | Habitat Builder MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Nov 24, 2025 | Issue with our download enpodintsAfter our maintenance window today, we experienced issues with our download endpoint due to an underlying infrastructure problem. The team has resolved the issue. We apologize for any inconvenience caused. | 0 min | Resolved |
| Nov 24, 2025 | Infra UpgradeThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
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 Chef 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 Chef 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 Chef 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 Chef outage in this window ran 4d 8h, against a mean recovery of 13h 46m. If you depend on Chef 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.