What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with Snowflake now? Check the current statusAffected services
Updates (7)
- May 13, 2026, 12:16 AMAzure - West US 2 (Washington): INC0156645
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/INC0156645](https://community.snowflake.com/s/article/INC0156645)
Snowflake ↗ - May 5, 2026, 12:30 PMAzure - West US 2 (Washington): INC0156645
<b>Current status:</b> We've implemented the fix for this issue and 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. <b>Customer experience:</b> Customers hosted in the specified region may have observed stale or delayed data in account usage views and organization usage views. <b>Incident start time:</b> 12:03 UTC May 04, 2026 <b>Incident end time:</b> 08:54 UTC May 05, 2026 <b>Preliminary root cause:</b> We identified an issue affectin
Snowflake ↗ - May 5, 2026, 11:30 AMAzure - West US 2 (Washington): INC0156645
<b>Current status:</b> We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. <b>Customer experience:</b> Customers hosted in the specified region may have observed stale or delayed data in account usage views and organization usage views. <b>Incident start time:</b> 12:03 UTC May 04, 2026 <b>Incident end time:</b> 08:54 UTC May 05, 2026 <b>Preliminary root cause:</b> We identified an issue affecting a small number of internal metering files in this region. When Snowflake attempted to read these f
Snowflake ↗ - May 5, 2026, 09:27 AMAzure - West US 2 (Washington): INC0156645
<b>Current status:</b> We've identified an issue affecting a subset of internal metering files, causing a delay in account usage updates. We have now completed changes to exclude those files, allowing processes to resume. Data freshness in this region is now improving as the processing backfill catches up. We are validating the remaining backlog and any required backfill before marking full recovery. We'll provide another update within two hours. <b>Customer experience:</b> Customers hosted in the specified region may observe stale or delayed data in account usage views and organization usage
Snowflake ↗ - May 5, 2026, 07:09 AMAzure - West US 2 (Washington): INC0156645
<b>Current status:</b> We've identified an issue affecting a subset of data files, which is resulting in a delay for account usage updates. We are preparing changes to safely exclude the affected files and allow processing to resume. Account Usage data in the affected region remains delayed while we finalize validation of the impacted files and complete recovery steps. We’ll provide another update within four hours. <b>Customer experience:</b> Customers hosted in the specified region may observe stale or delayed data in account usage views and organization usage views. Usage reporting may not
Snowflake ↗ - May 5, 2026, 05:10 AMAzure - West US 2 (Washington): INC0156645
<b>Current status:</b> We've identified an issue affecting a subset of data files, which is resulting in a delay for account usage updates. We're working on identifying a mitigation to restore normal processing. We'll provide another update within two hours. <b>Customer experience:</b> Customers hosted in the specified region may observe stale or delayed data in account usage views and organization usage views. Usage reporting may not reflect activity after 16:00 UTC on May 4, 2026. <b>Workaround:</b> There are currently no available workarounds for this issue. <b>Incident start time:</b> 1
Snowflake ↗ - May 5, 2026, 04:12 AMAzure - West US 2 (Washington): INC0156645
<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified region may observe stale or delayed data in account usage views and organization usage views. Usage reporting may not reflect activity after 16:00 UTC on May 4, 2026. <b>Workaround:</b> There are currently no available workarounds for this issue. <b>Incident start time:</b> 16:50 UTC May 04, 2026
Snowflake ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow Snowflake's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.