Skip to main content
Metabase logo

Is Metabase Down?

No — Metabase is up

Reachable from all 8 checked regions

Average response time: 671ms

Last checked · checks run every 6 hours

Official status page: https://status.metabase.com

Metabase uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
525ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 63 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

63-day clean streak
Sep 14: 100.00% uptime, 31 checks
Sep 15: 100.00% uptime, 24 checks
Sep 16: 100.00% uptime, 30 checks
Sep 17: 100.00% uptime, 31 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 28 checks
Oct 1: 100.00% uptime, 28 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ewr
214ms
DNS 87ms TCP 1ms TLS 19ms TTFB 213ms
fra
278ms
DNS 45ms TCP 1ms TLS 14ms TTFB 278ms
gru
445ms
DNS 267ms TCP 1ms TLS 11ms TTFB 444ms
iad
2940ms
DNS 90ms TCP 2ms TLS 12ms TTFB 2939ms
jnb
486ms
DNS 112ms TCP 0ms TLS 59ms TTFB 485ms
lax
397ms
DNS 83ms TCP 1ms TLS 26ms TTFB 396ms
lhr
222ms
DNS 43ms TCP 2ms TLS 13ms TTFB 222ms
nrt
392ms
DNS 166ms TCP 1ms TLS 7ms TTFB 392ms

What Metabase does

Metabase is a business intelligence tool for querying databases and building dashboards without SQL. It is open source and widely self-hosted, which matters during an incident: the status page covers only Metabase Cloud and the Metabase Store, so a self-hosted instance is unaffected by anything reported there and its own faults will never appear on that page.

What an outage looks like

Dashboards load their layout but individual cards fail or spin, because each question runs its own query. Saved questions time out against databases that respond normally when queried directly. Scheduled subscriptions and alerts stop arriving. On Metabase Cloud the login page itself may fail, while a self-hosted instance showing the same symptoms points at the instance or its data warehouse.

What to do about it

Check status.metabase.com, which reports Metabase Cloud Platform and Metabase Store as its only two components. If you self-host, that page will not reflect your instance: check your own server and the data warehouse it queries instead. A dashboard where some cards fail and others load usually points at one slow data source rather than at Metabase.

Is it down for everyone, or just you?

If this page says Metabase is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Metabase outage FAQ

I self-host Metabase. Does the status page apply to me?
No. status.metabase.com covers Metabase Cloud Platform and Metabase Store only. A self-hosted instance runs on your own infrastructure, so an incident on that page does not affect it, and a fault in your instance will never appear there. Check your own server, its logs, and the databases it queries.
Why do some dashboard cards load and others fail?
Each card runs its own query, often against different data sources, so they fail independently. A dashboard with a few broken cards usually points at one slow or unavailable database rather than at Metabase itself. Open the failing question on its own and check the data source it uses before treating this as a Metabase outage.
Do scheduled alerts and subscriptions resend after an outage?
Metabase does not promise redelivery of a subscription that failed to send, so treat a missed report as missed rather than delayed. If a scheduled email did not arrive during an incident, run the question manually once service is restored rather than waiting. Check the next scheduled run afterwards to confirm the schedule itself resumed.
Is a Metabase Store outage the same as the platform being down?
No. The Metabase Store is the billing and account side, listed as a separate component from Metabase Cloud Platform. A Store incident can block a purchase, licence change or plan update while dashboards and questions keep working normally. Read the two lines separately rather than treating either as a general outage.

How we measure this

  • We request Metabase's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Metabase publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Metabase goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required