[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":-5,"_6":7},"actionData","errors","root","routes/status-provider-incidents",{"_8":9,"_10":11,"_12":13},"provider",{"_37":78,"_21":79,"_23":80,"_81":82,"_83":84,"_85":86,"_87":88,"_89":90,"_17":-5,"_91":92,"_93":18,"_94":95,"_96":97},"history",{"_14":15,"_16":-5,"_17":18},"cursor","yKrqoQlyyqg6","incidents",[19,20],"nextCursor","sourceFetchedAt","2026-11-13T09:14:11.204Z",{"_21":60,"_23":24,"_25":26,"_27":61,"_29":62,"_31":63,"_33":64,"_35":65,"_37":66,"_39":40},{"_21":22,"_23":24,"_25":26,"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":38,"_39":40},"name","AWS - US West (Oregon): INC0150440","status","POSTMORTEM","impact","CRITICAL","startedAt","2026-01-22T19:18:15.430Z","updatedAt","2026-01-29T01:46:31.115Z","resolvedAt","2026-01-22T23:24:05.000Z","officialUrl","https://stspg.io/df9x1gf2vm8x","updates",[41,42,43,44,45],"id","oR7pO92vrXlW","isActive",false,{"_23":55,"_46":58,"_48":59},{"_23":55,"_46":56,"_48":57},{"_23":52,"_46":53,"_48":54},{"_23":50,"_46":51,"_48":32},{"_23":24,"_46":47,"_48":49},"body","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/INC0150359-and-INC0150440](https://community.snowflake.com/s/article/INC0150359-and-INC0150440)","occurredAt","2026-01-28T23:58:57.467Z","RESOLVED","Current status: Our observations of service telemetry continue to indicate that our service has recovered following the restart of the systems related to the Snowsight application-hosting layer. We'll continue to monitor the environment until we're confident all services are functioning properly.\n\nCustomer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight or may have experienced delays. A subset of customers may have encountered errors while executing queries and other related operations.\n\nIncident start time: 19:02 UTC January 22, 2026\nIncident end time: 19:30 UTC January 22, 2026\n\nPreliminary root cause: While we're continuing to investigate to determine the underlying root cause of this issue, we suspect that a recent change made to our internal monitoring systems may have resulted in the problem with the Snowsight application-hosting layer.\n\nA root cause analysis (RCA) document will be published within five business days.","MONITORING","Current status: Our observations of service telemetry indicate that our service has recovered following the restart of the systems related to the Snowsight application-hosting layer. We'll continue to monitor the environment until we're confident all services are functioning properly.\n\nCustomer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight or may have experienced delays.\n\nIncident start time: 19:02 UTC January 22, 2026\nIncident end time: 19:30 UTC January 22, 2026\n\nPreliminary root cause: While we're continuing to investigate to determine the underlying root cause of this issue, we suspect that a recent change made to our internal monitoring systems may have resulted in the problem with the Snowsight application-hosting layer.","2026-01-22T20:48:51.603Z","INVESTIGATING","Current status: Our investigation has led us to focus on a potential issue with the Snowsight application-hosting layer. We're restarting the systems related to the Snowsight application-hosting layer, and our initial observation of telemetry indicates that this is providing relief. We're continuing to monitor as this trend continues to ensure the service returns to normal health. We'll provide an update within 60 minutes.\n\nCustomer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight or may experience delays.","2026-01-22T19:48:31.133Z","Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes.\n\nCustomer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight or may experience delays.","2026-01-22T19:18:15.560Z","Azure - Central US (Iowa): INC0150687","2026-01-27T18:13:58.936Z","2026-02-04T03:40:43.641Z","2026-01-27T19:30:39.361Z","https://stspg.io/9qjf53j0br4q",[67,68,69,70],"0WbZvMbV1qOm",{"_23":55,"_46":76,"_48":77},{"_23":52,"_46":74,"_48":75},{"_23":50,"_46":73,"_48":63},{"_23":24,"_46":71,"_48":72},"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)","2026-02-04T01:34:42.778Z","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.\n\nCustomer 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.\n\nIncident start time: 17:51 UTC January 27, 2026\nIncident end time: 18:25 UTC January 27, 2026\n\nPreliminary 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.\n\nA root cause analysis (RCA) document will be published within five business days.","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.\n\nCustomer 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.\n\nIncident start time: 17:51 UTC January 27, 2026\nIncident end time: 18:25 UTC January 27, 2026\n\nPreliminary 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.","2026-01-27T19:02:18.422Z","Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.\n\nCustomer 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.","2026-01-27T18:13:59.086Z","dEa2q9rkyrpM","Snowflake","OPERATIONAL","statusDescription","All Systems Operational","officialPageUrl","https://status.snowflake.com/","productDomain","snowflake.com","productDomainAliases",[],"scraperState","ENABLED","activeIncidentCount",0,"incidentSourceFetchedAt","incidentDays",[98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127],"slug","snowflake",{"_128":162,"_130":140},{"_128":161,"_130":140},{"_128":160,"_130":131},{"_128":159,"_130":131},{"_128":158,"_130":140},{"_128":157,"_130":140},{"_128":156,"_130":133},{"_128":155,"_130":131},{"_128":154,"_130":131},{"_128":153,"_130":131},{"_128":152,"_130":131},{"_128":151,"_130":131},{"_128":150,"_130":131},{"_128":149,"_130":131},{"_128":148,"_130":140},{"_128":147,"_130":133},{"_128":146,"_130":140},{"_128":145,"_130":131},{"_128":144,"_130":131},{"_128":143,"_130":131},{"_128":142,"_130":131},{"_128":141,"_130":131},{"_128":139,"_130":140},{"_128":138,"_130":133},{"_128":137,"_130":131},{"_128":136,"_130":131},{"_128":135,"_130":131},{"_128":134,"_130":131},{"_128":132,"_130":133},{"_128":129,"_130":131},"date","2026-11-13","incidentCount",1,"2026-11-12",3,"2026-11-11","2026-11-10","2026-11-09","2026-11-08","2026-11-07","2026-11-06",2,"2026-11-05","2026-11-04","2026-11-03","2026-11-02","2026-11-01","2026-10-31","2026-10-30","2026-10-29","2026-10-28","2026-10-27","2026-10-26","2026-10-25","2026-10-24","2026-10-23","2026-10-22","2026-10-21","2026-10-20","2026-10-19","2026-10-18","2026-10-17","2026-10-16","2026-10-15"]

Snowflake outage history

Azure - Central US (Iowa): INC0150687

AWS - US West (Oregon): INC0150440