Since approximately 12:30 UTC, some users may experience issues where assets not appearing when browsing folders in the Media Library. Affected assets remain available and may still be accessible through search. Our team is investigating the issue and working to restore normal folder visibility. We will provide another update as soon as more information is available.
We are currently investigating an issue affecting the AEO Visibility & Analytics module. Some users are reporting that the module loads as a blank screen when accessed. As a temporary workaround, users may be able to access the module by: - Refreshing the page - Navigating away and then reselecting the AEO Visibility & Analytics module from the left-hand navigation menu The issue may not occur consistently and can be intermittent. We have identified that this functionality relies on a third-party integration and are actively working with the provider to investigate and resolve the issue as quickly as possible. We will provide additional updates as more information becomes available.
Salesforce is aware of and closely monitoring a phishing campaign appearing as fraudulent emails from Salesforce with a malicious link to download Remote Monitoring & Management (RMM) software. Our security teams are working diligently to contain this issue and urge all customers to maintain a high level of vigilance against phishing and social engineering attempts, as these remain frequently used tactics by threat actors. If you receive requests from Salesforce to install RMM software, we recommend you validate its legitimacy with Salesforce Support or architect teams prior to taking action by opening up a ticket through the Salesforce Help portal. For guidance and support, please reach out through the Salesforce Help portal. You can also refer to this article for guidance on how to protect your environments from social engineering threats: https://www.salesforce.com/blog/protect-against-social-engineering/.
There’s a Salesforce service disruption. During a service disruption, end users can’t access the service. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.
There’s a Salesforce service performance degradation. Users can access the Salesforce service, but some functionality can be unavailable or running at less than optimal performance. General and intermittent slow performance, timeouts, and connectivity issues are possible. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.
We are aware of a feature disruption that may impact you and are currently working on a solution to resolve user impact. During a feature disruption, end users sometimes can’t access certain aspects of the service. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
There’s a Salesforce service feature degradation. During a feature degradation, some features are unavailable or run at less than optimal performance. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.
We are currently investigating reports of users receiving 404 errors when accessing Formstack Documents through the OnlyOffice builder experience. At this time, we are seeing impact specifically related to the OnlyOffice builder. Native builder functionality, Manage Files access, and PDF uploads are currently operating as expected. Our team is actively working to identify the root cause and assess the full scope of impact. Additional updates will be provided as more information becomes available.
We are encountering a major issue that impact all API calls.
There’s a feature degradation impacting Agentforce, and we’re working to resolve it. We believe the issue only impacts Agentforce Service Agent (ASA) and Sales Development Representative (SDR). Customers using these features may experience issues launching new chats, interruptions to chats, elevated escalation to live agents, or latency in starting new conversations. Chat and Copilot are not impacted at this time. We’re investigating the issue and we’ll provide an update in 30 minutes or sooner if additional information becomes available.
There’s a Salesforce service feature disruption. During a feature disruption, end users sometimes can’t access certain aspects of the service. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.
There’s a Salesforce service performance degradation. Users can access the Salesforce service, but some functionality can be unavailable or running at less than optimal performance. General and intermittent slow performance, timeouts, and connectivity issues are possible. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.
There’s a Salesforce service feature degradation. During a feature degradation, some features are unavailable or run at less than optimal performance. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.
Between 17:38 and 17:57 UTC, we experienced elevated error rates affecting the Build Pipeline. Some customers may have encountered failed deploys or HTTP 500/503 errors during deployment processing. The systems are recovering and we're continuing to investigate the root cause
Usage API is encountering a major outage
Insights US is encountering a major outage
Insights DE is encountering a major outage
There’s a Salesforce service performance degradation. Users can access the Salesforce service, but some functionality can be unavailable or running at less than optimal performance. General and intermittent slow performance, timeouts, and connectivity issues are possible. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.
On May 19, 2026, between 05:30 UTC and 14:50 UTC, some Copilot users experienced failures when using code completions, chat sessions, and cloud agent sessions. At peak impact, approximately 13% of Copilot API requests failed, and approximately 24% of remote sessions failed to initialize. A partial mitigation at 08:16 UTC reduced the Copilot API error rate to approximately 0.3%, but intermittent failures persisted until a full fix was deployed at 14:15 UTC and recovery was verified by 14:50 UTC. The incident was caused by rate limits being exceeded on a shared infrastructure component. A recently enabled feature increased call volume to this component, and the combined load exceeded capacity limits as traffic increased during business hours. We mitigated the incident by deploying a caching layer to reduce load on shared infrastructure. To prevent recurrence, we are separating rate limit scopes between services, adding monitoring for internal dependency rate limiting, and reducing redundant calls.
There’s a Salesforce service performance degradation. Users can access the Salesforce service, but some functionality can be unavailable or running at less than optimal performance. General and intermittent slow performance, timeouts, and connectivity issues are possible. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.
Impact Statement: Starting from 13:59 UTC on 18 May 2026, customers using Microsoft Fabric - including Power BI and PowerBI Embedded - may be experiencing delays or failures while interacting with the service. This issue is affecting multiple regions in the Azure public cloud. Current Status: For the latest details, please refer to the Microsoft Fabric service status page: https://support.fabric.microsoft.com/support/
Impact Statement: Starting from 13:59 UTC on 18 May 2026, customers using Microsoft Fabric - including PowerBI and PowerBI Embedded - may be experiencing delays or failures while interacting with the service. This issue is affecting multiple regions in the Azure public cloud.Current Status: We are aware of this issue and are actively investigating. Our analysis indicates that an unexpected increase in request traffic is causing a portion of the infrastructure to operate below optimal levels. Our on-call engineering teams are investigating relevant mitigations. There is no workaround available at this time. We expect to be able to resolve this issue by 18:45 UTC, approximately 90 minutes from now. The next update will be provided in 60 minutes, or as events warrant.
We are aware of a performance degradation that may impact you and are currently working on a solution to resolve user impact. During a performance degradation users can access the service, but some functionality can be unavailable or running at less than optimal performance. General and intermittent slow performance, timeouts, and connectivity issues are possible. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
There’s a Salesforce service feature disruption. During a feature disruption, end users sometimes can’t access certain aspects of the service. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.
There’s a Commerce Cloud service disruption that’s affecting our Business Manager and customer storefront functionality. During a service disruption, users are unable to access the services. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.
Beginning at 02:49 UTC on May 15 2026 and lasting until 03:04 UTC, GitHub.com was unavailable for a subset of customers. This impact has been mitigated and normal service resumed. The issue was rooted in a sudden spike in traffic, with intermittent impact. We've identified the source of the traffic and prevented further disruption.
We will be carrying out a database upgrade during this maintenance window, affecting the EU and US regions. During the upgrade, the User Management API and the Spaces and Organizations endpoints in the Content Management API may experience brief interruptions. This may temporarily affect signup, login, logout, API key creation, SSO configuration, and access to license and account information. The Content Delivery API (CDA), Content Preview API (CPA), and GraphQL Content API are not affected.
Sauce Labs will have a two hour previously scheduled maintenance window on September 5th starting at 13:00 UTC and ending at 15:00 UTC. During this maintenance window, we will be making updates to our infrastructure and services in our US East data center. These maintenance actions may cause portions of the service (including running automated and manual tests) to be unavailable for up to two hours.
Sauce Labs will have a two hour previously scheduled maintenance window on September 5th, starting at 15:00 UTC and ending at 17:00 UTC. During this maintenance window, we will be making updates to our infrastructure and services in our EU Central data center. These maintenance actions may cause portions of the service (including running automated and manual tests) to be unavailable for up to two hours.
Sauce Labs will have a two hour previously scheduled maintenance window on September 5th, starting at 17:00 UTC and ending at 19:00 UTC. During this maintenance window, we will be making updates to our infrastructure and services in our US West data center. These maintenance actions may cause portions of the service (including running automated and manual tests) to be unavailable for up to two hours.
Sauce Labs will have a two hour regularly scheduled maintenance window of Error Reporting (Backtrace) product on August 19th, starting at 15:00 UTC and ending at 17:00 UTC. During this maintenance window, we will be making updates to related infrastructure and services. These maintenance actions may cause portions of the service to be unavailable for up to two hours.