User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is Level down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → level.io—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 2 hr ago. Last stored result reached it in 107 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 114 ms | 0 |
| Mon 13 | 0 | 0.0 | 146 ms | 0 |
| Mon 15 | 0 | 0.0 | 108 ms | 0 |
| Mon 18 | 0 | 0.0 | 126 ms | 0 |
| Mon 20 | 0 | 0.0 | 139 ms | 0 |
| Mon 22 | 0 | 0.0 | 132 ms | 0 |
| Tue 00 | 0 | 0.0 | 93 ms | 0 |
| Tue 02 | 0 | 0.0 | 186 ms | 0 |
| Tue 04 | 0 | 0.0 | 99 ms | 0 |
| Tue 06 | 0 | 0.0 | 224 ms | 0 |
| Tue 08 | 0 | 0.0 | 62 ms | 0 |
| Tue 10 | 0 | 0.0 | 72 ms | 0 |
| Tue 13 | 0 | 0.0 | 73 ms | 0 |
| Tue 15 | 0 | 0.0 | 200 ms | 0 |
| Tue 17 | 0 | 0.0 | 174 ms | 0 |
| Tue 19 | 0 | 0.0 | 216 ms | 0 |
| Tue 22 | 0 | 0.0 | 81 ms | 0 |
| Wed 00 | 0 | 0.0 | 103 ms | 0 |
| Wed 02 | 0 | 0.0 | 223 ms | 0 |
| Wed 04 | 0 | 0.0 | 89 ms | 0 |
| Wed 07 | 0 | 0.0 | 89 ms | 0 |
| Wed 09 | 0 | 0.0 | 81 ms | 0 |
| Wed 11 | 0 | 0.0 | 133 ms | 0 |
| Wed 13 | 0 | 0.0 | 141 ms | 0 |
| Wed 15 | 0 | 0.0 | 95 ms | 0 |
| Wed 17 | 0 | 0.0 | 229 ms | 0 |
| Wed 20 | 0 | 0.0 | 221 ms | 0 |
| Wed 22 | 0 | 0.0 | 113 ms | 0 |
| Thu 00 | 0 | 0.0 | 102 ms | 0 |
| Thu 02 | 0 | 0.0 | 133 ms | 0 |
| Thu 04 | 0 | 0.0 | 125 ms | 0 |
| Thu 06 | 0 | 0.0 | 223 ms | 0 |
| Thu 08 | 0 | 0.0 | 243 ms | 0 |
| Thu 10 | 0 | 0.0 | 93 ms | 0 |
| Thu 12 | 0 | 0.0 | 95 ms | 0 |
| Thu 15 | 0 | 0.0 | 126 ms | 0 |
| Thu 17 | 0 | 0.0 | 257 ms | 0 |
| Thu 19 | 0 | 0.0 | 497 ms | 0 |
| Thu 20 | 0 | 0.0 | 81 ms | 0 |
| Thu 22 | 0 | 0.0 | 283 ms | 0 |
| Fri 00 | 0 | 0.0 | 114 ms | 0 |
| Fri 02 | 0 | 0.0 | 152 ms | 0 |
| Fri 04 | 0 | 0.0 | 104 ms | 0 |
| Fri 06 | 0 | 0.0 | 84 ms | 0 |
| Fri 09 | 0 | 0.0 | 183 ms | 0 |
| Fri 10 | 0 | 0.0 | 379 ms | 0 |
| Fri 11 | 0 | 0.0 | 108 ms | 0 |
| Fri 13 | 0 | 0.0 | 107 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Level badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Level yet. Outages of 10 minutes or more get their own page here.
Having trouble with Level?
One report per service every 10 minutes from this network. No account.
Follow Level
Get an email when Level goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Level alerts to Slack, Discord or a webhook — free.
About Level
Level is listed in our Cloud & developer category and checked at level.io. See what needs attention, automate routine work, patch on your schedule, and remote in when you need to. RMM for Windows, macOS, and Linux. First 10 devices free.
Level publishes an official status page at status.level.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: 196 ms average, 81–497 ms range across 12 successful checks.
Questions
Is Level down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Level last down?
We have not recorded a public Level incident since monitoring began 8 days ago.
What is Level's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Level respond?
196 ms on average over the last 24 hours (81–497 ms).
Does Level have an official status page?
Yes, at https://status.level.io.
Level not working for me but the status is fine. What now?
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 Level here at once, the problem is on Level'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 Level. 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.