Skip to main content

Is Metabase Down?

No — Metabase is up

Reachable from all 8 checked regions

Average response time: 582ms

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
583ms
Avg response, 30 days

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

30-day history

12-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: 100.00% uptime, 24 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 36 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 31 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Jul 25 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.

gru
506ms
DNS 299ms TCP 2ms TLS 9ms TTFB 503ms
iad
145ms
DNS 39ms TCP 2ms TLS 9ms TTFB 143ms
jnb
613ms
DNS 217ms TCP 0ms TLS 63ms TTFB 612ms
lax
2302ms
DNS 20ms TCP 1ms TLS 28ms TTFB 2300ms
lhr
240ms
DNS 15ms TCP 2ms TLS 11ms TTFB 238ms
nrt
453ms
DNS 166ms TCP 2ms TLS 8ms TTFB 451ms
ord
200ms
DNS 34ms TCP 1ms TLS 28ms TTFB 199ms
sin
465ms
DNS 109ms TCP 1ms TLS 6ms TTFB 463ms
sjc
239ms
DNS 31ms TCP 1ms TLS 11ms TTFB 237ms

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 all 18 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 — 8 of them answered the most recent check.
  • 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 the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required