Salesforce is restoring service after a global outage on Wednesday, September 16, 2026, that disrupted core Salesforce services across all regions for several hours. If your team is seeing severe delays, intermittent errors, or "down for maintenance" messages this morning, this guide covers what happened and what to do next.
This post tracks Salesforce incident 20004433 ("Service Disruption") with explicit "as of" timestamps, because the situation is still evolving. All incident details are drawn from Salesforce's official status communications — we will not speculate on root cause.
As of 8:00 AM CT on Wednesday, September 16, 2026: Salesforce is rolling out a validated fix for a global service disruption (incident 20004433) that began around 2:50 AM CT. Salesforce says services are returning to normal in regions where the rollout has completed, GovCloud customers are no longer affected, and monitoring continues while a permanent fix is developed. Admins should check their specific instance on the Salesforce Status page, hold non-critical data jobs, communicate a clear status message to users, and plan a post-incident data verification pass before assuming everything is back to normal.
According to Salesforce's status page incident tracker, the disruption began around 2:50 AM CT (3:50 AM ET) on Wednesday, September 16, 2026. Salesforce's incident 20004433, classified as a Service Disruption affecting Core Service, was posted shortly after and updated roughly every 30 minutes through the morning.
The timing made the outage especially visible: it landed on day two of Dreamforce '26, Salesforce's annual conference in San Francisco, which is drawing more than 40,000 in-person attendees and over 200,000 online registrants this week.
In its 4:10 AM CT update, Salesforce said its investigation indicated that "requests are stalling while waiting on a response from an internal login service, which is using up available server resources." A later update at approximately 5:42 AM CT added that increased load on a core system component had limited its capacity to process requests. Beyond those statements, Salesforce has not published a root cause, and this post will not speculate on one.
| Time (CT) | Salesforce status update |
|---|---|
| ~2:50 AM | Disruption begins, per the incident tracker timeline |
| ~3:30 AM | Incident 20004433 posted: severe delays, intermittent errors, inability to access some services |
| ~4:10 AM | Salesforce: requests stalling on an internal login service, consuming server resources; support case creation also affected |
| ~5:09 AM | Salesforce: "no longer pursuing restarts as a path to remediation" |
| ~5:42 AM | Increased load on a core system component identified; fix being tested on one instance |
| ~6:00 AM | Fix validated on a test instance; deployment across all affected instances begins |
| ~6:27 AM | Fix rolling out "fleetwide"; customers seeing service return to normal |
| ~7:00 AM | Deployment proceeding region by region; no confirmed completion time; GovCloud customers no longer affected |
| ~7:27 AM | Services returning to normal in regions where rollout completed; monitoring continues while a permanent fix is developed |
Independent outage tracker Downdetector showed a large spike in user reports through the morning, with the most-reported problems split across website access (69%), the mobile app (16%), and login (15%) — consistent with Salesforce's own description of the incident.
This is a genuinely global incident. Salesforce's status page lists hundreds of affected instances, and reporting from The Register confirms impact across the USA, Japan, India, the UK, France, and Germany — spanning all three of Salesforce's operating regions.
Per Salesforce's Trust site as of 8:00 AM CT:
The important caveat: restoration is rolling out region by region and instance by instance. "Salesforce is back" on social media does not mean your instance is back — the only authoritative answer for your org is your instance's row on the status page.
If your org is still seeing errors, or has just come back online, work this checklist in order:
Outages end, but the next one is always coming. The teams that handle them well run the same playbook every time:
Monitoring. Bookmark status.salesforce.com and know your instance IDs — production and every sandbox. My Trust Center provides status tailored to your specific tenants and is worth setting up before you need it at 3 AM. Downdetector is a useful early signal for "is it us or is it Salesforce," but Salesforce's status communications are the only authoritative source.
Communication. Name one communications owner so updates aren't improvised by whoever is loudest. Use a single channel — a pinned Slack or Teams message or a standing distribution list — and commit to a cadence ("next update at 9:00 AM CT, or sooner if status changes"), then keep it even when the update is "no change." And never promise a restoration time Salesforce hasn't committed to — Salesforce itself had no confirmed completion time as of 7:00 AM CT.
When your instance shows green, the outage is over for users — but not for admins. Intermittent errors and stalled requests during a multi-hour disruption can leave data in an inconsistent state. Before you declare all-clear:
If your team doesn't have the bandwidth or the runbook for this kind of verification pass, that's exactly the gap a managed services partner fills — and it's worth closing before the next incident, not during it.
Vantage Point is a boutique, senior-led Salesforce and HubSpot consulting partner. Our managed services and ongoing support team monitors platform incidents on behalf of clients, runs user communication during outages, and performs the post-incident data verification pass described above — failed-job reruns, duplicate checks, and impact documentation included.
If this morning's outage exposed gaps in your incident runbook, our advisory and change management consultants can help you build a durable outage communication and verification playbook, and our integration and data migration team can harden the sync patterns that turn a platform outage into a data-quality problem.
If your org took data damage during the disruption — stuck integrations, duplicate records, missing cases — Vantage Point's senior consultants can run the verification and cleanup with you. Contact Vantage Point to talk through what you're seeing, or explore our Salesforce services to see how we support orgs before, during, and after incidents like this one.
As of 8:00 AM CT on September 16, 2026, Salesforce says services are returning to normal in regions where its fix has finished deploying, but some customers may still see severe delays and intermittent errors while the rollout completes. The authoritative answer for your org is your instance's current status on status.salesforce.com — restoration is proceeding region by region, so global headlines don't tell you whether your instance is back.
Salesforce lists the incident against Core Service across hundreds of instances in all three operating regions, with confirmed impact reported in the USA, Japan, India, the UK, France, and Germany. MuleSoft, Tableau, Marketing Cloud, Heroku, and Experience Cloud showed as available as of 8:00 AM CT, and GovCloud customers were cleared as of the 7:00 AM CT update.
Salesforce has not published a root cause. Its status updates state that requests were stalling while waiting on a response from an internal login service, consuming server resources, and that increased load on a core system component limited request-processing capacity. Anything beyond those statements is speculation, and we won't add to it — Salesforce typically publishes a post-incident summary after major disruptions.
Salesforce's status updates confirm that support case creation was itself affected by this incident. If you submitted a case during the outage window, don't assume it was received — verify once service stabilizes. For urgent issues during an active incident, contact your Salesforce account team or use premier support channels directly.
Salesforce's communications describe a service availability and performance incident, not a data loss event. The realistic risk is indirect: integrations and automations that partially ran during intermittent errors can leave duplicates, gaps, or half-completed records. Run the post-incident verification checklist above before considering your org back to normal.
Send one message now — confirmed global Salesforce outage, fix deploying, what still works, next update time — then keep the cadence you promised even when nothing changes. Assign a single communications owner, use one pinned channel, and never quote a restoration time Salesforce hasn't committed to. Vantage Point's advisory and change management team helps organizations build this playbook in advance.
Salesforce posts incident updates at status.salesforce.com (search your instance for incident 20004433) and has been updating roughly every 30 minutes during this incident. Salesforce My Trust Center provides tenant-specific status. Third-party trackers like Downdetector are useful early signals but are not authoritative.
Incident details current as of 8:00 AM CT on September 16, 2026. This is an evolving situation — check Salesforce's status page for the latest.
Vantage Point is a boutique CRM consulting firm helping businesses transform with Salesforce, HubSpot, and AI — 150+ clients, 400+ engagements, and a 4.71/5 average engagement rating. Learn more at vantagepoint.io.