User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
mage.space · AI
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Plum is down; Magejutsu is degraded | Plum is down; Magejutsu is degraded | Plum is down; Magejutsu is degraded | Plum is down; Magejutsu is degraded | Plum is down; Magejutsu i...
Source: the vendor's status page · We are not affiliated with Mage.
Estimated fix: Not enough Mage history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
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 53 min ago. Last stored result reached it in 68 ms.
Minor incident
Plum is down; Magejutsu is degraded | Plum is down; Magejutsu is degraded | Plum is down; Magejutsu is degraded | Plum is down; Magejutsu is degraded | Plum is down; Magejutsu is degraded | Plum is down; Magejutsu is degraded | Plum is down; Magejutsu is degraded | Plum is down; Magejutsu is degrade Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 137 ms | 0 |
| Mon 15 | 0 | 0.0 | 142 ms | 0 |
| Mon 18 | 0 | 0.0 | 133 ms | 0 |
| Mon 20 | 0 | 0.0 | 149 ms | 0 |
| Mon 22 | 0 | 0.0 | 88 ms | 0 |
| Tue 00 | 0 | 0.0 | 73 ms | 0 |
| Tue 02 | 0 | 0.0 | 82 ms | 0 |
| Tue 04 | 0 | 0.0 | 158 ms | 0 |
| Tue 06 | 0 | 0.0 | 92 ms | 0 |
| Tue 08 | 0 | 0.0 | 77 ms | 0 |
| Tue 11 | 0 | 0.0 | 158 ms | 0 |
| Tue 13 | 0 | 0.0 | 73 ms | 0 |
| Tue 15 | 0 | 0.0 | 100 ms | 0 |
| Tue 17 | 0 | 0.0 | 91 ms | 0 |
| Tue 19 | 0 | 0.0 | 228 ms | 0 |
| Tue 22 | 0 | 0.0 | 78 ms | 0 |
| Wed 00 | 0 | 0.0 | 89 ms | 0 |
| Wed 02 | 0 | 0.0 | 95 ms | 0 |
| Wed 04 | 0 | 0.0 | 88 ms | 0 |
| Wed 07 | 0 | 0.0 | 100 ms | 0 |
| Wed 09 | 0 | 0.0 | 112 ms | 0 |
| Wed 11 | 0 | 0.0 | 120 ms | 0 |
| Wed 13 | 0 | 0.0 | 105 ms | 0 |
| Wed 15 | 0 | 0.0 | 100 ms | 0 |
| Wed 17 | 0 | 0.0 | 129 ms | 0 |
| Wed 20 | 0 | 0.0 | 472 ms | 0 |
| Wed 22 | 0 | 0.0 | 68 ms | 0 |
| Thu 00 | 0 | 0.0 | 89 ms | 0 |
| Thu 02 | 0 | 0.0 | 166 ms | 0 |
| Thu 04 | 0 | 0.0 | 76 ms | 0 |
| Thu 06 | 0 | 0.0 | 79 ms | 0 |
| Thu 08 | 0 | 0.0 | 94 ms | 0 |
| Thu 10 | 0 | 0.0 | 145 ms | 0 |
| Thu 12 | 0 | 0.0 | 141 ms | 0 |
| Thu 14 | 0 | 0.0 | 116 ms | 0 |
| Thu 16 | 0 | 0.0 | 177 ms | 0 |
| Thu 18 | 0 | 0.0 | 100 ms | 0 |
| Thu 20 | 0 | 0.0 | 137 ms | 0 |
| Thu 22 | 0 | 0.0 | 68 ms | 0 |
| Fri 00 | 0 | 0.0 | 126 ms | 0 |
| Fri 02 | 0 | 0.0 | 147 ms | 0 |
| Fri 05 | 0 | 0.0 | 99 ms | 0 |
| Fri 07 | 0 | 0.0 | 89 ms | 0 |
| Fri 09 | 0 | 0.0 | 86 ms | 0 |
| Fri 10 | 0 | 0.0 | 143 ms | 0 |
| Fri 12 | 0 | 0.0 | 64 ms | 0 |
| Fri 14 | 0 | 0.0 | 77 ms | 0 |
| Fri 16 | 0 | 0.0 | 68 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 Mage 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 Mage goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Mage alerts to Slack, Discord or a webhook — free.
Mage is listed in our AI category and checked at mage.space. Mage Space: unlimited AI image, video, and audio generation with frontier models in one place. Free to start and private by default.
Mage publishes an official status page at status.mage.space; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 100 ms average, 64–147 ms range across 12 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Plum is down; Magejutsu is degraded | Plum is down; Magejutsu is degraded | Plum is down; Magejutsu is degraded | Plum is down; Magejutsu is degraded | Plum is down; Magejutsu i...
We have not recorded a public Mage incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
100 ms on average over the last 24 hours (64–147 ms).
Yes, at https://status.mage.space.
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 Mage here at once, the problem is on Mage'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 Mage. 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.