Historial de interrupciones de Chef

1. June 24, 2026 at 4:49 PM UTCidentified

   Actualmente estamos experimentando un problema impactando el registro del usuario en el Supermercado. Nuestro equipo ha identificado el problema y está trabajando activamente para restaurar el servicio normal lo antes posible. En este momento, algunos usuarios pueden ser incapaces de iniciar sesión; sin embargo, las sesiones de inicio de sesión existentes seguirán funcionando. Comprendemos la molestia que esto puede causar y apreciar su paciencia mientras trabajamos en resolverlo. Seguiremos proporcionando actualizaciones a medida que se disponga de más información.

2. June 25, 2026 at 12:44 PM UTCresolved

   La cuestión que impacta el registro del usuario en el Supermercado ya se ha resuelto, y el servicio normal ha sido totalmente restaurado. Los usuarios deben ahora poder iniciar sesión sin ningún problema. Sinceramente nos disculpamos por la inconveniencia causada y apreciamos su paciencia mientras trabajamos para resolver este problema.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 16, 2026 at 6:18 AM UTCinvestigating

   We are currently facing some technical issue with supermarket and we are investigating on it.

2. June 16, 2026 at 9:41 AM UTCmonitoring

   Issue with supermarket is resolved. Currently monitoring the systems.

3. June 16, 2026 at 9:41 AM UTCmonitoring

   We are continuing to monitor for any further issues.

4. June 16, 2026 at 12:25 PM UTCresolved

   This incident has been resolved.

1. May 13, 2026 at 9:50 PM UTCinvestigating

   We are currently facing some technical issue with supermarket. We are on it and we will keep this page updated

2. May 13, 2026 at 10:09 PM UTCinvestigating

   We are continuing to investigate this issue.

3. May 13, 2026 at 11:37 PM UTCidentified

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

4. May 14, 2026 at 2:30 AM UTCmonitoring

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

5. May 14, 2026 at 10:33 AM UTCinvestigating

   The issue has re-surfaced and we are looking into it

6. May 14, 2026 at 3:06 PM UTCmonitoring

   The issue with supermarket is fixed and we are monitoring the results.

7. May 18, 2026 at 6:26 AM UTCresolved

   The issue with supermarket is resolved

1. February 17, 2026 at 6:08 PM UTCinvestigating

   There are currently reports coming in from users about degraded performance with our CDN in some regions. Users may encounter timeouts when downloading binaries using the Chef download API endpoints. Current Actions: We are actively working with Fastly to identify the root cause and resolve this issue. We will provide updates as more information becomes available.

2. February 18, 2026 at 5:41 PM UTCresolved

   The status has been resolved.

1. November 24, 2025 at 1:24 PM UTCresolved

   After 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.

1. May 22, 2025 at 6:22 PM UTCinvestigating

   We have an isolated incident with our habitat database and we are investigating the issue. We will update when we are back online. Please check our Slack channel for updates. https://chefcommunity.slack.com/archives/CAW6DQBV2

2. May 23, 2025 at 3:44 AM UTCresolved

   Issue is resolved, all Habitat service is functional now.

1. April 12, 2023 at 6:24 PM UTCresolved

   There was an incident with Hosted Chef today morning at 6:00AM UTC, the Hosted Chef application (manage.chef.io) was down for 15 mins. We identified the root cause and fixed the issue immediately. The systems are now healthy and up and running.

1. March 21, 2022 at 2:33 PM UTCinvestigating

   We have identified that sign in for supermarket is not working. We are currently investigating the issue and we will keep you posted

2. March 21, 2022 at 6:15 PM UTCresolved

   We have identified and fixed the issue, sign in is working as expected now. We will continue to monitor the system.

1. December 22, 2021 at 1:39 PM UTCinvestigating

   We are seeing increased Error rates in Hosted Chef , this seems to be because of an on going AWS network issue in us-east-1 region. Our Engineers are working on this and we will keep you posted.

2. December 22, 2021 at 3:27 PM UTCidentified

   We have identified our internal Search Service to be the problem and this is because of on-going AWS us-east-1 incident. Our Engineers are working to restore the service with normal performance.

3. December 22, 2021 at 11:06 PM UTCmonitoring

   The issue is fixed and both Hosted Chef Web console and Hosted Chef API are performing normally now. We will continue to monitor for a while.

4. December 22, 2021 at 11:18 PM UTCresolved

   This Incident is resolved and services are back to normal. Thanks for your patience.

1. August 31, 2021 at 7:00 PM UTCidentified

   We are experiencing network performance degradation due to a vendor.

2. August 31, 2021 at 9:36 PM UTCmonitoring

   We have implemented a workaround which should alleviate timeouts and error rates. We are continuing to monitor the upstream vendor outage.

3. August 31, 2021 at 9:46 PM UTCmonitoring

   Error rates have improved for package distribution infrastructure. We will continue to monitor the upstream outage.

4. August 31, 2021 at 11:36 PM UTCresolved

   Vendor has resolved their incident.

1. June 23, 2021 at 7:58 PM UTCinvestigating

   We are facing issues with our Package Distribution Infrastructure. We are Working on identifying the issue and a resolution.

2. June 23, 2021 at 8:26 PM UTCresolved

   This incident has been resolved.

1. April 21, 2021 at 5:57 PM UTCidentified

   We are facing increased 5xx Error rate on Hosted Chef. We have identified the problem and are working to resolve the issue. We will keep you updated.

2. April 21, 2021 at 8:14 PM UTCidentified

   We have not been able to fix the issue yet and are continuing our work to resolve the issue. Thanks for being patient.

3. April 21, 2021 at 10:20 PM UTCresolved

   We have fixed the issue and Error rate is close to 0. We will continue to monitor for a while. Thank you for your patience.

1. March 11, 2021 at 6:09 AM UTCinvestigating

   We are currently investigating increased error rate in Hosted Chef. We will keep you posted.

2. March 11, 2021 at 7:32 AM UTCresolved

   The issue has been resolved. We were facing error with our indexing cluster and that lead to increased 5xx for the API calls.

1. July 2, 2020 at 12:22 PM UTCinvestigating

   We are investigating an issue with Hosted Chef - Manage UI functionality. Please note this does not affect the Hosted Chef API and Knife functionality is still available.

2. July 2, 2020 at 3:46 PM UTCresolved

   We have deployed a previous release of Manage to Hosted Chef to fix the UI bug until we can fix it in the latest version of manage.

1. April 16, 2020 at 11:06 PM UTCinvestigating

   After upgrading PostgreSQL we are seeing database connections and CPU spikes. We're resizing the database to get more system resources and will provide additional updates as we have them.

2. April 17, 2020 at 12:00 AM UTCinvestigating

   We're investigating an unexpected elevation in fetches by the authz service from the database.

3. April 17, 2020 at 1:58 AM UTCinvestigating

   We're isolating the issue with authz service's database queries that is taking an abnormally long time to complete.

4. April 17, 2020 at 2:13 AM UTCinvestigating

   We've implemented a short term workaround to restore service. We're monitoring the service.

5. April 17, 2020 at 2:24 AM UTCinvestigating

   Traffic patterns and service have normalized to regular levels observed prior to the maintenance window. We will conduct an incident analysis and write up a blog post for this next week. Thank you for your patience and I'm sorry that this impacted your workflows.

6. April 17, 2020 at 2:37 AM UTCresolved

   This incident has been resolved.

1. February 6, 2020 at 3:36 PM UTCinvestigating

   We are investigating increased error rates and timeouts with supermarket.chef.io

2. February 6, 2020 at 5:56 PM UTCinvestigating

   We're investigating what is causing the load balancer to remove hosts sporadically.

3. February 6, 2020 at 9:26 PM UTCinvestigating

   The load balancers removing hosts sporadically was a symptom. We're continuing to investigate what appears to be regularly occuring spikes in cache gets at the :00 and :30 minute marks each hour.

4. February 6, 2020 at 10:04 PM UTCmonitoring

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

5. February 6, 2020 at 11:21 PM UTCresolved

   This incident has been resolved.

1. January 10, 2020 at 1:12 AM UTCinvestigating

   We are investigating increased error rates for Hosted Chef services

2. January 10, 2020 at 1:16 AM UTCmonitoring

   Backend services have stabilized, engineers are monitoring

3. January 10, 2020 at 2:53 AM UTCresolved

   This incident has been resolved.

1. December 10, 2019 at 5:01 PM UTCinvestigating

   We are investigating problems in the Hosted Chef backend. Unfortunately, we expect chef-client communications to be severely impacted at this time. We will post further info regularly, as we find it.

2. December 10, 2019 at 5:11 PM UTCmonitoring

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

3. December 10, 2019 at 5:28 PM UTCresolved

   This incident has been resolved.

1. October 11, 2019 at 4:16 PM UTCresolved

   https://omnitruck.chef.io/install.sh serves up bootstrap scripts for use by unattended installs like autoscaling and `knife bootstrap ...` initiated bootstraps. We have become aware of an omnitruck.chef.io issue affecting downloads of the bootstrap install script from opscode.com/chef/install.sh as well. Please upgrade if running older chef-client/knife code that would point at opscode.com We expect the issue to have been cleared at 2019-10-11 8am Pacific US

1. September 19, 2019 at 5:12 PM UTCinvestigating

   Please note that some customers may be experiencing a disruption to their Chef services. We are actively investigating this issue and working on a resolution. We apologize for the disruption and will regularly update this page with a status and resolution timeline.

2. September 19, 2019 at 7:48 PM UTCidentified

   We have isolated the issue to be failures in Chef client runs whose cookbooks rely on libraries which are not currently available. Mirrors that sync these libraries will also encounter issues. These issues do not impact customer data, privacy or data integrity. We are working to resolve these issues ASAP and will provide a further update shortly.

3. September 19, 2019 at 8:51 PM UTCidentified

   We will shortly have remediation steps for repairing environments affected by this issue.

4. September 20, 2019 at 1:08 AM UTCmonitoring

   We have identified a fix and released new versions of relevant cookbooks and libraries. Remediation steps will be shared to customers via our customer success teams.

5. September 20, 2019 at 4:09 PM UTCresolved

   We've received independent verification from customers that remediation steps have resolved the issue for their use case(s) and are calling this incident resolved. Please reach out to Chef Support if you experience further problems. The affected gems (chef-sugar, chef-api, stove) have been restored to the rubygems.org site under their original namespaces.