Skip to content
Snowflake · Data and observabilityJan 27, 2026, 18:13 UTC

Azure - Central US (Iowa): INC0150687

CriticalDatabaseUpdated 20h ago
Jan 27, 18:13 UTCJan 27, 19:30 UTC
Duration
1h 17m
Impact
Critical
Root cause
Database
Snowflake, 90 days
22 incidents
Affected
Databases, Tables, and ViewsData Loading and UnloadingAzure - Central US (Iowa) - Databases, Tables, and ViewsAzure - Central US (Iowa) - Data Loading and Unloading
Status page

Final update

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

Timeline

  1. Postmortem · Feb 4, 01:34 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/INC0150687](https://community.snowflake.com/s/article/INC0150687)
  2. Resolved · Jan 27, 19:30 UTC
    Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. 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 regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Additionally, they may have been unable to continuously stream data into Snowflake using Snowpipe Streaming, or ingest data using Snowpipe, and may have been unable to execute queries, retrieve results, or manage data objects such as tables and views. Incident start time: 17:51 UTC January 27, 2026 Incident end time: 18:25 UTC January 27, 2026 Preliminary root cause: A recent change to our service infrastructure experienced an incompatibility issue on a subset of instances in the metadata database layer, causing requests to fail. A root cause analysis (RCA) document will be published within five business days.
  3. Monitoring · Jan 27, 19:02 UTC
    Current status: We've identified a recent change to our service infrastructure that resulted in impact. We've reverted this change to remediate the issue, and we've observed that the issue has been resolved. 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 have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Additionally, they may have been unable to continuously stream data into Snowflake using Snowpipe Streaming, or ingest data using Snowpipe, and may have been unable to execute queries, retrieve results, or manage data objects such as tables and views. Incident start time: 17:51 UTC January 27, 2026 Incident end time: 18:25 UTC January 27, 2026 Preliminary root cause: A recent change to our service infrastructure experienced an incompatibility issue on a subset of instances in the metadata database layer, causing requests to fail.
  4. Investigating · Jan 27, 18:13 UTC
    Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. Additionally, they may be unable to continuously stream data into Snowflake using Snowpipe Streaming, and may be unable to execute queries, retrieve results, or manage data objects such as tables and views.

More from Snowflake

Full history
StartedIncidentDuration
Sep 1404:48 UTCINC200002171h 21m
Sep 1107:18 UTCINC200002136h 1m
Sep 921:53 UTCINC200002111h 58m
Sep 407:34 UTCINC200001992h 36m
Sep 109:58 UTCINC200001903h 52m
Aug 3117:20 UTCINC200001882h 24m

Also caused by database

All
StartedIncidentDuration
Sep 1309:16 UTCIncident with several GitHub ServicesGitHub1h 29m
Aug 2616:17 UTCIssues performance is degraded in the USSentry4h 19m
Aug 1216:16 UTCIncident with Pull Requests and IssuesGitHub25m
Aug 818:57 UTCAccount Registration, Droplets, and Related ServicesDigitalOcean6h 3m
Jul 2817:41 UTCEvent ingestion and retrieval delays for some North America customersHubSpot2h
Jul 2419:37 UTCIncident with Pull RequestsGitHub46m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.