Snowflake: AWS - Asia Pacific (Tokyo): INC0106687
Timeline of updates
- resolved
Current status: Our investigation determined that this issue was transient in nature and impacted a localized subset of internal users. Customer experience: There were no customer impacts as the detected issue was only to an internal Snowflake Service not utilized by customers. Incident start time: 19:55 UTC April 17, 2024 Incident end time: 21:46 UTC April 17, 2024 Preliminary root cause: Snowflake Engineering investigated a spike in telemetry data that was initially suspected to be affecting customers in the specified regions using Streamlit. Upon thorough investigation, the issue was found to be with an internal account that produced errors that elevated awareness. We have confirmed that there were no customer impacts resulting from this issue.
From Snowflake’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.snowflake.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Snowflake, started 2024-04-17 21:01 UTC, resolved after 2.0 h, 1 update(s).
- Title
- AWS - Asia Pacific (Tokyo): INC0106687
- Vendor
- Snowflake
- Date
- URL
- https://rewindex.com/company/snowflake/incidents/1zd9g3nlpy1j
Snowflake profileRecent Snowflake incidentsAll outages on April 17, 2024Snowflake in April 2024MarkdownJSON