해결됨 · 3시간 지속

8월 31일 Snowflake 장애

Snowflake 제보가 시간당 322건까지 급증했고 3시간 동안 높게 유지됐어요.

시작
오후 4:00
2026년 8월 31일 · UTC
정상 복구
오후 7:00
3시간 후
최고치
시간당 322
평소의 322×
Snowflake 인시던트
2시간 24분
INC20000188

장애 중 제보

오후 2:00오후 8:50 UTC

Snowflake의 발표 내용

status.snowflake.com
해결됨오후 5:20~7:44 · 2시간 24분

INC20000188

  1. 해결됨 · 오후 5:27

    Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000188](https://community.snowflake.com/s/article/INC20000188)

  2. 해결됨 · 오후 7:44

    Current status: We've monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have been unable to access or use multiple core Snowflake services and features, including signing in to Snowsight, executing queries, loading and unloading data, and using Snowpark Container Services. Some customers may have also experienced delays with Snowpipe Streaming ingestion and elevated error rates when accessing Snowsight. The majority of impact was resolved at 17:25 UTC; however, some customers may have continued to experience some residual errors or increased latency until approximately 18:10 UTC. Incident start time: 16:58 UTC August 31, 2026 Incident end time: 18:10 UTC August 31, 2026 Preliminary root cause: A recent configuration change degraded backend processing due to a compatibility issue with how the affected systems handled requests. As a result, the infrastructure experienced resource contention and subsequent impact to multiple Snowflake services and features. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

  3. 모니터링 중 · 오후 6:45

    Current status: We've implemented a fix to address the residual impact, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified region may have been unable to access or use multiple core Snowflake services and features, including signing in to Snowsight, executing queries, loading and unloading data, and using Snowpark Container Services. Some customers may have also experienced delays with Snowpipe Streaming ingestion and elevated error rates when accessing Snowsight. The majority of impact was resolved at 17:25 UTC; however, some customers may have continued to experience some residual errors or increased latency until approximately 18:10 UTC. Incident start time: 16:58 UTC August 31, 2026 Incident end time: 18:10 UTC August 31, 2026 Preliminary root cause: A recent change on the affected infrastructure inadvertently resulted in an increase in resource contention and subsequent impact to multiple Snowflake services and features.

  4. 확인됨 · 오후 5:59

    Current status: We are continuing to monitor service recovery, and have confirmed that the majority of service impact has been resolved as of 17:25 UTC with some residual impact to Snowsight access and Snowpipe Streaming. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: Most services have returned to a healthy state. We expect any residual impact to Snowsight access and Snowpipe Streaming to be resolved within the next hour. Incident start time: 16:58 UTC August 31, 2026

  5. 확인됨 · 오후 5:31

    Current status: We identified and have since reverted a problematic change as a potential mitigation. Initial telemetry indicates that the service is recovering. We will continue to monitor to confirm recovery. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: Customers should be starting to see recovery, and our current estimate is that service will be restored within 1 hour.

  6. 조사 중 · 오후 5:20

    Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.

Snowflake은(는) 제보가 늘기 시작한 지 1시간 20분 후에 첫 업데이트를 올렸어요.

Snowflake 지금 다운되었나요?

실시간 상태, 오늘의 제보, 다른 이전 장애.

Snowflake 현재 상태 →