Check here before you debug your own stack. A live record of major internet outages: what broke, when it started, and how long the service was down.
Active incident
Between 13:30 PDT and 13:33 PDT, Programmable Messaging API. Users may have experienced 5XX errors when sending messages. There was no impact to SMS and MMS. The issue has been resolved.
View incident →Click any outage to explore the incident.
We are aware of an issue with Klarna, which may be affecting checkouts using this gateway, and other related performance issues.
We are aware of a feature degradation that may impact you and are currently working on a solution to resolve user impact. During a feature degradation, certain features are unavailable or run at less than optimal performance. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
We are currently investigate the issue.
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.
Customers using Freshservice webhook triggers may not receive new updates in their Zaps. We are investigating the disruption with Freshservice and will share further information as it becomes available.
We are aware of a bug affecting customers on Elasticsearch versions 9.5.0, 9.5.1 and 9.5.2 where bulk index operations processed on the primary shard can result in divergence on the replicas resulting in high disk usage and long-running recoveries. The team is working on a fix. More information can be found on https://www.elastic.co/docs/release-notes/elasticsearch/known-issues#elasticsearch-9.5.2-known-issues The next update will be in the next 2 hours or sooner if needed.
Some Firefox users may see delayed or failed asset loads on R2 custom domains due to an incorrect HTTP/3 advertisement. We are working on a fix.
Title: Users may experience issues when utilizing multiple Microsoft 365 services User impact: Users may experience issues when utilizing multiple Microsoft 365 services. More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. OneDrive for Business and SharePoint Online: -Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: -Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected. Microsoft Teams: -Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. Microsoft Purview: -Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: -Users may experience intermittent authorization failures across solutions in Defender. Current status: We've identified issues related to a core authentication configuration used by multiple Microsoft 365 services which is resulting in the impact outlined above. We've identified a potential remediation and we're performing tests to ensure its efficacy before applying it more broadly. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Next update by: Monday, August 31, 2026, at 6:30 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Monday, August 31, 2026, at 7:30 PM UTC
Cloudflare is investigating issues with Cloudflare WARP and Cloudflare Zero Trust users being incorrectly geolocated by some third party services.
Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context. More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels. Current status: We've reproduced the issue in our testing environment and are reviewing HTTP Archive (HAR) logs to determine why direct links fail when Authentication Context is enabled through sensitivity labels. Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted. Next update by: Monday, August 31, 2026, at 2:30 PM UTC
We are investigating reports that a limited number of users in Myanmar are unable to access Supabase. We will provide additional updates as information becomes available.
We have identified the root cause of newly refreshed JWTs being rejected by the API, resulting in HTTP 401 errors for affected sessions. We are working on a fix and will provide updates as things progress.
Users with custom data retention policies enabled might be unable to see or load older messages. We apologize for the trouble and we'll share more news as it becomes available.
Title: We're looking into a potential problem impacting Microsoft 365 Copilot Chat User impact: We're checking for potential impact to your users. Current status: We're investigating a potential issue impacting Microsoft 365 Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.
We are investigating a system issue. To protect platform stability, we have limited the volume of collected data. Expect a visible reduction in data within Performance Monitoring dashboards and BigQuery exports.
We have identified an issue with Azure affecting the Cloud NGFW westeurope and southcentralus regions. Customers may experience failures to during autoscaling and during deployment of new resources. Current Status: Azure is currently experiencing compute capacity issues within the regions. This is impacting our ability to scale out new virtual machines. Ongoing Actions: Our engineering team is monitoring the provider’s recovery efforts and is prepared to validate service health as soon as infrastructure stabilizes. Next Update: July 13th, 8:00UTC
Anthropic’s announcement of Claude Mythos underscores a reality Salesforce has been preparing for: increasingly capable frontier AI models will continue to accelerate the evolution of the cybersecurity landscape. Our security teams are continuously evaluating how frontier models like Mythos may change attacker and defender capabilities, and we are applying those insights to strengthen our security posture and guide continued enhancements across our environment. We view this as an acceleration of work already underway, not a departure from it. Salesforce has long invested in automation and AI to help identify risk, strengthen defenses, and support the trust our customers place in us. Trust remains our #1 value, and we remain focused on helping protect our customers’ data in a rapidly evolving threat environment.
We are investigating increased API error rates in a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region.
We are investigating issues with AWS services in the ME-CENTRAL-1 Region.
Our team is investigating an emerging service issue affecting booting up GPU plans. We will share additional updates as we have more information.
Where our outage data comes from, and how we treat it.
We watch the status pages of the major providers around the clock, so you do not have to check twenty of them.
Every entry comes from an incident reported for that provider. No guess work at play.
Each entry names the provider and the time it was reported, in UTC, so you can check it against their own status page.
Some providers never close an incident. We stop showing an incident as ongoing after 3 days rather than let it run forever.
There's nothing to install. No credit card required. 50 monitors for free.
