Live  /  Providers  /  Luma Labs

Luma Labs

lumalabs.aiNo open incidents

Independent assessment — SquidGrid is not affiliated with Luma Labs. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

AI · SquidGrid tracks Luma Labs’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Luma Labs is reporting

Current & recent incidents

Resolved

Ray2 increased queue times

Incident impact · 2026-09-17 01:00 UTC

Resolved

Ray2 increased queue times

Minor impact · 2026-09-17 01:00 UTC

Resolved

Ray2 Flash service degraded

Minor impact · 2026-09-16 00:00 UTC

Resolved

Ray2 Flash service degraded

Incident impact · 2026-09-16 00:00 UTC

Resolved

Ray2 Flash service degraded

Minor impact · 2026-09-03 02:00 UTC

Resolved

Ray2 Flash service degraded

Incident impact · 2026-09-03 02:00 UTC

Resolved

Authentication degraded: upstream provider issue

Minor impact · 2026-07-16 10:11 UTC

Resolved

Authentication degraded: upstream provider issue

Incident impact · 2026-07-16 10:11 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what Luma Labs has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Luma Labs runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Luma Labs is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Luma Labs.