XIO

xArchive

Stored page text, served from the archive.

Snowflake Status - INC20000106

Archived: 2026-11-10 13:27:19 UTC View live page ↗
https://status.snowflake.com/incidents/0yt2v05n42gz

Stored text only -- layout, images, and scripts from the original page are not preserved.

COMMUNITY SUPPORT STATUS API Subscribe to Updates Subscribe x Get email notifications whenever Snowflake creates , updates or resolves an incident. Email address: Enter OTP: Resend OTP in: seconds Didn't receive the OTP? Resend OTP By subscribing you agree to our Privacy Policy . This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Get text message notifications whenever Snowflake creates or resolves an incident. Country code: Afghanistan (+93) Albania (+355) Algeria (+213) American Samoa (+1) Andorra (+376) Angola (+244) Anguilla (+1) Antigua and Barbuda (+1) Argentina (+54) Armenia (+374) Aruba (+297) Australia/Cocos/Christmas Island (+61) Austria (+43) Azerbaijan (+994) Bahamas (+1) Bahrain (+973) Bangladesh (+880) Barbados (+1) Belarus (+375) Belgium (+32) Belize (+501) Benin (+229) Bermuda (+1) Bolivia (+591) Bosnia and Herzegovina (+387) Botswana (+267) Brazil (+55) Brunei (+673) Bulgaria (+359) Burkina Faso (+226) Burundi (+257) Cambodia (+855) Cameroon (+237) Canada (+1) Cape Verde (+238) Cayman Islands (+1) Central Africa (+236) Chad (+235) Chile (+56) China (+86) Colombia (+57) Comoros (+269) Congo (+242) Congo, Dem Rep (+243) Costa Rica (+506) Croatia (+385) Cyprus (+357) Czech Republic (+420) Denmark (+45) Djibouti (+253) Dominica (+1) Dominican Republic (+1) Egypt (+20) El Salvador (+503) Equatorial Guinea (+240) Estonia (+372) Ethiopia (+251) Faroe Islands (+298) Fiji (+679) Finland/Aland Islands (+358) France (+33) French Guiana (+594) French Polynesia (+689) Gabon (+241) Gambia (+220) Georgia (+995) Germany (+49) Ghana (+233) Gibraltar (+350) Greece (+30) Greenland (+299) Grenada (+1) Guadeloupe (+590) Guam (+1) Guatemala (+502) Guinea (+224) Guyana (+592) Haiti (+509) Honduras (+504) Hong Kong (+852) Hungary (+36) Iceland (+354) India (+91) Indonesia (+62) Iraq (+964) Ireland (+353) Israel (+972) Italy (+39) Jamaica (+1) Japan (+81) Jordan (+962) Kenya (+254) Korea, Republic of (+82) Kosovo (+383) Kuwait (+965) Kyrgyzstan (+996) Laos (+856) Latvia (+371) Lebanon (+961) Lesotho (+266) Liberia (+231) Libya (+218) Liechtenstein (+423) Lithuania (+370) Luxembourg (+352) Macao (+853) Macedonia (+389) Madagascar (+261) Malawi (+265) Malaysia (+60) Maldives (+960) Mali (+223) Malta (+356) Martinique (+596) Mauritania (+222) Mauritius (+230) Mexico (+52) Monaco (+377) Mongolia (+976) Montenegro (+382) Montserrat (+1) Morocco/Western Sahara (+212) Mozambique (+258) Namibia (+264) Nepal (+977) Netherlands (+31) New Zealand (+64) Nicaragua (+505) Niger (+227) Nigeria (+234) Norway (+47) Oman (+968) Pakistan (+92) Palestinian Territory (+970) Panama (+507) Paraguay (+595) Peru (+51) Philippines (+63) Poland (+48) Portugal (+351) Puerto Rico (+1) Qatar (+974) Reunion/Mayotte (+262) Romania (+40) Russia/Kazakhstan (+7) Rwanda (+250) Samoa (+685) San Marino (+378) Saudi Arabia (+966) Senegal (+221) Serbia (+381) Seychelles (+248) Sierra Leone (+232) Singapore (+65) Slovakia (+421) Slovenia (+386) South Africa (+27) Spain (+34) Sri Lanka (+94) St Kitts and Nevis (+1) St Lucia (+1) St Vincent Grenadines (+1) Sudan (+249) Suriname (+597) Swaziland (+268) Sweden (+46) Switzerland (+41) Taiwan (+886) Tajikistan (+992) Tanzania (+255) Thailand (+66) Togo (+228) Tonga (+676) Trinidad and Tobago (+1) Tunisia (+216) Turkey (+90) Turks and Caicos Islands (+1) Uganda (+256) Ukraine (+380) United Arab Emirates (+971) United Kingdom (+44) United States (+1) Uruguay (+598) Uzbekistan (+998) Venezuela (+58) Vietnam (+84) Virgin Islands, British (+1) Virgin Islands, U.S. (+1) Yemen (+967) Zambia (+260) Zimbabwe (+263) Phone number: Change number Enter OTP: Resend OTP in: 30 seconds Didn't receive the OTP? Resend OTP Message and data rates may apply.

By subscribing you agree to our Privacy Policy , the Atlassian Terms of Service , and the Atlassian Privacy Policy . This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Get incident updates and maintenance status messages in Slack. Subscribe via Slack By subscribing you acknowledge our Privacy Policy .

In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy . Get incident updates and maintenance status messages in Microsoft Teams channel. Channel's Webhook URL: Here's where to find the URL of a teams channel By subscribing you acknowledge our Privacy Policy . In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy .

Get webhook notifications whenever Snowflake creates an incident, updates an incident, resolves an incident or changes a component status. Webhook URL: The URL we should send the webhooks to Email address: We'll send you email if your endpoint fails By subscribing you agree to our Privacy Policy . This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Get the Atom Feed or RSS Feed .

INC20000106 Incident Report for Snowflake Postmortem 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/INC20000106 Posted Jul 31 , 2026 - 20:38 UTC Resolved Current status: We've confirmed that this issue has been resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. 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 resume warehouses or may have experienced significant delays with serverless tasks and other workloads that required compute resources.

Queries may have queued for extended periods instead of executing immediately, with some customers experiencing delays of several hours. Workaround: There were no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Incident end time: 15:05 UTC July 25, 2026 Preliminary root cause: Unexpected demand from a large-scale workload exceeded available network capacity in the affected region, causing resource exhaustion that prevented new compute resources from being provisioned. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

Posted Jul 25 , 2026 - 16:01 UTC Monitoring Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified region may have been unable to resume warehouses or may have experienced significant delays with serverless tasks and other workloads that required compute resources. Queries may have queued for extended periods instead of executing immediately, with some customers experiencing delays of several hours. Workaround: There were no available workarounds for this issue.

Incident start time: 07:45 UTC July 25, 2026 Incident end time: 15:05 UTC July 25, 2026 Preliminary root cause: Unexpected demand from a large-scale workload exceeded available network capacity in the affected region, causing resource exhaustion that prevented new compute resources from being provisioned. Posted Jul 25 , 2026 - 15:28 UTC Update Current status: We've identified that IP address exhaustion in the affected region is preventing new compute resources from being provisioned, and we're implementing additional network capacity to restore service. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be unable to resume warehouses or may experience significant delays with serverless tasks and other workloads that require compute resources.

Queries may queue for extended periods instead of executing immediately, with some customers experiencing delays of several hours. ETA: We've implemented additional network capacity to resolve the IP address exhaustion. Service restoration is dependent on additional workload adjustments affecting resource consumption. An ETA is not yet available.

We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Preliminary root cause: Unexpected demand from a large-scale workload exceeded available network capacity in the affected region, causing IP address exhaustion that prevents new compute resources from being provisioned. Posted Jul 25 , 2026 - 14:38 UTC Update Current status: We've identified that IP address exhaustion in the affected region is preventing new compute resources from being provisioned, and we're implementing additional network capacity to restore service.

We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be unable to resume warehouses or may experience significant delays with serverless tasks and other workloads that require compute resources. Queries may queue for extended periods instead of executing immediately, with some customers experiencing delays of several hours. ETA: We're implementing additional network capacity to resolve the IP address exhaustion.

An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Preliminary root cause: Unexpected demand from a large-scale workload exceeded available network capacity in the affected region, causing IP address exhaustion that prevents new compute resources from being provisioned.

Posted Jul 25 , 2026 - 12:45 UTC Update Current status: We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be unable to resume warehouses or may experience delays with serverless tasks and other workloads that require compute resources. Queries may queue instead of executing immediately.

ETA: We're working with a third-party cloud platform to remove throttling limits. An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue.

Incident start time: 07:45 UTC July 25, 2026 Preliminary root cause: Unexpected demand exceeded available capacity in the affected region, causing the third-party cloud platform to throttle provisioning requests. Posted Jul 25 , 2026 - 10:52 UTC Identified Current status: We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified regions may experience intermittent delays or failures when accessing or using Snowflake services and features.

This may include slower query execution, intermittent availability, or limited feature functionality. ETA: We're working with a third-party cloud platform to increase capacity limits. An ETA is not yet available. We'll provide one as soon as possible.

Workaround: There are currently no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Preliminary root cause: Unexpected demand exceeded available capacity in the affected region, causing the third-party cloud platform to throttle provisioning requests. Posted Jul 25 , 2026 - 09:57 UTC Investigating Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour.

Customer experience: Customers hosted in the specified regions may experience longer than expected warehouse resume and spin-up times for standard warehouses. All other Snowflake features are not impacted. ETA: An ETA is not yet available. We'll provide one as soon as possible.

In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Posted Jul 25 , 2026 - 09:05 UTC This incident affected: Azure - Central US (Iowa) (Databases, Tables, and Views, Virtual Warehouses). ← Current Status Powered by Atlassian Statuspage Operational Disruption Partial Outage Outage Under Maintenance AWS Azure GCP ABOUT LEGAL CAREERS COMMUNITY PRIVACY DOCS SUPPORT © Snowflake Computing Inc.

All Rights Reserved × Subscribe to Incident Subscribe to updates for INC20000106 via email and/or text message. You'll receive email notifications when incidents are updated, and text message notifications whenever Snowflake creates or resolves an incident. VIA EMAIL: VIA SMS: Afghanistan (+93) Albania (+355) Algeria (+213) American Samoa (+1) Andorra (+376) Angola (+244) Anguilla (+1) Antigua and Barbuda (+1) Argentina (+54) Armenia (+374) Aruba (+297) Australia/Cocos/Christmas Island (+61) Austria (+43) Azerbaijan (+994) Bahamas (+1) Bahrain (+973) Bangladesh (+880) Barbados (+1) Belarus (+375) Belgium (+32) Belize (+501) Benin (+229) Bermuda (+1) Bolivia (+591) Bosnia and Herzegovina (+387) Botswana (+267) Brazil (+55) Brunei (+673) Bulgaria (+359) Burkina Faso (+226) Burundi (+257) Cambodia (+855) Cameroon (+237) Canada (+1) Cape Verde (+238) Cayman Islands (+1) Central Africa (+236) Chad (+235) Chile (+56) China (+86) Colombia (+57) Comoros (+269) Congo (+242) Congo, Dem Rep (+243) Costa Rica (+506) Croatia (+385) Cyprus (+357) Czech Republic (+420) Denmark (+45) Djibouti (+253) Dominica (+1) Dominican Republic (+1) Egypt (+20) El Salvador (+503) Equatorial Guinea (+240) Estonia (+372) Ethiopia (+251) Faroe Islands (+298) Fiji (+679) Finland/Aland Islands (+358) France (+33) French Guiana (+594) French Polynesia (+689) Gabon (+241) Gambia (+220) Georgia (+995) Germany (+49) Ghana (+233) Gibraltar (+350) Greece (+30) Greenland (+299) Grenada (+1) Guadeloupe (+590) Guam (+1) Guatemala (+502) Guinea (+224) Guyana (+592) Haiti (+509) Honduras (+504) Hong Kong (+852) Hungary (+36) Iceland (+354) India (+91) Indonesia (+62) Iraq (+964) Ireland (+353) Israel (+972) Italy (+39) Jamaica (+1) Japan (+81) Jordan (+962) Kenya (+254) Korea, Republic of (+82) Kosovo (+383) Kuwait (+965) Kyrgyzstan (+996) Laos (+856) Latvia (+371) Lebanon (+961) Lesotho (+266) Liberia (+231) Libya (+218) Liechtenstein (+423) Lithuania (+370) Luxembourg (+352) Macao (+853) Macedonia (+389) Madagascar (+261) Malawi (+265) Malaysia (+60) Maldives (+960) Mali (+223) Malta (+356) Martinique (+596) Mauritania (+222) Mauritius (+230) Mexico (+52) Monaco (+377) Mongolia (+976) Montenegro (+382) Montserrat (+1) Morocco/Western Sahara (+212) Mozambique (+258) Namibia (+264) Nepal (+977) Netherlands (+31) New Zealand (+64) Nicaragua (+505) Niger (+227) Nigeria (+234) Norway (+47) Oman (+968) Pakistan (+92) Palestinian Territory (+970) Panama (+507) Paraguay (+595) Peru (+51) Philippines (+63) Poland (+48) Portugal (+351) Puerto Rico (+1) Qatar (+974) Reunion/Mayotte (+262) Romania (+40) Russia/Kazakhstan (+7) Rwanda (+250) Samoa (+685) San Marino (+378) Saudi Arabia (+966) Senegal (+221) Serbia (+381) Seychelles (+248) Sierra Leone (+232) Singapore (+65) Slovakia (+421) Slovenia (+386) South Africa (+27) Spain (+34) Sri Lanka (+94) St Kitts and Nevis (+1) St Lucia (+1) St Vincent Grenadines (+1) Sudan (+249) Suriname (+597) Swaziland (+268) Sweden (+46) Switzerland (+41) Taiwan (+886) Tajikistan (+992) Tanzania (+255) Thailand (+66) Togo (+228) Tonga (+676) Trinidad and Tobago (+1) Tunisia (+216) Turkey (+90) Turks and Caicos Islands (+1) Uganda (+256) Ukraine (+380) United Arab Emirates (+971) United Kingdom (+44) United States (+1) Uruguay (+598) Uzbekistan (+998) Venezuela (+58) Vietnam (+84) Virgin Islands, British (+1) Virgin Islands, U.S. (+1) Yemen (+967) Zambia (+260) Zimbabwe (+263) Enter mobile number Edit number Send OTP Enter the OTP sent Resend OTP in 30 seconds To receive SMS updates, please verify your number.

To proceed with just email click ‘Subscribe’ Subscribe to Incident Message and data rates may apply. By subscribing you agree to our Privacy Policy , the Atlassian Terms of Service , and the Atlassian Privacy Policy . This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.