- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 100
What to do
Check whether your product depends on Luma AI. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 45m it lasted.
Anything that failed between 2026-07-16 08:26 UTC and 2026-07-16 10:11 UTC may need a replay.Subscribe to Luma AI's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=luma works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Luma AI 2
- update
We're experiencing degraded authentication across some of our applications due to an ongoing incident with our upstream identity provider/ Users may see slow or failed logins, including SSO. Existing sessions are not affected. We're monitoring the provider's status and will update as soon as service is restored.
provider
- resolved
The upstream auth provider issue has been resolved. Logins and SSO are back to normal across all apps. We've confirmed recovery and will continue monitoring.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-a7d12db503
Is Luma AI still down?
No, this incident was resolved 2026-07-16 10:11 UTC. For Luma AI's live state, see https://down.guide/luma.
How long did it last?
1h 45m, from 2026-07-16 08:26 UTC to 2026-07-16 10:11 UTC, by the times Luma AI posted.
What caused it?
Luma AI hasn't published a root cause. If it does, it shows here.
Where does this come from?
Luma AI's official status page, https://status.lumalabs.ai, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.