User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
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 1 hr ago. Last stored result reached it in 506 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 10 | 0 | 0.0 | 1285 ms | 0 |
| Mon 12 | 0 | 0.0 | 1398 ms | 0 |
| Mon 15 | 0 | 0.0 | 1836 ms | 0 |
| Mon 17 | 0 | 0.0 | 1455 ms | 0 |
| Mon 19 | 0 | 0.0 | 1162 ms | 0 |
| Mon 21 | 0 | 0.0 | 1439 ms | 0 |
| Mon 23 | 0 | 0.0 | 650 ms | 0 |
| Tue 01 | 0 | 0.0 | 558 ms | 0 |
| Tue 03 | 0 | 0.0 | 1149 ms | 0 |
| Tue 05 | 0 | 0.0 | 1158 ms | 0 |
| Tue 07 | 0 | 0.0 | 1240 ms | 0 |
| Tue 10 | 0 | 0.0 | 1285 ms | 0 |
| Tue 12 | 0 | 0.0 | 894 ms | 0 |
| Tue 14 | 0 | 0.0 | 1178 ms | 0 |
| Tue 16 | 0 | 0.0 | 1584 ms | 0 |
| Tue 18 | 0 | 0.0 | 1316 ms | 0 |
| Tue 21 | 0 | 0.0 | 930 ms | 0 |
| Tue 23 | 0 | 0.0 | 1143 ms | 0 |
| Wed 01 | 0 | 0.0 | 1032 ms | 0 |
| Wed 03 | 0 | 0.0 | 1238 ms | 0 |
| Wed 06 | 0 | 0.0 | 920 ms | 0 |
| Wed 08 | 0 | 0.0 | 763 ms | 0 |
| Wed 10 | 0 | 0.0 | 590 ms | 0 |
| Wed 12 | 0 | 0.0 | 1315 ms | 0 |
| Wed 14 | 0 | 0.0 | 1698 ms | 0 |
| Wed 16 | 0 | 0.0 | 1231 ms | 0 |
| Wed 19 | 0 | 0.0 | 1714 ms | 0 |
| Wed 21 | 0 | 0.0 | 703 ms | 0 |
| Wed 23 | 0 | 0.0 | 1191 ms | 0 |
| Thu 01 | 0 | 0.0 | 1550 ms | 0 |
| Thu 03 | 0 | 0.0 | 654 ms | 0 |
| Thu 05 | 0 | 0.0 | 1307 ms | 0 |
| Thu 07 | 0 | 0.0 | 1184 ms | 0 |
| Thu 09 | 0 | 0.0 | 1060 ms | 0 |
| Thu 12 | 0 | 0.0 | 628 ms | 0 |
| Thu 14 | 0 | 0.0 | 946 ms | 0 |
| Thu 16 | 0 | 0.0 | 1646 ms | 0 |
| Thu 18 | 0 | 0.0 | 661 ms | 0 |
| Thu 20 | 0 | 0.0 | 758 ms | 0 |
| Thu 22 | 0 | 0.0 | 1360 ms | 0 |
| Fri 00 | 0 | 0.0 | 1447 ms | 0 |
| Fri 02 | 0 | 0.0 | 1334 ms | 0 |
| Fri 04 | 0 | 0.0 | 644 ms | 0 |
| Fri 06 | 0 | 0.0 | 891 ms | 0 |
| Fri 08 | 0 | 0.0 | 1182 ms | 0 |
| Fri 10 | 0 | 0.0 | 1043 ms | 0 |
| Fri 12 | 0 | 0.0 | 1004 ms | 0 |
| Fri 14 | 0 | 0.0 | 506 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Lumar 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 Lumar goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Lumar alerts to Slack, Discord or a webhook — free.
Lumar is listed in our Cloud & developer category and checked at lumar.io. The ultimate website optimization platform with tools for tech SEO, GEO, web accessibility, site speed, & more, built for enterprise scale.
Lumar publishes an official status page at status.lumar.io; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 1032 ms average, 475–1646 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Lumar incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
1032 ms on average over the last 24 hours (475–1646 ms).
Yes, at https://status.lumar.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Lumar here at once, the problem is on Lumar'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 Lumar. 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.