Grade One Press

Technology reporting you can check

News · Security & privacy

Salesforce customers faced severe delays and errors for more than seven hours, across all regions

Requests stalled on an internal login service. Salesforce says the fix held from 15:26 UTC, and that it will publish the cause after a full investigation.

Catching up: the original came out on . This story was published later, when the site opened.

Grade One Newsroom · 1 min read

Sources: 1 · top grade 3How evidence is graded

A Salesforce outage caused severe delays and errors for more than seven hours

Grade 3 · Filed record

Source: Salesforce Trust

What changed
Salesforce reported a major service disruption from 07:50 to 15:26 UTC on 16 September, with severe delays, errors and loss of access to some services.
Who it affects
Salesforce customers on some of its Hyperforce cloud instances; the company later said the impact was narrower than first understood.
What it does not tell you
How many customers were affected, or what the root cause was. Salesforce says it will investigate and has not published either.

The full story Check the source

Salesforce recorded a major service disruption from 07:50 to 15:26 UTC on 16 September, in which customers faced severe delays, intermittent errors and an inability to reach some services, according to its status record [1].

Some customers also could not open new support cases through its help portal [1].

Early in the incident, Salesforce said requests were stalling while waiting on an internal login service, using up server resources. It later described increased load on a core system component that limited its capacity [1].

What it covers

Salesforce's core service. The record first listed 595 instances across all regions [1].

Salesforce later said the impact was narrower: a subset of its Hyperforce instances. Sandboxes and its own first-party environments were not affected [1].

The company rolled out a fix region by region from about 11:19 UTC and restarted by hand the instances where it did not take. Some customers reported scheduled jobs not running after access returned [1].

What it does not tell you

How many customers were affected, or for how long each. The record does not say [1].

The underlying cause. Salesforce says it will investigate the technical trigger and root cause [1].

Sources and their grades

  1. Salesforce Trust, Salesforce Trust status, incident 20004433 (16 September 2026). Read 29 September 2026. Grade 3 · Filed record Salesforce's own incident record, read through its status API; the times and descriptions are its own.

A grade says how much weight a source will take, from 1 (a body that can compel an answer and has nothing to sell) to 5 (somebody describing what they sell, or themselves). The standard sets out what each grade may be used for.

Filed under Cloud Outages

Comments

Commenting needs an account, made with nothing but an email address. A first comment is read before it appears.

More news

See all