Minor impactResolvedDatabases

Snowflake incident: INC0157230

Snowflake reported this minor-impact incident on its official status page on May 15, 2026, 04:01 UTC. It was resolved after 1h 24m.

Right now Snowflake is degraded. Live Snowflake status →

🔔 Get alerted when Snowflake has issuesFree · email alerts · no credit card
May 15, 2026, 04:01 UTC
started
May 15, 2026, 05:25 UTC
resolved
1h 24m
duration
Minor
impact

Affected components

  • AI and ML
  1. postmortemMay 22, 2026, 00:26 UTC

    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)

  2. resolvedMay 15, 2026, 05:25 UTC

    <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> 04:05 UTC May 15, 2026 <b>Preliminary root cause:</b> A recent update to Cortex Code introduced a code issue that caused Cortex Code in Snowsight to incorrectly halt responses, preventing requests from completing. A root cause analysis (RCA) document will be published within five business days.

  3. monitoringMay 15, 2026, 04:34 UTC

    <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 root cause:</b> A recent update to Cortex Code introduced a code issue that caused Cortex Code in Snowsight to incorrectly halt responses, preventing requests from completing.

  4. investigatingMay 15, 2026, 04:01 UTC

    <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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Snowflake's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Snowflake have incidents?

Snowflake reported 23 incidents in the last 90 days, 18 of them major or critical. A typical incident lasted 1h 56m. See Snowflake's uptime and incident history

Snowflake incident on May 15, 2026: INC0157230 · APIStatus.watch