User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
microcms.io · 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 56 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 11 | 0 | 0.0 | 49 ms | 0 |
| Mon 13 | 0 | 0.0 | 176 ms | 0 |
| Mon 15 | 0 | 0.0 | 166 ms | 0 |
| Mon 17 | 0 | 0.0 | 117 ms | 0 |
| Mon 19 | 0 | 0.0 | 154 ms | 0 |
| Mon 21 | 0 | 0.0 | 287 ms | 0 |
| Mon 23 | 0 | 0.0 | 46 ms | 0 |
| Tue 01 | 0 | 0.0 | 91 ms | 0 |
| Tue 04 | 0 | 0.0 | 98 ms | 0 |
| Tue 06 | 0 | 0.0 | 50 ms | 0 |
| Tue 08 | 0 | 0.0 | 52 ms | 0 |
| Tue 10 | 0 | 0.0 | 98 ms | 0 |
| Tue 12 | 0 | 0.0 | 84 ms | 0 |
| Tue 14 | 0 | 0.0 | 85 ms | 0 |
| Tue 17 | 0 | 0.0 | 191 ms | 0 |
| Tue 19 | 0 | 0.0 | 45 ms | 0 |
| Tue 21 | 0 | 0.0 | 111 ms | 0 |
| Tue 23 | 0 | 0.0 | 86 ms | 0 |
| Wed 01 | 0 | 0.0 | 142 ms | 0 |
| Wed 04 | 0 | 0.0 | 51 ms | 0 |
| Wed 06 | 0 | 0.0 | 51 ms | 0 |
| Wed 08 | 0 | 0.0 | 51 ms | 0 |
| Wed 11 | 0 | 0.0 | 67 ms | 0 |
| Wed 13 | 0 | 0.0 | 73 ms | 0 |
| Wed 15 | 0 | 0.0 | 161 ms | 0 |
| Wed 17 | 0 | 0.0 | 96 ms | 0 |
| Wed 19 | 0 | 0.0 | 107 ms | 0 |
| Wed 21 | 0 | 0.0 | 91 ms | 0 |
| Wed 23 | 0 | 0.0 | 87 ms | 0 |
| Thu 02 | 0 | 0.0 | 111 ms | 0 |
| Thu 04 | 0 | 0.0 | 206 ms | 0 |
| Thu 06 | 0 | 0.0 | 134 ms | 0 |
| Thu 08 | 0 | 0.0 | 158 ms | 0 |
| Thu 10 | 0 | 0.0 | 92 ms | 0 |
| Thu 12 | 0 | 0.0 | 169 ms | 0 |
| Thu 14 | 0 | 0.0 | 284 ms | 0 |
| Thu 16 | 0 | 0.0 | 113 ms | 0 |
| Thu 18 | 0 | 0.0 | 235 ms | 0 |
| Thu 20 | 0 | 0.0 | 55 ms | 0 |
| Thu 22 | 0 | 0.0 | 100 ms | 0 |
| Fri 00 | 0 | 0.0 | 183 ms | 0 |
| Fri 02 | 0 | 0.0 | 172 ms | 0 |
| Fri 03 | 0 | 0.0 | 57 ms | 0 |
| Fri 06 | 0 | 0.0 | 82 ms | 0 |
| Fri 08 | 0 | 0.0 | 72 ms | 0 |
| Fri 10 | 0 | 0.0 | 93 ms | 0 |
| Fri 11 | 0 | 0.0 | 54 ms | 0 |
| Fri 12 | 0 | 0.0 | 56 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for microCMS 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 microCMS goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send microCMS alerts to Slack, Discord or a webhook — free.
microCMS, at microcms.io, is one of the Cloud & developer services we monitor. microCMSはAPIベースの日本製のヘッドレスCMSです。もう社内向け編集/管理画面を自作する必要はありません。開発・運用コストを大きく下げることでビジネスを加速させます。
microCMS publishes an official status page at status.microcms.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 119 ms average, 54–284 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 microCMS incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
119 ms on average over the last 24 hours (54–284 ms).
Yes, at https://status.microcms.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 microCMS here at once, the problem is on microCMS'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 microCMS. 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.