Störungsverlauf von Chef

1. 24. Juni 2026 um 16:49 UTCidentified

   Wir haben derzeit ein Problem, das sich auf die Anmeldung zum Supermarkt auswirkt. Unser Team hat das Problem erkannt und arbeitet aktiv daran, den normalen Service so schnell wie möglich wiederherzustellen. Zu diesem Zeitpunkt können sich einige Benutzer möglicherweise nicht anmelden; bestehende Anmeldesitzungen funktionieren jedoch weiterhin. Wir verstehen die Unannehmlichkeiten, die dies verursachen kann, und schätzen Ihre Geduld, während wir daran arbeiten, sie zu lösen. Wir werden weiterhin Updates bereitstellen, sobald mehr Informationen verfügbar sind.

2. 25. Juni 2026 um 12:44 UTCresolved

   Das Problem, das sich auf die Anmeldung zum Supermarkt auswirkt, wurde nun behoben und der normale Service wurde vollständig wiederhergestellt. Benutzer sollten sich jetzt ohne Probleme anmelden können. Wir entschuldigen uns aufrichtig für die Unannehmlichkeiten und schätzen Ihre Geduld, während wir daran gearbeitet haben, dieses Problem zu lösen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Juni 2026 um 06:18 UTCinvestigating

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

2. 16. Juni 2026 um 09:41 UTCmonitoring

   Issue with supermarket is resolved. Currently monitoring the systems.

3. 16. Juni 2026 um 09:41 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 16. Juni 2026 um 12:25 UTCresolved

   This incident has been resolved.

1. 13. Mai 2026 um 21:50 UTCinvestigating

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

2. 13. Mai 2026 um 22:09 UTCinvestigating

   We are continuing to investigate this issue.

3. 13. Mai 2026 um 23:37 UTCidentified

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

4. 14. Mai 2026 um 02:30 UTCmonitoring

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

5. 14. Mai 2026 um 10:33 UTCinvestigating

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

6. 14. Mai 2026 um 15:06 UTCmonitoring

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

7. 18. Mai 2026 um 06:26 UTCresolved

   The issue with supermarket is resolved

1. 17. Februar 2026 um 18:08 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. 18. Februar 2026 um 17:41 UTCresolved

   The status has been resolved.

1. 24. November 2025 um 13:24 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. 22. Mai 2025 um 18:22 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. 23. Mai 2025 um 03:44 UTCresolved

   Issue is resolved, all Habitat service is functional now.

1. 12. April 2023 um 18:24 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. 21. März 2022 um 14:33 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. 21. März 2022 um 18:15 UTCresolved

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

1. 22. Dezember 2021 um 13:39 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. 22. Dezember 2021 um 15:27 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. 22. Dezember 2021 um 23:06 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. 22. Dezember 2021 um 23:18 UTCresolved

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

1. 31. August 2021 um 19:00 UTCidentified

   We are experiencing network performance degradation due to a vendor.

2. 31. August 2021 um 21:36 UTCmonitoring

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

3. 31. August 2021 um 21:46 UTCmonitoring

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

4. 31. August 2021 um 23:36 UTCresolved

   Vendor has resolved their incident.

1. 23. Juni 2021 um 19:58 UTCinvestigating

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

2. 23. Juni 2021 um 20:26 UTCresolved

   This incident has been resolved.

1. 21. April 2021 um 17:57 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. 21. April 2021 um 20:14 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. 21. April 2021 um 22:20 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. 11. März 2021 um 06:09 UTCinvestigating

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

2. 11. März 2021 um 07:32 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. 2. Juli 2020 um 12:22 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. 2. Juli 2020 um 15:46 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. 16. April 2020 um 23:06 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. 17. April 2020 um 00:00 UTCinvestigating

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

3. 17. April 2020 um 01:58 UTCinvestigating

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

4. 17. April 2020 um 02:13 UTCinvestigating

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

5. 17. April 2020 um 02:24 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. 17. April 2020 um 02:37 UTCresolved

   This incident has been resolved.

1. 6. Februar 2020 um 15:36 UTCinvestigating

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

2. 6. Februar 2020 um 17:56 UTCinvestigating

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

3. 6. Februar 2020 um 21:26 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. 6. Februar 2020 um 22:04 UTCmonitoring

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

5. 6. Februar 2020 um 23:21 UTCresolved

   This incident has been resolved.

1. 10. Januar 2020 um 01:12 UTCinvestigating

   We are investigating increased error rates for Hosted Chef services

2. 10. Januar 2020 um 01:16 UTCmonitoring

   Backend services have stabilized, engineers are monitoring

3. 10. Januar 2020 um 02:53 UTCresolved

   This incident has been resolved.

1. 10. Dezember 2019 um 17:01 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. 10. Dezember 2019 um 17:11 UTCmonitoring

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

3. 10. Dezember 2019 um 17:28 UTCresolved

   This incident has been resolved.

1. 11. Oktober 2019 um 16:16 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. 19. September 2019 um 17:12 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. 19. September 2019 um 19:48 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. 19. September 2019 um 20:51 UTCidentified

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

4. 20. September 2019 um 01:08 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. 20. September 2019 um 16:09 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.