User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
metabase.com · 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 183 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 139 ms | 0 |
| Mon 15 | 0 | 0.0 | 265 ms | 0 |
| Mon 17 | 0 | 0.0 | 188 ms | 0 |
| Mon 19 | 0 | 0.0 | 82 ms | 0 |
| Mon 21 | 0 | 0.0 | 181 ms | 0 |
| Mon 23 | 0 | 0.0 | 204 ms | 0 |
| Tue 01 | 0 | 0.0 | 95 ms | 0 |
| Tue 03 | 0 | 0.0 | 86 ms | 0 |
| Tue 05 | 0 | 0.0 | 102 ms | 0 |
| Tue 07 | 0 | 0.0 | 104 ms | 0 |
| Tue 10 | 0 | 0.0 | 169 ms | 0 |
| Tue 12 | 0 | 0.0 | 170 ms | 0 |
| Tue 14 | 0 | 0.0 | 234 ms | 0 |
| Tue 16 | 0 | 0.0 | 71 ms | 0 |
| Tue 18 | 0 | 0.0 | 183 ms | 0 |
| Tue 21 | 0 | 0.0 | 72 ms | 0 |
| Tue 23 | 0 | 0.0 | 94 ms | 0 |
| Wed 01 | 0 | 0.0 | 193 ms | 0 |
| Wed 03 | 0 | 0.0 | 268 ms | 0 |
| Wed 06 | 0 | 0.0 | 88 ms | 0 |
| Wed 08 | 0 | 0.0 | 107 ms | 0 |
| Wed 10 | 0 | 0.0 | 92 ms | 0 |
| Wed 12 | 0 | 0.0 | 279 ms | 0 |
| Wed 14 | 0 | 0.0 | 62 ms | 0 |
| Wed 17 | 0 | 0.0 | 69 ms | 0 |
| Wed 19 | 0 | 0.0 | 212 ms | 0 |
| Wed 21 | 0 | 0.0 | 122 ms | 0 |
| Wed 23 | 0 | 0.0 | 336 ms | 0 |
| Thu 01 | 0 | 0.0 | 189 ms | 0 |
| Thu 03 | 0 | 0.0 | 169 ms | 0 |
| Thu 05 | 0 | 0.0 | 69 ms | 0 |
| Thu 07 | 0 | 0.0 | 61 ms | 0 |
| Thu 10 | 0 | 0.0 | 57 ms | 0 |
| Thu 12 | 0 | 0.0 | 160 ms | 0 |
| Thu 14 | 0 | 0.0 | 130 ms | 0 |
| Thu 16 | 0 | 0.0 | 252 ms | 0 |
| Thu 18 | 0 | 0.0 | 195 ms | 0 |
| Thu 20 | 0 | 0.0 | 114 ms | 0 |
| Thu 22 | 0 | 0.0 | 151 ms | 0 |
| Fri 00 | 0 | 0.0 | 203 ms | 0 |
| Fri 02 | 0 | 0.0 | 99 ms | 0 |
| Fri 04 | 0 | 0.0 | 107 ms | 0 |
| Fri 06 | 0 | 0.0 | 343 ms | 0 |
| Fri 08 | 0 | 0.0 | 270 ms | 0 |
| Fri 11 | 0 | 0.0 | 62 ms | 0 |
| Fri 13 | 0 | 0.0 | 167 ms | 0 |
| Fri 15 | 0 | 0.0 | 115 ms | 0 |
| Fri 17 | 0 | 0.0 | 183 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 Metabase Cloud 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 Metabase Cloud goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Metabase Cloud alerts to Slack, Discord or a webhook — free.
Metabase Cloud is listed in our Cloud & developer category and checked at metabase.com. Metabase grounds every answer in your semantic layer — your metrics and business logic — so you can inspect the query behind it.
Metabase Cloud publishes an official status page at status.metabase.com; 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: 153 ms average, 36–343 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Metabase Cloud incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
153 ms on average over the last 24 hours (36–343 ms).
Yes, at https://status.metabase.com.
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 Metabase Cloud here at once, the problem is on Metabase Cloud'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 Metabase Cloud. 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.