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 114 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 01 | 0 | 0.0 | 75 ms | 0 |
| Tue 03 | 0 | 0.0 | 110 ms | 0 |
| Tue 05 | 0 | 0.0 | 122 ms | 0 |
| Tue 07 | 0 | 0.0 | 54 ms | 0 |
| Tue 09 | 0 | 0.0 | 142 ms | 0 |
| Tue 11 | 0 | 0.0 | 163 ms | 0 |
| Tue 13 | 0 | 0.0 | 112 ms | 0 |
| Tue 16 | 0 | 0.0 | 58 ms | 0 |
| Tue 18 | 0 | 0.0 | 123 ms | 0 |
| Tue 20 | 0 | 0.0 | 122 ms | 0 |
| Tue 22 | 0 | 0.0 | 109 ms | 0 |
| Wed 01 | 0 | 0.0 | 44 ms | 0 |
| Wed 03 | 0 | 0.0 | 81 ms | 0 |
| Wed 05 | 0 | 0.0 | 128 ms | 0 |
| Wed 07 | 0 | 0.0 | 104 ms | 0 |
| Wed 10 | 0 | 0.0 | 161 ms | 0 |
| Wed 12 | 0 | 0.0 | 120 ms | 0 |
| Wed 14 | 0 | 0.0 | 116 ms | 0 |
| Wed 16 | 0 | 0.0 | 145 ms | 0 |
| Wed 18 | 0 | 0.0 | 231 ms | 0 |
| Wed 20 | 0 | 0.0 | 138 ms | 0 |
| Wed 23 | 0 | 0.0 | 121 ms | 0 |
| Thu 01 | 0 | 0.0 | 96 ms | 0 |
| Thu 03 | 0 | 0.0 | 228 ms | 0 |
| Thu 05 | 0 | 0.0 | 126 ms | 0 |
| Thu 07 | 0 | 0.0 | 105 ms | 0 |
| Thu 09 | 0 | 0.0 | 109 ms | 0 |
| Thu 11 | 0 | 0.0 | 60 ms | 0 |
| Thu 13 | 0 | 0.0 | 102 ms | 0 |
| Thu 15 | 0 | 0.0 | 57 ms | 0 |
| Thu 17 | 0 | 0.0 | 111 ms | 0 |
| Thu 19 | 0 | 0.0 | 185 ms | 0 |
| Thu 21 | 0 | 0.0 | 115 ms | 0 |
| Thu 23 | 0 | 0.0 | 50 ms | 0 |
| Fri 02 | 0 | 0.0 | 51 ms | 0 |
| Fri 04 | 0 | 0.0 | 55 ms | 0 |
| Fri 06 | 0 | 0.0 | 34 ms | 0 |
| Fri 08 | 0 | 0.0 | 39 ms | 0 |
| Fri 10 | 0 | 0.0 | 108 ms | 0 |
| Fri 11 | 0 | 0.0 | 147 ms | 0 |
| Fri 13 | 0 | 0.0 | 53 ms | 0 |
| Fri 15 | 0 | 0.0 | 143 ms | 0 |
| Fri 17 | 0 | 0.0 | 50 ms | 0 |
| Fri 19 | 0 | 0.0 | 101 ms | 0 |
| Fri 20 | 0 | 0.0 | 213 ms | 0 |
| Fri 22 | 0 | 0.0 | 57 ms | 0 |
| Sat 00 | 0 | 0.0 | 125 ms | 0 |
| Sat 01 | 0 | 0.0 | 114 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for LANDR 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 LANDR goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send LANDR alerts to Slack, Discord or a webhook — free.
We track LANDR (landr.com) as part of the AI group. Everything you need to create and release music. Industry-leading AI mastering, distribution, plugins, samples, collaboration tools & courses, all in one place.
LANDR publishes an official status page at status.landr.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 92 ms average, 7–213 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 LANDR incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
92 ms on average over the last 24 hours (7–213 ms).
Yes, at https://status.landr.com.
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 LANDR here at once, the problem is on LANDR'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 LANDR. 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.