Is Snowflake down?

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 errors or connectivity issues when using Snowflake Openflow. Other features that leverage Snowpark Container Services aren't affected by this issue.

Current status: We've narrowed our investigation to an issue within the systems that manage connections to Openflow runtimes. We've applied a mitigation in a limited number of cases and are evaluating its effect. We're continuing to investigate the issue and will provide another update within 1 hour. Customer experience: Customers hosted in the specified regions may be unable to access or manage their Openflow runtimes deployed in Snowpark Container Services, including the Openflow canvas. Existing data flows are not affected and continue to process data. Other features that leverage Snowpark Container Services are also not affected by this issue. Impact start time: 17:34 UTC October 30, 2026

Current status: We've completed validating our fix and we're implementing it in the affected regions to resolve this issue. We anticipate that the operation will be complete within 4 hours, and affected customers will experience recovery at different times as the fix reaches their environment. We'll provide another update within 4 hours. Customer experience: Customers hosted in the specified regions may be unable to access or manage their Openflow runtimes deployed in Snowpark Container Services. Runtimes may show as active, but opening the Openflow canvas may fail with errors saying the runtime is unavailable or that the connection was refused. Most existing data flows continue to process data, and other features that leverage Snowpark Container Services aren't affected by this issue. ETA: Our current estimate is that service will be restored within 4 hours. Impact start time: 17:34 UTC October 30, 2026

Current status: We've implemented the fix for this issue across the affected regions, and 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 manage their Openflow runtimes deployed in Snowpark Container Services. Runtimes may have shown as active, but opening the Openflow canvas may have failed with errors saying the runtime was unavailable or that the connection was refused. Impact start time: 17:34 UTC October 30, 2026 Impact end time: 22:55 UTC October 30, 2026 Preliminary root cause: A subset of infrastructure responsible for secure communication with Openflow runtimes experienced a certificate issue, which prevented connections to the affected Openflow runtimes

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 manage their Openflow runtimes deployed in Snowpark Container Services. Runtimes may have shown as active, but opening the Openflow canvas may have failed with errors saying the runtime was unavailable or that the connection was refused. Impact start time: 17:34 UTC October 30, 2026 Impact end time: 22:55 UTC October 30, 2026 Preliminary root cause: A subset of infrastructure responsible for secure communication with Openflow runtimes experienced a certificate issue, which prevented connections to the affected Openflow runtimes A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

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 experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Impact start time: 03:00 UTC October 29, 2026

Current status: We've increased virtual warehouse resources in the specified regions to reduce the impact while we work to identify the cause. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to run. Workaround: There are currently no available workarounds for this issue. Impact start time: 03:00 UTC October 29, 2026

Current status: We've determined that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. The provider is deploying a fix, and we're working with them to restore service. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we expect their fix to be in place within two hours. We'll provide an updated ETA as we receive more information. Workaround: There are currently no available workarounds for this issue. Impact start time: 03:00 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

Current status: We've confirmed that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. The provider is in the process of deploying a fix, and we are starting to see initial signs of recovery across a subset of regions. We continue to work with them as they progress the fix across all impacted regions and will provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we expect their fix to be in place within 90 minutes. Workaround: There are currently no available workarounds for this issue. Impact start time: 03:00 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

Current status: We've confirmed that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. The provider remains in the process of deploying a fix across impacted regions and we're starting to see indications of recovery across our EMEA regions. We continue to work with them as they progress their recovery actions and will provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we still expect their fix to be in place within 90 minutes. Workaround: There are currently no available workarounds for this issue. Impact start time: 03:00 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

Current status: We've confirmed that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. The provider remains in the process of deploying a fix across impacted regions and, although they have revised their timeframe to recovery, we expect the majority of customer impact to now be mitigated. We remain in contact with them as they progress their recovery actions and will provide another update within 2 hours. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we expect their fix to be in place within 2 hours. Workaround: There are currently no available workarounds for this issue. Impact start time: 03:00 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

Current status: We've confirmed that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. Although the provider continues to take recovery actions impacted regions, our telemetry indicates that the majority of customer impact remains mitigated. We're in contact with the provider as they actively work towards recovery and will provide another update within 3 hours. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we can't provide an ETA for recovery but expect the majority of customer impact to be mitigated. Workaround: There are currently no available workarounds for this issue. Impact start time: 03:00 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

Current status: We've confirmed that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. The provider is actively progressing their recovery actions and our telemetry continues to indicate that the majority of customer impact is mitigated. We're in contact with the provider as they actively work towards recovery and will provide another update within 3 hours. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we can't provide an ETA for recovery but expect the majority of customer impact to be mitigated. Workaround: There are currently no available workarounds for this issue. Impact start time: 03:00 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

Current status: Our telemetry continues to indicate that the majority of customer impact is no longer occurring. We're continuing to coordinate with the third-party cloud platform provider responsible for managing the affected service environment as they actively work towards full recovery and will provide another update within 4 hours. Customer experience: Customers hosted in the specified regions may have experienced delays or intermittent failures when resuming or managing virtual warehouses, with the majority of impact occurring between 03:00 and 08:40 UTC October 29, 2026. Existing warehouses that were already running may have been unaffected. Additionally, serverless tasks may have taken longer than expected to begin. Following our mitigation actions, we aren't currently observing any ongoing customer impact. ETA: Based on information from our third-party cloud platform provider, we can't provide an ETA for recovery but expect the majority of customer impact to be mitigated. Impact start time: 03:00 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

Current status: Our telemetry continues to indicate that the majority of customer impact is no longer occurring. The third-party cloud platform provider responsible for managing the affected service environment is finalizing their fix for the issue, and we're monitoring our telemetry as the operation completes to confirm that the change has completely resolved the underlying issue affecting the provisioning request workflow. We will provide another update within 4 hours. Customer experience: Customers hosted in the specified regions may have experienced delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected. Additionally, serverless tasks may have taken longer than expected to begin. Following our mitigation actions, we aren't currently observing any ongoing customer impact. ETA: Based on information from our third-party cloud platform provider, we can't provide an ETA for recovery but expect the majority of customer impact to be mitigated. Impact start time: 03:00 UTC October 29, 2026 Impact end time: 08:40 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

Current status: Our third-party cloud platform provider has completed their fix for the underlying issue at 20:45 UTC October 29, 2026. Our earlier mitigation actions had already addressed the majority of customer impact as of 08:40 UTC October 29, 2026. With the provider's fix in place, we've reversed those temporary mitigation actions and confirmed that we are back to pre-incident configurations at 23:05 UTC October 29, 2026. 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 experienced delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected. Additionally, serverless tasks may have taken longer than expected to begin. Following our mitigation actions, we aren't currently observing any ongoing customer impact. Impact start time: 03:00 UTC October 29, 2026 Impact end time: 08:40 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

Current status: We've coordinated with our third-party cloud platform to implement the fix for this issue, and we've 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 experienced delays or intermittent failures when resuming or managing virtual warehouses, with the majority of impact occurring between 03:00 and 08:40 UTC October 29, 2026. Existing warehouses that were already running may have been unaffected. Additionally, serverless tasks may have taken longer than expected to begin. Impact start time: 03:00 UTC October 29, 2026 Impact end time: 08:40 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes. A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.

Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 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, use Snowsight, or ingest files using Snowpipe.

Current status: We're investigating the core systems that process requests in the impacted region to assist us in isolating the source of the impact and identifying a path to resolution. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, or ingest files using Snowpipe.

Current status: We're continuing to investigate the core systems that process requests in the impacted region to assist us in isolating the root cause of this issue. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, or ingest files using Snowpipe. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, customers using replication may review their failover procedures and determine whether failover is warranted based on the impact to their organization.

Current status: We've identified a configuration issue within the core systems which process requests in the impacted region that we suspect is contributing to impact, and we're further investigating this issue to confirm our findings and identify a method to restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also fail to run or may not start as expected. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, customers using replication may review their failover procedures and determine whether failover is warranted based on the impact to their organization. Impact start time: 18:00 UTC October 21, 2026

Current status: We've completed a configuration change to address the issue that we suspect caused the impact while we continue to investigate other potential factors. We're also monitoring the region for signs of recovery and are continuing to work on restoring full service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also fail to run or may not start as expected. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, customers using replication may review their failover procedures and determine whether failover is warranted based on the impact to their organization.

Current status: We're continuing to monitor the affected region, and we're seeing early signs of recovery. Affected services are recovering gradually, and we're working to confirm full restoration. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also fail to run or may not start as expected. ETA: Our current estimate is that service will be restored within 1 hour. Impact start time: 18:00 UTC October 21, 2026

Current status: Services in the specified region are recovering, and our monitoring indicates that most core services, including sign-in, Snowsight, query execution, and data ingestion, are returning to normal operation. We're continuing to monitor to confirm full recovery across all services. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also fail to run or may not start as expected. Impact start time: 18:00 UTC October 21, 2026 Preliminary root cause: A recent configuration change in the affected region caused service infrastructure to stop processing requests, resulting in a service disruption.

Current status: Our monitoring indicates that the previously affected services have returned to normal operation. 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 access or use multiple Snowflake services and features. Affected users may have been unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also have failed to run or may not start as expected. Impact start time: 18:00 UTC October 21, 2026 Impact end time: 21:25 UTC October 21, 2026 Preliminary root cause: A configuration change applied to the cloud services layer in the specified region interacted with existing settings in a way that caused a significant number of instances to be taken out of service. This led to cascading failures across sign-in, query execution, data ingestion, and other dependent services.

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 region may have been unable to access or use multiple Snowflake services and features. Affected users may have been unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also have failed to run or may not start as expected. Impact start time: 17:50 UTC October 21, 2026 Impact end time: 21:25 UTC October 21, 2026 Preliminary root cause: A configuration change applied to the cloud services layer in the specified region interacted with existing settings in a way that caused a significant number of instances to be taken out of service. This led to cascading failures across sign-in, query execution, data ingestion, and other dependent services. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

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

Current status: We identified that a subset of infrastructure responsible for routing service traffic in the affected region became intermittently unhealthy, which caused some requests to fail. We removed the affected infrastructure from service and are monitoring the environment to confirm that all services are functioning properly. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may have experienced intermittent failures when using Snowsight. Symptoms may have included slow page loads or brief errors when accessing Snowsight. Retrying the operation may have succeeded in most cases, as the issue was intermittent in nature. Impact start time: 06:18 UTC October 21, 2026 Impact end time: 07:06 UTC October 21, 2026 Preliminary root cause: A subset of infrastructure responsible for routing incoming traffic in the affected region became unavailable, resulting in intermittent failures when loading Snowsight.

Current status: We've monitored the environment and confirmed 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 experienced intermittent failures when using Snowsight. Symptoms may have included slow page loads or brief errors when accessing Snowsight. Retrying the operation may have succeeded in most cases, as the issue was intermittent in nature. Impact start time: 06:18 UTC October 21, 2026 Impact end time: 07:06 UTC October 21, 2026 Preliminary root cause: A subset of infrastructure responsible for routing incoming traffic in the affected region became unavailable, resulting in intermittent failures when loading Snowsight. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

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

Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple Snowflake services and features, including Snowflake Postgres. Affected users may experience errors or failures when connecting to Snowflake Postgres instances, managing data, loading data, or using applications. Incident start time: 06:01 UTC October 20, 2026

Current status: We've identified an issue with a third-party cloud platform that's affecting part of the infrastructure in the specified region, and we're coordinating with the provider to develop and implement a fix to restore service. We have identified an issue with one of the availability zones in the region. Workloads have automatically moved away from the affected infrastructure. We'll provide another update within 30 minutes. Customer experience: We're seeing recovery of the affected services as of 6:40 UTC. Customers hosted in the specified region may have been unable to access or use multiple Snowflake services and features, including Snowflake Postgres. Affected users may experience errors or failures when connecting to Snowflake Postgres instances, managing data, loading data, or using applications. ETA: An ETA isn't available yet. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 06:01 UTC October 20, 2026

Current status: Our monitoring has shown healthy service since 06:40 UTC October 20, 2026, but the affected availability zone remains unavailable at our third-party cloud platform provider. We've stopped new workloads from being placed in that zone and paused routine software updates in the region as a precaution. We're continuing to coordinate with the provider to restore the affected infrastructure and to develop and implement a fix. We'll provide another update within 2 hours. Customer experience: We're seeing recovery of the affected services as of 6:40 UTC. Customers hosted in the specified region may have been unable to access or use multiple Snowflake services and features, including Snowflake Postgres. Affected users may experience errors or failures when connecting to Snowflake Postgres instances, managing data, loading data, or using applications. ETA: An ETA isn't available yet. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 06:01 UTC October 20, 2026

Current status: Our monitoring has shown healthy service since 06:40 UTC October 20, 2026, but the affected availability zone remains unavailable at our third-party cloud platform provider. We've stopped new workloads from being placed in that zone and paused routine software updates in the region as a precaution. We're continuing to coordinate with the provider to restore the affected infrastructure and to develop and implement a fix. Additional updates are available on the Cloud Provider's status page https://status.cloud.google.com/. We'll provide another update within 3 hours. Customer experience: We're seeing recovery of the affected services as of 6:40 UTC. Customers hosted in the specified region may have been unable to access or use multiple Snowflake services and features, including Snowflake Postgres. Affected users may have experienced errors or failures when connecting to Snowflake Postgres instances, managing data, loading data, or using applications. ETA: An ETA isn't available yet. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 06:01 UTC October 20, 2026

Our monitoring still shows healthy service since 06:40 UTC October 20, 2026. As per updates on the Cloud Provider's status page https://status.cloud.google.com, some infrastructure in the affected availability zone at our third-party cloud platform provider has begun to come back online, but the zone isn't fully available yet. Our mitigation actions continue to keep new workloads out of the affected zone and these mitigations will remain in place until the availability zone is fully back online. We'll provide another update within 2 hours. Customer experience: We're seeing recovery of the affected services as of 6:40 UTC. Customers hosted in the specified region may have been unable to access or use multiple Snowflake services and features, including Snowflake Postgres. Affected users may have experienced errors or failures when connecting to Snowflake Postgres instances, managing data, loading data, or using applications. ETA: Our current estimate is that the availability zone will be restored within 2 hours. Workaround: There are currently no available workarounds for this issue. Incident start time: 06:01 UTC October 20, 2026

Current status: Our Cloud Provider has confirmed via their status page https://status.cloud.google.com that the issue has been largely mitigated. We're are closely monitoring service health and are preparing to revert our previously completed precautionary changes; though at this time, customers should no longer be experiencing impact. Customer experience: Customers hosted in the specified region may have been unable to access or use multiple Snowflake services and features, including Snowflake Postgres. Affected users may have experienced errors or failures when connecting to Snowflake Postgres instances, managing data, loading data, or using applications. Incident start time: 06:01 UTC October 20, 2026 Incident end time: 14:03 UTC October 20, 2026

Current status: We've monitored the environment and confirmed that service has been 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 region may have been unable to access or use multiple Snowflake services and features. Affected users may have experienced errors or failures when connecting to Snowsight, managing data, loading data, or using applications. Incident start time: 06:01 UTC October 20, 2026 Incident end time: 14:00 UTC October 20, 2026 Preliminary root cause: A power event at our third-party cloud platform provider made one of the availability zones in the specified region unavailable. Snowflake infrastructure running in that zone, including components that support Snowsight, became unreachable, and requests that depended on it failed until workloads moved to the remaining availability zones. To limit further impact, we stopped placing new workloads in the affected zone and paused routine software updates in the region until the provider restored the zone. A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.