GlobalOutageMap
← Live dashboard
Snowflake

INC0157230

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update May 15, 2026, 04:01 AM · Resolved May 15, 2026, 05:25 AM

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/INC0157230](https://community.snowflake.com/s/article/INC0157230)

Snowflake live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Snowflake now? Check the current status

Affected services

AI and ML

Updates (4)

  1. May 22, 2026, 12:26 AM
    INC0157230

    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/INC0157230](https://community.snowflake.com/s/article/INC0157230)

    Snowflake ↗
  2. May 15, 2026, 05:25 AM
    INC0157230

    <b>Current status:</b> We've monitored the environment and confirmed the rollback restored service. 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 regions may have experienced Cortex Code in Snowsight stopping mid-response after completing only one step of a request. The response may have stopped without an error message or may have repeated without progressing. <b>Incident start time:</b> 22:50 UTC May 14, 2026 <b>Incident end time:</b> 0

    Snowflake ↗
  3. May 15, 2026, 04:34 AM
    INC0157230

    <b>Current status:</b> We've identified and rolled back a Cortex Code update to resolve this issue. 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 regions may have experienced Cortex Code in Snowsight stopping mid-response after completing only one step of a request. The response may have stopped without an error message or may have repeated without progressing. <b>Incident start time:</b> 22:50 UTC May 14, 2026 <b>Incident end time:</b> 04:05 UTC May 15, 2026 <b>Preliminary

    Snowflake ↗
  4. May 15, 2026, 04:01 AM
    INC0157230

    <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 regions may experience Cortex Code in Snowsight stopping mid-response after completing only one step of a request. The response may stop without an error message or may repeat without progressing.

    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.