← Live dashboard

INC20000046

ResolvedmajorOfficial source confirmedSpecific component onlyFirst recorded update Jun 23, 2026, 01:05 AM · Resolved Jun 23, 2026, 02:35 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/INC20000046](https://community.snowflake.com/s/article/INC20000046)

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

ApplicationsSnowpark Container Services

Updates (4)

  1. Jul 2, 2026, 09:47 PM
    INC20000046

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

    Snowflake ↗
  2. Jun 23, 2026, 02:35 AM
    INC20000046

    Current status: We've monitored the environment to confirm that reverting the configuration change restored service. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have been unable to access Snowpark Container Services, and may have intermittently been unable to sign in to Snowsight. Affected users may have seen HTTP 500 errors. Workaround: There were no available workarounds for this issue. Incident start time: 22:38 UTC June 22, 202

    Snowflake ↗
  3. Jun 23, 2026, 01:43 AM
    INC20000046

    Current status: We identified and reverted a recent configuration change to resolve the impact. We'll continue to monitor the environment until we're confident all services are functioning properly. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may have been unable to access Snowpark Container Services, and may have intermittently been unable to sign in to Snowsight. Affected users may have seen HTTP 500 errors. Workaround: There were no available workarounds for this issue. Incident start time: 22:38 UTC June 22, 2026 Incident

    Snowflake ↗
  4. Jun 23, 2026, 01:05 AM
    INC20000046

    Current status: We're investigating an issue with Snowpark Container Services and Snowsight. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified region may be unable to access Snowpark Container Services, and may intermittently be unable to sign in to Snowsight. Affected users may see HTTP 500 errors. Incident start time: 22:38 UTC June 22, 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.