SupportWizard Diagnostics

Object Storage service in location nbg1 is currently degraded. Requests may fail or time out. We are currently investigating the issue.

We are continuing to investigate this issue. The scope of this CVE has been expanded to include any foreign data which is being processed with the Brotli decoder, not just node.js. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001apcFhCAIWe will provide an update as we progress.

8x8 is currently investigating intermittent call connectivity issues for US Region Contact Center customers. 8x8 Operations teams are engaged and investigating the cause. We'll provide updates as they become available.

Status: No impact identified; review ongoing We have found no impact to Notion from PHP2Shell. Notion's services do not run PHP. Our review is continuing, and we'll update this notice if anything changes.

We are investigating a potential issue with the service. An update will be provided within 30 minutes.

We are experiencing higher than normal latency in our US West region. We have identified the issue and are working on a fix.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Title: Users may be unable to create SharePoint knowledge agents using Microsoft 365 Copilot in SharePoint Online User impact: Users may be unable to create SharePoint knowledge agents using Microsoft 365 Copilot in SharePoint Online. More info: When users attempt to create a SharePoint knowledge agent using Copilot in SharePoint Online, they may receive an error that states, “We couldn't verify your license.” Current status: We're continuing to monitor the rate of the deployment's progression through the impacted environment in an effort to establish a timeline for remediation. We'll aim to provide an update on this when possible. Scope of impact: Any user attempting to create SharePoint knowledge agents using Copilot in SharePoint Online may be affected. This information may be updated as our investigation continues. Root cause: A recent service change had a missing configuration that's preventing the licensing from being fetched and validated, causing impact. Next update by: Wednesday, October 28, 2026, at 7:00 PM UTC

Some Salesforce Pardot Zaps continue to experience connection errors, preventing them from running or delaying workflows. We are continuing to work with our partner, Salesforce, to obtain full confirmation of the underlying issue and the steps needed for recovery. If you are affected, try reconnecting your Salesforce Pardot account in Zapier. Reconnecting has helped some customers restore their connections and may resolve the errors, but we have not confirmed that it works for everyone affected. If errors persist after reconnecting, or you need help, please contact our support team "contact our support team": https://zapier.com/app/get-help. We do not yet have a confirmed recovery time.

The issue has been identified and a fix is being implemented.

Core Cloud Services - Admin UI: Zscaler has detected an issue with its zscloud.net Cloud. Customers may encounter issues with Administation UI login, Zscaler Client Connector portal, and SCIM auto-provisioning. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.Latest Update - Fri, 23 Oct 2026 02:29:03 UTCZscaler continues to monitor service performance in the zscloud.net cloud following mitigation. Recent monitoring indicates improved performance. We remain focused on sustained recovery and continue to work toward full resolution. Further updates will be provided as more information becomes available.Update - Tue, 20 Oct 2026 10:34:43 UTCZscaler is prioritizing the issue and is actively working to isolate the problem and identify the root cause. We appreciate your patience and understanding during this investigation. Additional updates will be provided as more information becomes available.Update - Tue, 20 Oct 2026 14:14:19 UTCZscaler has implemented preliminary mitigation measures to address the issue. The team is actively monitoring and evaluating the effectiveness of these measures.Update - Wed, 21 Oct 2026 05:48:28 UTCZscaler's monitoring confirms that the environment has remained stable following the mitigation. Continued monitoring is in place to ensure sustained stability and prevent recurrence.Update - Wed, 21 Oct 2026 19:07:39 UTCZscaler continues to monitor the service following the mitigation actions implemented earlier. While the issue is not yet fully resolved, we are closely monitoring the environment and actively working toward full restoration. We will provide additional updates as more information becomes available.Update - Fri, 23 Oct 2026 02:29:03 UTCZscaler continues to monitor service performance in the zscloud.net cloud following mitigation. Recent monitoring indicates improved performance. We remain focused on sustained recovery and continue to work toward full resolution. Further updates will be provided as more information becomes available.

Current status: Virtual warehouse capacity and provisioning have remained stable, and we do not expect further broad risk to customer workloads, but we will continue monitoring through periods of peak demand. Snowpark Container Services (SPCS) remains subject to capacity constraints. We continue to preserve available resources, coordinate with our third-party cloud provider, and work on additional capacity options. We have seen improvement, but workloads that require additional new capacity may still be affected. We continue to target late October before considering the SPCS impact mitigated, subject to sustained resource availability and service readiness. We will provide another update within seven days, or sooner if there is a significant change. Customer experience: Customers using virtual warehouses should no longer experience the broader provisioning impact associated with this incident. Customers with continuing or customer-specific reliability issues should contact Snowflake Support for assistance. Customers using Snowpark Container Services may still encounter delays, timeouts, or failures when starting or resuming Notebooks, provisioning or resuming compute pools, or setting up OpenFlow runtimes. The remaining risk is concentrated in workloads that require additional new capacity; existing workloads generally continue to run normally. ETA: We have seen sustained stability in virtual warehouse capacity and provisioning since October 7, 2026. For Snowpark Container Services, we continue to target late October for mitigation as additional capacity and service readiness are validated. We will provide an updated ETA if that timeline changes. Workaround: For virtual warehouses, we are no longer recommending a broad migration to Gen1 as a workaround for this incident. Customers who previously moved affected warehouses to Gen1 may work with Snowflake Support or their account team to evaluate returning to Gen2. There is currently no general workaround for Snowpark Container Services compute pool impact; customers experiencing specific failures should contact Snowflake Support. Impact start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform is experiencing constrained compute capacity in the specified region, limiting the availability of compute resources for Snowpark Container Services and causing delays or failures when provisioning or resuming virtual warehouses.

Planned Maintenance

Our third-party SMS provider has reported an issue that may impact the successful delivery of SMS messages used for Two-Factor Authentication (2FA). The provider is actively working on a resolution, and we will provide updates as they become available.

We are currently aware of and investigating an issue with cropped images disappearing after selecting "Done".

Our third-party SMS provider has reported an issue that may impact the successful delivery of SMS messages used for Two-Factor Authentication (2FA). The provider is actively working on a resolution, and we will provide updates as they become available.

A fix has been implemented and we are monitoring the results.

ConnectWise is investigating recent attempts of unauthorized access associated with the ConnectWise Cloud Backup environment. Upon detecting this threat, we promptly initiated our incident response procedures. Containment measures are in place, and our investigation continues. At this time, there is no indication that partner backup data has been accessed. Our engineering teams are continuing to explore the nature and scope of the issue. Our investigation is ongoing, and we will provide additional information as appropriate. We appreciate your patience while we work through this process. Indicators of Compromise (IOCs) The following indicators have been associated with the reported suspicious authentication activity . Source IP Address 144.172.64.128 Observed User Agents Python-urllib/3.12 python-requests/2.31 These indicators are provided transparency to assist with security monitoring and investigation. Their presence alone does not establish unauthorized activity or confirm compromise.

We have developed a fix that is currently undergoing QA testing. We are targeting deployment on 26 October 2026 and will provide an update if this date changes.

The root cause has been identified as undersea cable issues affecting Azure infrastructure. The impact is highest for South Africa, which has the longest network path to Australia. Requests from South Africa to Azure DevOps organizations hosted in Australia are seeing an availability impact of around 6%. We expect improvement by October 26 and further recovery by November 4, though both dates are tentative due to technical complexity of the issue itself.

The issue has been identified and a fix is being implemented.

We're aware of recently announced PHP vulnerabilities. We have mitigations in place, and have patched our managed services, including Web Hosting and Managed Hosting for WordPress. If you manage your own server or VPS, you'll need to apply the PHP update yourself. Latest updates and steps can be found at https://www.godaddy.com/resources/news/important-php-security-update-what-website-owners-need-to-do

The issue has been identified and mitigation is in process.

Twilio customers may be experiencing voice call failures from Twilio Phone Numbers to network subscribers in Romania. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 4 hours or as soon as more information becomes available.

Customers will see an error opening a data source from a workbook: "That page could not be accessed. Either the data source does not exist or you do not have the necessary permissions. Engineers are working on a fix, there is a workaround to access these data sources: Don't open the data source from the workbook's Data Sources list. Go to Explore → Data Sources and select the data source by name. We have a KI published: https://help.salesforce.com/s/articleView?id=005465388&type=1

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are providing an update on the disruption affecting the Middle East (UAE) (me-central-1) Region. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in the mec1-az2 Availability Zone. We continue to work on recovering regional resources, as well as zonal resources hosted in the other affected Availability Zones (mec1-az1 and mec1-az3). Since the disruption began in March, most customers have been able to re-establish their operations in other Regions by restoring backups or copying data that remained accessible. AWS Support remains available to help customers who need assistance moving their applications to alternate Regions. We remain committed to supporting our customers in the UAE. We are working on replacing the affected infrastructure and will provide an update on the restoration of our services in the coming months. We have notified the relevant authorities and continue to work with them toward that goal.