Luma AI
AI. Source: Luma AI status page.
History starts 2026-09-02 17:00 UTC, the oldest incident this status page still shows. Figures for the last 90 days cover only the part since then.
- Incidents, last 90 days
- 3+
- Median to mitigation
- not reported
- Median to resolution
- 9h
- p95 to resolution
- 13h
- Naming an upstream provider
- 0%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| The text does not say enough to tell | 2 |
| Exhausted memory, disk, CPU, queues, connection pools or quotas | 1 |
Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.
Incidents per month
Hatched months are before the recorded history starts.
All recorded incidents
Ray2 increased queue times
Affected: API, Dream Machine
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
degraded
we are observing high queue times for Ray2
-
resolved
service is back to normal
Excerpts are shortened. Read the full incident on Luma AI's status page.
Ray2 Flash service degraded
Affected: API, Dream Machine
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
degraded
we’ve observed that ray2-flash jobs are timed out.
-
resolved
service is back to normal
Excerpts are shortened. Read the full incident on Luma AI's status page.
Ray2 Flash service degraded
Affected: API, Dream Machine
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
degraded
we’ve observed that ray2-flash jobs are timed out.
-
resolved
Service is back to normal
Excerpts are shortened. Read the full incident on Luma AI's status page.