User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 96 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Thu 02 | 0 | 0.0 | 111 ms | 0 |
| Thu 04 | 0 | 0.0 | 49 ms | 0 |
| Thu 06 | 0 | 0.0 | 57 ms | 0 |
| Thu 08 | 0 | 0.0 | 51 ms | 0 |
| Thu 10 | 0 | 0.0 | 68 ms | 0 |
| Thu 13 | 0 | 0.0 | 56 ms | 0 |
| Thu 15 | 0 | 0.0 | 59 ms | 0 |
| Thu 17 | 0 | 0.0 | 83 ms | 0 |
| Thu 19 | 0 | 0.0 | 35 ms | 0 |
| Thu 21 | 0 | 0.0 | 68 ms | 0 |
| Thu 23 | 0 | 0.0 | 74 ms | 0 |
| Fri 01 | 0 | 0.0 | 71 ms | 0 |
| Fri 03 | 0 | 0.0 | 285 ms | 0 |
| Fri 05 | 0 | 0.0 | 49 ms | 0 |
| Fri 07 | 0 | 0.0 | 57 ms | 0 |
| Fri 09 | 0 | 0.0 | 32 ms | 0 |
| Fri 11 | 0 | 0.0 | 39 ms | 0 |
| Fri 13 | 0 | 0.0 | 28 ms | 0 |
| Fri 15 | 0 | 0.0 | 78 ms | 0 |
| Fri 17 | 0 | 0.0 | 73 ms | 0 |
| Fri 19 | 0 | 0.0 | 70 ms | 0 |
| Fri 20 | 0 | 0.0 | 87 ms | 0 |
| Fri 22 | 0 | 0.0 | 43 ms | 0 |
| Sat 00 | 0 | 0.0 | 65 ms | 0 |
| Sat 02 | 0 | 0.0 | 51 ms | 0 |
| Sat 04 | 0 | 0.0 | 80 ms | 0 |
| Sat 07 | 0 | 0.0 | 52 ms | 0 |
| Sat 09 | 0 | 0.0 | 29 ms | 0 |
| Sat 11 | 0 | 0.0 | 41 ms | 0 |
| Sat 14 | 0 | 0.0 | 61 ms | 0 |
| Sat 15 | 0 | 0.0 | 49 ms | 0 |
| Sat 18 | 0 | 0.0 | 36 ms | 0 |
| Sat 20 | 0 | 0.0 | 35 ms | 0 |
| Sat 22 | 0 | 0.0 | 64 ms | 0 |
| Sun 00 | 0 | 0.0 | 52 ms | 0 |
| Sun 03 | 0 | 0.0 | 38 ms | 0 |
| Sun 05 | 0 | 0.0 | 45 ms | 0 |
| Sun 06 | 0 | 0.0 | 75 ms | 0 |
| Sun 07 | 0 | 0.0 | 75 ms | 0 |
| Sun 09 | 0 | 0.0 | 35 ms | 0 |
| Sun 11 | 0 | 0.0 | 58 ms | 0 |
| Sun 13 | 0 | 0.0 | 43 ms | 0 |
| Sun 16 | 0 | 0.0 | 43 ms | 0 |
| Sun 18 | 0 | 0.0 | 48 ms | 0 |
| Sun 20 | 0 | 0.0 | 52 ms | 0 |
| Sun 21 | 0 | 0.0 | 127 ms | 0 |
| Sun 22 | 0 | 0.0 | 71 ms | 0 |
| Mon 00 | 0 | 0.0 | 96 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 11 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Lumana yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Lumana goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
We track Lumana (lumana.ai) as part of the AI group. Lumana provides a hybrid cloud video security and video surveillance system powered by agentic AI to help improve physical security, safety, and operations
Lumana publishes an official status page at status.lumana.ai; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 11 days of checks. No public incidents logged since monitoring began 11 days ago.
Response time over the last 24 hours: 60 ms average, 30–127 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Lumana incident since monitoring began 11 days ago.
From our own checks: 100% over 11 days of checks.
60 ms on average over the last 24 hours (30–127 ms).
Yes, at https://status.lumana.ai.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Lumana here at once, the problem is on Lumana's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Lumana. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.