- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 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 3h 30m it lasted.
Anything that failed between 2026-01-17 16:30 UTC and 2026-01-17 20:00 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 3
- update
we are observing high queue times for Ray3 and Ray2
provider
- update
ray2 queue is back to normal
provider
- resolved
back to normal
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-38c56f96b5
Is Luma AI still down?
No, this incident was resolved 2026-01-17 20:00 UTC. For Luma AI's live state, see https://down.guide/luma.
How long did it last?
3h 30m, from 2026-01-17 16:30 UTC to 2026-01-17 20:00 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.