Luma AI Outage History
5 incidents recorded over the last 365 days, 5 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Luma AI Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 16, 2026 | Ray2 increased queue times | 1193h 9m | Resolved |
| Sep 15, 2026 | Ray2 Flash service degraded | 1207h 9m | Resolved |
| Sep 2, 2026 | Ray2 Flash service degraded | 1524h 9m | Resolved |
| Jul 16, 2026 | Authentication degraded: upstream provider issue | 1839h 15m | Resolved |
| Jun 22, 2026 | Ray2 flash increased queue times | 1686h 55m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Luma AI incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Luma AI Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Luma AI acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Luma AI outage in this window ran 76d 15h, against a mean recovery of 62d 2h. If you depend on Luma AI in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.