User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
magemojo.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 2415 ms · 9 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 04:30 | 0 | 0.0 | 1883 ms | 0 |
| 04:45 | 0 | 0.0 | 636 ms | 0 |
| 05:00 | 0 | 0.0 | 1735 ms | 0 |
| 05:15 | 0 | 0.0 | 1139 ms | 0 |
| 05:30 | 0 | 0.0 | 361 ms | 0 |
| 05:45 | 0 | 0.0 | 872 ms | 0 |
| 06:00 | 0 | 0.0 | 788 ms | 0 |
| 06:15 | 0 | 0.0 | 1294 ms | 0 |
| 06:30 | 0 | 0.0 | 3755 ms | 0 |
| 06:45 | 0 | 0.0 | 1416 ms | 0 |
| 07:00 | 0 | 0.0 | 1919 ms | 0 |
| 07:15 | 0 | 0.0 | 1615 ms | 0 |
| 07:30 | 0 | 0.0 | 1730 ms | 0 |
| 07:45 | 0 | 0.0 | 368 ms | 0 |
| 08:00 | 0 | 0.0 | 2071 ms | 0 |
| 08:15 | 0 | 0.0 | 975 ms | 0 |
| 08:30 | 0 | 0.0 | 323 ms | 0 |
| 08:45 | 0 | 0.0 | 1531 ms | 0 |
| 09:00 | 0 | 0.0 | 1325 ms | 0 |
| 09:15 | 0 | 0.0 | 706 ms | 0 |
| 09:30 | 0 | 0.0 | 1307 ms | 0 |
| 09:45 | 0 | 0.0 | 3095 ms | 0 |
| 10:00 | 0 | 0.0 | 3171 ms | 0 |
| 10:15 | 0 | 0.0 | 2236 ms | 0 |
| 10:30 | 0 | 0.0 | 1762 ms | 0 |
| 10:45 | 0 | 0.0 | 2702 ms | 0 |
| 11:00 | 0 | 0.0 | 281 ms | 0 |
| 11:15 | 0 | 0.0 | 871 ms | 0 |
| 11:30 | 0 | 0.0 | 1410 ms | 0 |
| 11:45 | 0 | 0.0 | 2850 ms | 0 |
| 12:00 | 0 | 0.0 | 1525 ms | 0 |
| 12:15 | 0 | 0.0 | 2247 ms | 0 |
| 12:30 | 0 | 0.0 | 1459 ms | 0 |
| 12:45 | 0 | 0.0 | 730 ms | 0 |
| 13:00 | 0 | 0.0 | 1558 ms | 0 |
| 13:15 | 0 | 0.0 | 2805 ms | 0 |
| 13:30 | 0 | 0.0 | 2911 ms | 0 |
| 13:45 | 0 | 0.0 | 2178 ms | 0 |
| 14:00 | 0 | 0.0 | 886 ms | 0 |
| 14:15 | 0 | 0.0 | 680 ms | 0 |
| 14:30 | 0 | 0.0 | 687 ms | 0 |
| 14:45 | 0 | 0.0 | 1152 ms | 0 |
| 15:00 | 0 | 0.0 | 959 ms | 0 |
| 15:15 | 0 | 0.0 | 2894 ms | 0 |
| 15:30 | 0 | 0.0 | 667 ms | 0 |
| 15:45 | 0 | 0.0 | 1805 ms | 0 |
| 16:00 | 0 | 0.0 | 3333 ms | 0 |
| 16:15 | 0 | 0.0 | 2415 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Magemojo 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 Magemojo goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Magemojo alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Magemojo is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Magemojo's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.