← Back to Salesforce's check readings
We started checking Salesforce on August 20, 2026, which is 66 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Salesforce reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Salesforce's own status page declared. Below it, any public chatter we saw about Salesforce and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Salesforce's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, auth (primary)
Unverified user reportsNo reports about Salesforce in the last 24 hours, which is not evidence that nothing is wrong.
Salesforce's status pageService disruption on 15 instances: partial outageService disruption on 16 instances: partial outageService disruption on 35 instances: partial outage- Service disruption on 15 instances: partial outage, from before this window to 06:30 UTC.
- Service disruption on 16 instances: partial outage, from before this window to 05:45 UTC.
- Service disruption on 35 instances: partial outage, from before this window to 06:15 UTC.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Salesforce's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Salesforce next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Their declared record
Salesforce's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Service disruption on 35 instancesPartial outage
Oct 23, 2026, 1:25 AM UTC to Oct 23, 2026, 6:10 AM UTC (4h 45m)resolved
their latest update (Oct 23, 2026, 6:35 AM UTC): We have resolved an issue that prevented users from logging in. We identified an issue with a recent release that prevented login sessions from being created. We deployed a fix forward, and access is now restored. Users can log in and open their orgs again.
We apologize for how …
Service disruption on 12 instancesPartial outage
Oct 23, 2026, 1:25 AM UTC
their latest update (Oct 23, 2026, 6:54 AM UTC): The fix-forward deployment continues to progress well, bringing additional impacted instances closer to recovery. Our teams remain focused on completing the rollout across the remaining instances and validating that users can successfully log in and access their orgs.
As we confi…
Service disruption on 15 instancesPartial outage
Oct 23, 2026, 1:25 AM UTC to Oct 23, 2026, 6:30 AM UTC (5h 5m)resolved
their latest update (Oct 23, 2026, 6:46 AM UTC): We have resolved an issue that prevented users from logging in. We identified an issue with a recent release that prevented login sessions from being created. We deployed a fix forward, and access is now restored. Users can log in and open their orgs again.
We apologize for how …
Service disruption on 16 instancesPartial outage
Oct 23, 2026, 1:25 AM UTC to Oct 23, 2026, 5:33 AM UTC (4h 8m)resolved
their latest update (Oct 23, 2026, 5:56 AM UTC): We resolved an issue that prevented users from logging in. We identified an issue with a recent release that prevented login sessions from being created. We deployed a fix forward, and access is now restored. Users can log in and open their orgs again.
We apologize for how this …
Feature perf degradation on 21 instancesMinor incident
Oct 21, 2026, 12:25 AM UTC to Oct 21, 2026, 2:07 AM UTC (1h 42m)resolved
their latest update (Oct 21, 2026, 3:30 AM UTC): Agentforce Coworker is now operating at normal service levels. Requests are completing successfully again. Error rates returned to normal after a third-party service provider recovered their services.
We apologize for how this incident affected you and your business. We will und…
Feature perf degradation on 21 instancesMinor incident
Oct 20, 2026, 4:04 AM UTC to Oct 20, 2026, 10:45 AM UTC (6h 41m)resolved
their latest update (Oct 20, 2026, 10:57 AM UTC): We restored email delivery by rolling back a recent change to an email service component. Customers now receive all new password reset and one-time passcode (OTP) emails.
Some delayed emails remain queued, and we're flushing those queues so it delivers sooner.
We'll perform a…
Performance degradation on 84 instancesMinor incident
Oct 9, 2026, 10:14 PM UTC to Oct 9, 2026, 10:51 PM UTC (37 min)resolved
their latest update (Oct 9, 2026, 11:40 PM UTC): We’ve investigated and confirmed resolution of a third party performance degradation that impacted multiple Salesforce instances. Impacted customers may have experienced latency and errors. We apologize for how this incident affected you and your business. We will undertake a ful…
Performance degradation on 96 instancesMinor incident
Oct 8, 2026, 10:52 AM UTC to Oct 8, 2026, 3:18 PM UTC (4h 26m)resolved
their latest update (Oct 8, 2026, 7:32 PM UTC): Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
Feature service disruption on 34 instancesMinor incident
Oct 7, 2026, 6:00 PM UTC to Oct 8, 2026, 10:21 PM UTC (1d 4h)resolved
their latest update (Oct 8, 2026, 10:29 PM UTC): We’ve resolved an issue affecting CRM Analytics recipe runs for a number of customers, preventing recipes from completing successfully. We rolled back the affected service to a prior stable version, and recipe runs have now returned to normal. We apologize for how this incident a…
Feature service disruption on 398 instancesMinor incident
Sep 25, 2026, 8:55 PM UTC to Sep 26, 2026, 6:46 PM UTC (21h 51m)resolved
their latest update (Oct 2, 2026, 9:25 PM UTC): Between 20:55 UTC on September 25 and 18:46 UTC on September 26, customers using the Microsoft Teams connector may have been unable to authenticate or maintain their connection. Our team traced the issue to an expired authentication credential, immediately issued a new one, and r…
Showing the 10 most recent of 11 incidents Salesforce has declared in the history we hold.
These entries are Salesforce's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Salesforce's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.