Vendor reports: operationalResolved · vendor status “resolved”Official status API
Unable to Access LastPass
Reported by LastPass · Identity & Security · source last read just now
- Vendor start
- Dec 11, 2024, 15:58 UTC
- Vendor's clock
- Resolved
- Dec 11, 2024, 16:52 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 53 min
- From vendor start and resolution
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
What is unknown
Last update in these facts: 2024-12-11 16:52 UTC · summary s1, evidence 37da089a24a164fd
Evidence (7)
- E1LastPass reports operational. (vendor) source (opens in a new tab)
- E2Vendor title: "Unable to Access LastPass". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2024-12-11 15:58 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6The vendor attached no components. (Statuswall)
- E7Vendor-reported resolution: 2024-12-11 16:52 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: not stated by the vendor
No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.
Potential relevance
LastPass is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Dec 11, 2024, 15:58 UTCVendor-reported startVendor time
- Dec 11, 2024, 16:52 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.