Loading status…
Loading status…
Salesforce status · SaaS · checked (1s ago)
Also searched as Sales Cloud, Service Cloud, Salesforce Trust.
Partly — Salesforce is up but running slower than usual (Degraded Performance: 1 active incident).
According to Salesforce's official status page, Salesforce was reporting “Degraded Performance: 1 active incident” when isuptime last checked at . Over the last 30 days, Salesforce's feed reported no outage in 94.82% of our checks.
isuptime cannot fix Salesforce, and neither can you. These are the things that are actually worth doing until it comes back.
Status shown for each is read from that provider's own feed, on the same schedule as this page.
Everything above is read from Salesforce's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Salesforce in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Salesforce is the largest CRM platform — Sales Cloud, Service Cloud, Marketing Cloud, Experience Cloud and the Lightning Platform that custom applications are built on. Most large enterprises run a substantial part of their commercial operation on it.
Salesforce runs thousands of numbered instances and publishes status per instance, which makes a single ordinary incident touch hundreds of instances at once. Counting instances would report a routine degradation as a catastrophe, so isuptime reads Salesforce's active-incident feed instead: one entry per incident, graded by Salesforce's own vocabulary of degradation versus disruption and minor versus major impact. Your own instance may or may not be among those affected — Salesforce Trust will tell you, this page cannot.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Salesforce's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Salesforce was down.
13 other services isuptime tracks were also reporting a problem as of the same check, 1s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Salesforce's status endpoint.
Every incident Salesforce has published in the last 12 months.
Salesforce has not published a single incident in the last 12 months. That is a statement about Salesforce's posting habits as much as its reliability — a status page only records what its owner decides to record.
Find your instance name in Setup and check it specifically on Trust; an incident affecting other instances is genuinely irrelevant to you. Governor limits, API request caps and a full sandbox refresh queue all produce errors that look like platform faults. A failing Apex job or a validation rule change is your org's configuration, and it will never appear on any Salesforce status page.