INC0140464
Incident
Report for Snowflake
Postmortem
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/INC0140464
Resolved
Current status: We've monitored the environment and confirmed the service is restored. If you experience additional issues or have questions, please open a support case via Snowflake Community.
Customer experience: Customers hosted in the specified regions may observe delayed or stale data for the ACCOUNT_USAGE.SESSIONS view.
Incident start time: 01:50 UTC August 05, 2025
Incident end time: 10:30 UTC August 09, 2025
Preliminary root cause: A recent data exporting change for the ACCOUNT_USAGE.SESSIONS view inadvertently led to a processing backlog and subsequent delays or stale data.
A root cause analysis (RCA) document will be published within seven business days.
Customer experience: Customers hosted in the specified regions may observe delayed or stale data for the ACCOUNT_USAGE.SESSIONS view.
Incident start time: 01:50 UTC August 05, 2025
Incident end time: 10:30 UTC August 09, 2025
Preliminary root cause: A recent data exporting change for the ACCOUNT_USAGE.SESSIONS view inadvertently led to a processing backlog and subsequent delays or stale data.
A root cause analysis (RCA) document will be published within seven business days.
Monitoring
Current status: The backlog has been processed, and customers should now be experiencing issue resolution. We'll continue to monitor the environment until we're confident all services are functioning properly.
Customer experience: Customers hosted in the specified regions may observe delayed or stale data for the ACCOUNT_USAGE.SESSIONS view.
Incident start time: 01:50 UTC August 05, 2025
Incident end time: 10:30 UTC August 09, 2025
Preliminary root cause: A recent data exporting change for the ACCOUNT_USAGE.SESSIONS view inadvertently led to a processing backlog and subsequent delays or stale data.
Customer experience: Customers hosted in the specified regions may observe delayed or stale data for the ACCOUNT_USAGE.SESSIONS view.
Incident start time: 01:50 UTC August 05, 2025
Incident end time: 10:30 UTC August 09, 2025
Preliminary root cause: A recent data exporting change for the ACCOUNT_USAGE.SESSIONS view inadvertently led to a processing backlog and subsequent delays or stale data.
Update
Current status: The backlog is taking an extended amount of time to process, and as such, we are amending our previous estimated time of resolution. While two of the affected regions have been completed, we anticipate that the remaining regions may require up to an additional 12-24 hours to complete.
Customer experience: Customers hosted in the specified regions may observe delayed or stale data for the ACCOUNT_USAGE.SESSIONS view.
ETA: We expect the issue will be fully resolved by 20:00 UTC on August 9, 2025. Customers may experience restoration earlier depending on when the backlog is processed and cleared across different affected regions.
Preliminary root cause: A recent data exporting change for the ACCOUNT_USAGE.SESSIONS view inadvertently led to a processing backlog and subsequent delays or stale data.
Incident start time: 01:50 UTC August 05, 2025
Customer experience: Customers hosted in the specified regions may observe delayed or stale data for the ACCOUNT_USAGE.SESSIONS view.
ETA: We expect the issue will be fully resolved by 20:00 UTC on August 9, 2025. Customers may experience restoration earlier depending on when the backlog is processed and cleared across different affected regions.
Preliminary root cause: A recent data exporting change for the ACCOUNT_USAGE.SESSIONS view inadvertently led to a processing backlog and subsequent delays or stale data.
Incident start time: 01:50 UTC August 05, 2025
Identified
Current status: We're investigating a recent issue that resulted in delays or stale data for the ACCOUNT_USAGE.SESSIONS view. We've identified a recent change that inadvertently led to a processing backlog. We reverted the change to resolve the issue; however, we anticipate it may require up to 24 hours for the backlog to be fully processed.
Customer experience: Customers hosted in the specified regions may observe delayed or stale data for the ACCOUNT_USAGE.SESSIONS view.
ETA: We expect the issue will be fully resolved by 20:00 UTC on August 8, 2025. Customers may experience restoration earlier depending on when the backlog is processed and cleared across different affected regions.
Preliminary root cause: A recent data exporting change for the ACCOUNT_USAGE.SESSIONS view inadvertently led to a processing backlog and subsequent delays or stale data.
Incident start time: 01:50 UTC August 05, 2025
Customer experience: Customers hosted in the specified regions may observe delayed or stale data for the ACCOUNT_USAGE.SESSIONS view.
ETA: We expect the issue will be fully resolved by 20:00 UTC on August 8, 2025. Customers may experience restoration earlier depending on when the backlog is processed and cleared across different affected regions.
Preliminary root cause: A recent data exporting change for the ACCOUNT_USAGE.SESSIONS view inadvertently led to a processing backlog and subsequent delays or stale data.
Incident start time: 01:50 UTC August 05, 2025
This incident affected: AWS - US West (Oregon) (Organization and Account Management), AWS - US East (N. Virginia) (Organization and Account Management), and Azure - East US 2 (Virginia) (Organization and Account Management).