We are investigating reports of impacted performance for some GitHub services.

Users of our Shopify integration may be encountering issues due to an issue with Shopify. You can find more details of the issue here: https://www.shopifystatus.com/

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’re currently investigating reports of issues affecting login services the US-only region. Users may experience issues while logging in. Our team is working to identify the cause and will share updates as soon as possible.

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 investigating reports of impacted performance for some GitHub services.

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.

Some customers are experiencing issues uploading files. We are investigating.

We are aware of an issue affecting AI Assistant. We have identified the issue and will provide updates as the investigation progresses

We are currently investigating this incident and will post updates as soon as we know more.

We are investigating reports of impacted performance for some GitHub services.

We are experiencing an issue where the US-EAST data center is currently unavailable. We are investigating.

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 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.

Some Upstash Vector indexes in the US-EAST-1 region may be experiencing intermittent slowness. Initial investigation indicates this may be related to memory pressure on the affected servers. Our team is actively investigating the root cause and working to restore normal performance. We will provide updates as soon as more information is available.

Between May 29th at 15:30 UTC till June 2 6:08 UTC, we experienced sporadic issues with Blobs in our Sydney region, affecting any Function using Blobs, including the ones that are generated by the framework runtimes. Our team has deployed a fix and the errors have subsided.

In the 20 mins duration some customers might have seen some missing snapshots in the build or failures in creating builds themselves with the 401 status code on the Percy CLI logs. We have fixed the issue and monitoring the stack.

Impact Statement- Starting at 04:27 UTC on 29 May 2026, customers may experience increased latency, intermittent connectivity, or timeouts when accessing resources hosted in the West US 2 region, due to a power event. We are in process of recovering power and working to restore infrastructure in the region. We started seeing partial recovery and will be sending targeted communications to impacted customers through the Azure Service Health dashboard. The next update will be provided within 60 minutes.

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.

Impact statement: Starting at 04:27 UTC on 29 May 2026, a severe thunderstorm caused widespread utility power loss across multiple West US 2 datacenter facilities, resulting in impact to multiple Azure services. Datacenter power has been fully restored, and the majority of network and storage infrastructure has recovered. Infrastructure in Availability Zone 2 has recovered and is operating normally. Residual impact is now concentrated on a subset of infrastructure within Availability Zones 1 and 3, where two storage stamps are undergoing final recovery and validation. Customers with resources deployed exclusively in Availability Zone 2 should not be affected by the remaining recovery activities; however, those with dependencies in Availability Zones 1 or 3 may continue to experience intermittent connectivity, elevated latency, or resource unavailability.The following Azure services are in the final stages of recovery:Azure SQL, Virtual Machines, Virtual Machine Scale Sets, Azure Kubernetes Service, Application Insights, Azure Monitor, and Azure Log Analytics.The following services have recovered and are operating normally:Azure Managed Grafana, Azure Database for MySQL Flexible Server, Azure Functions, Azure Database for PostgreSQL Flexible Server, Service Bus, Azure Storage, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Azure Resource Manager, Azure Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Data Factory, Azure Databricks, Azure Cache for Redis, and Azure Synapse Analytics.Current Status: A severe weather event, including multiple lightning strikes, affected several datacenter facilities in the West US 2 region, resulting in concurrent utility power interruptions across multiple availability zones. Backup generators activated as designed; however, during the transition to sustained generator operation, a subset of generator systems were unable to fully synchronize under the sudden facility load, while others subsequently shut down due to thermal protection mechanisms as cooling systems were impacted by the broader power disruption. Because these events occurred across multiple facilities within the same timeframe, the resulting conditions exceeded the resiliency designed for this particular failure scenario.Datacenter utility power has been fully restored. HVAC systems have normalized, ambient temperatures have returned to expected operating ranges, and the majority of network and storage infrastructure has recovered successfully. While most services have returned to normal operation, two storage stamps are completing final recovery and validation activities. These stamps have shown consistent improvement throughout the recovery process, with functionality progressively returning to expected levels. The remaining impacted services should continue recovering incrementally as validation activities complete; we are monitoring stamp health to confirm sustained stability before declaring full mitigation.Estimated Time to Resolution: With datacenter power restored and the majority of network and storage infrastructure recovered, remaining work is focused on two storage stamps completing final recovery and data integrity validation activities. Based on current progress, we estimate full-service restoration within approximately 1-2 hours. Individual services dependent on these stamps will recover progressively as validation activities are completed.Customer Guidance:Single-region workloads will recover automatically as infrastructure restoration activities are completed; no customer action is required.We recommend postponing new deployments into West US 2 until this incident is resolved and using alternate regions for urgent deployment needs.Logical availability zones assigned to customer subscriptions may map to different physical availability zones. Customers can use the Locations API to understand this mapping: https://learn.microsoft.com/rest/api/resources/subscriptions/list-locations?HTTP#availabilityzonemappings.Next Update: We will provide our next status update within 60 minutes, or sooner if significant progress is made.

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 28, 2026, between 19:07 UTC and 19:16 UTC, multiple GitHub services experienced elevated error rates. This was due to a change that was partially deployed to an authentication service, causing errors for dependent services including the web experience, REST API, Git operations, and GitHub Actions. At peak impact, 10% of GitHub Actions runs failed to queue or encountered errors while downloading actions. We mitigated the incident by rolling back the change. We are expanding test coverage and improving our deployment validation process to prevent recurrence of this issue in the future.

We are investigating reports of impacted performance for some GitHub services.

We are currently investigating this incident.

We are investigating an issue affecting some in progress workflow sessions that include the Data Search step. Our engineering team is actively working on a fix. New updates will be shared as we learn more.

There’s a service degradation impacting Salesforce Data Cloud. Users can access the service however some functionality can be unavailable or running at less than optimal performance. The team is actively monitoring and working to restore the service. To see if your account is affected, use the following guide to identify your functional domain: https://sfdc.co/MiAEk or alternatively follow this article if you need to identify your core instance http://sfdc.co/coreinstance

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.

We are investigating reports of degraded performance for Webhooks