Outage Status Now

Guides / Salesforce login issues, MFA loops, or blank Lightning page

Part of: Business apps slow or won't load

Last reviewed · By

Salesforce login issues, MFA loops, or blank Lightning page

Cannot log into Salesforce, stuck in MFA, or Lightning loads blank? Split a Salesforce incident from SSO, IP restrictions and browser problems.

Sales cannot get into Salesforce. The login page loops, MFA never finishes, or Lightning UI paints a blank shell. Someone posts in the company chat: "Is Salesforce down?" Sometimes yes. More often it is My Domain, SSO, an IP restriction, or a browser profile that has been accumulating cookies since 2019.

Is Salesforce down?

Open status.salesforce.com and pick your instance (for example NA86, EU46). Salesforce incidents are instance-scoped; a red NA pod does not excuse a quiet EU pod. We do not invent a Salesforce tile — use their board, then our URL checker against your My Domain host if you need an outside path test. If Salesforce has posted for your instance, stop resetting passwords and wait.

User checks

  1. Private window on LTE. If that works, office proxy, SSL inspection or a sick browser profile is to blame.
  2. My Domain URL. Bookmark https://yourcompany.my.salesforce.com (or the Experience Cloud domain your admin documented). The generic login.salesforce.com path plus the wrong portal confuses people after migrations.
  3. SSO vs direct login. If your company uses Okta or Entra for Salesforce, a broken IdP session looks like Salesforce being down. Try another SSO app. See Okta SSO.
  4. MFA. Salesforce Authenticator, email OTP, or IdP MFA can fail independently. If the push never arrives, fix the factor — see Okta Verify push when Okta is in the path.
  5. Password lockout. Repeated failures lock the user. An admin must unlock in Setup → users; more password attempts make it worse.
  6. Lightning vs Classic. A blank Lightning page with Classic still working points to browser compatibility, blocked scripts, or a broken Lightning component — not the core login service.

Admin causes

Evidence for Salesforce support

Capture: instance ID, My Domain, time with time zone, screenshot of the exact error, whether SSO or direct login, browser and OS, and whether status.salesforce.com was green. Login History under Setup shows failure reasons (invalid password, IP restricted, SAML failure) — read that before guessing.

When to escalate

Escalate to Salesforce when your instance is red on their status page or Login History shows platform errors for many users. Escalate to identity when only SSO users fail. Escalate to networking when only one egress IP fails IP restrictions. One locked user is an unlock, not an outage bridge.

Related status pages

Related guides

FAQ

Why can I not log into Salesforce?
Check status.salesforce.com for your instance first. Then try a private window on LTE, confirm My Domain, and verify SSO or MFA is working. Lockouts and IP restrictions are common.
Why does Salesforce work in the office but not at home?
Login IP ranges on the profile often allow only office addresses. Connect the company VPN or ask an admin to adjust trusted networks.
Is a blank Lightning page an outage?
Usually not. Try Classic, another browser, and disable extensions. If the whole instance is red on status.salesforce.com, then treat it as an incident.
Does Okta being down take Salesforce with it?
If Salesforce login is federated through Okta, yes for SSO users. Direct login users and some Experience Cloud users may still work. Fix or wait on the IdP.

Did this help?

Still broken? Check another tool