Chef 장애 기록

1. 2026년 6월 24일 PM 4:49 UTCidentified

   우리는 현재 슈퍼마켓에 사용자 기호에 영향을 미치는 문제점을 경험하고 있습니다. 우리의 팀은 문제를 확인하고 가능한 한 빨리 정상적인 서비스를 복원하기 위해 적극적으로 노력하고 있습니다. 이 때, 일부 사용자는 로그인 할 수 없습니다. 그러나 기존 로그인 세션은 계속 작용합니다. 우리는이 불편을 겪고 우리가 해결하는 동안 당신의 인내력을 평가 할 수 있습니다. 더 많은 정보로 업데이트를 계속 제공 할 것입니다.

2. 2026년 6월 25일 PM 12:44 UTCresolved

   슈퍼마켓에 대한 사용자 기호에 영향을 미치는 문제는 이제 해결되었습니다. 정상적인 서비스는 완전히 복원되었습니다. 사용자는 이제 모든 문제없이 로그인 할 수 있어야합니다. 우리는 우리가이 문제를 해결하기 위해 일하면서 인 불편에 대해 진심으로 사과합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 16일 AM 6:18 UTCinvestigating

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

2. 2026년 6월 16일 AM 9:41 UTCmonitoring

   Issue with supermarket is resolved. Currently monitoring the systems.

3. 2026년 6월 16일 AM 9:41 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2026년 6월 16일 PM 12:25 UTCresolved

   This incident has been resolved.

1. 2026년 5월 13일 PM 9:50 UTCinvestigating

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

2. 2026년 5월 13일 PM 10:09 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 5월 13일 PM 11:37 UTCidentified

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

4. 2026년 5월 14일 AM 2:30 UTCmonitoring

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

5. 2026년 5월 14일 AM 10:33 UTCinvestigating

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

6. 2026년 5월 14일 PM 3:06 UTCmonitoring

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

7. 2026년 5월 18일 AM 6:26 UTCresolved

   The issue with supermarket is resolved

1. 2026년 2월 17일 PM 6: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. 2026년 2월 18일 PM 5:41 UTCresolved

   The status has been resolved.

1. 2025년 11월 24일 PM 1: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. 2025년 5월 22일 PM 6: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. 2025년 5월 23일 AM 3:44 UTCresolved

   Issue is resolved, all Habitat service is functional now.

1. 2023년 4월 12일 PM 6: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. 2022년 3월 21일 PM 2: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. 2022년 3월 21일 PM 6:15 UTCresolved

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

1. 2021년 12월 22일 PM 1: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. 2021년 12월 22일 PM 3: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. 2021년 12월 22일 PM 11: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. 2021년 12월 22일 PM 11:18 UTCresolved

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

1. 2021년 8월 31일 PM 7:00 UTCidentified

   We are experiencing network performance degradation due to a vendor.

2. 2021년 8월 31일 PM 9:36 UTCmonitoring

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

3. 2021년 8월 31일 PM 9:46 UTCmonitoring

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

4. 2021년 8월 31일 PM 11:36 UTCresolved

   Vendor has resolved their incident.

1. 2021년 6월 23일 PM 7:58 UTCinvestigating

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

2. 2021년 6월 23일 PM 8:26 UTCresolved

   This incident has been resolved.

1. 2021년 4월 21일 PM 5: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. 2021년 4월 21일 PM 8: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. 2021년 4월 21일 PM 10: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. 2021년 3월 11일 AM 6:09 UTCinvestigating

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

2. 2021년 3월 11일 AM 7: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. 2020년 7월 2일 PM 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. 2020년 7월 2일 PM 3: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. 2020년 4월 16일 PM 11: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. 2020년 4월 17일 AM 12:00 UTCinvestigating

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

3. 2020년 4월 17일 AM 1:58 UTCinvestigating

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

4. 2020년 4월 17일 AM 2:13 UTCinvestigating

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

5. 2020년 4월 17일 AM 2: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. 2020년 4월 17일 AM 2:37 UTCresolved

   This incident has been resolved.

1. 2020년 2월 6일 PM 3:36 UTCinvestigating

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

2. 2020년 2월 6일 PM 5:56 UTCinvestigating

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

3. 2020년 2월 6일 PM 9: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. 2020년 2월 6일 PM 10:04 UTCmonitoring

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

5. 2020년 2월 6일 PM 11:21 UTCresolved

   This incident has been resolved.

1. 2020년 1월 10일 AM 1:12 UTCinvestigating

   We are investigating increased error rates for Hosted Chef services

2. 2020년 1월 10일 AM 1:16 UTCmonitoring

   Backend services have stabilized, engineers are monitoring

3. 2020년 1월 10일 AM 2:53 UTCresolved

   This incident has been resolved.

1. 2019년 12월 10일 PM 5: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. 2019년 12월 10일 PM 5:11 UTCmonitoring

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

3. 2019년 12월 10일 PM 5:28 UTCresolved

   This incident has been resolved.

1. 2019년 10월 11일 PM 4: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. 2019년 9월 19일 PM 5: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. 2019년 9월 19일 PM 7: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. 2019년 9월 19일 PM 8:51 UTCidentified

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

4. 2019년 9월 20일 AM 1: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. 2019년 9월 20일 PM 4: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.