Is Medusa Down?

No — Medusa is up

Medusa's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 326 ms

Right now

The verdict is the worse of these two. How we decide

Medusa's status page

status.medusajs.com · read 3 minutes ago · checked every 3 minutes

Operational

Medusa's components, as its status page reports them
Component	Status
API	Operational
Build & Deploy	Operational
Dashboard	Operational
Compute	Operational
Database	Operational
Cache	Operational
Logs	Operational

Open their status page

FlareWarden checks

medusajs.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 326 ms
Checked: 29 minutes ago

By region

Amsterdam reachable, 150 ms
Dallas reachable, 336 ms
Paris reachable, 291 ms
San Jose reachable, 165 ms
Singapore reachable, 468 ms
Stockholm reachable, 358 ms
Sydney reachable, 593 ms
Toronto reachable, 249 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	33 ms	5 ms	18 ms	132 ms
Dallas	79 ms	25 ms	32 ms	259 ms
Paris	27 ms	10 ms	20 ms	251 ms
San Jose	77 ms	5 ms	10 ms	153 ms
Singapore	404 ms	2 ms	10 ms	461 ms
Stockholm	127 ms	1 ms	14 ms	354 ms
Sydney	241 ms	1 ms	8 ms	586 ms
Toronto	96 ms	11 ms	30 ms	204 ms

We check that medusajs.com loads, not every feature behind it. Test it yourself

History

Incidents Medusa reported

Since Oct 30, 7 days · from status.medusajs.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Medusa website availability

Measured by FlareWarden · medusajs.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 257ms

Last 30 days

7-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of medusajs.com from multiple regions every 6 hours. Medusa's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 7 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Medusa does

Medusa is an open-source commerce platform: a Node.js server with commerce modules for products, carts, orders and inventory, a framework for custom logic, and an admin dashboard for merchants. Teams can host it on any provider that runs Node.js, or on Medusa Cloud, which deploys from GitHub and hosts the server, admin, storefront, PostgreSQL database and Redis. Medusa's status page covers Medusa Cloud only.

What an outage looks like

On Medusa Cloud, a routing fault shows as storefront and API requests returning 502 or 503, as in the EU region for about 25 minutes on September 16, 2026. Build faults are more common: builds sit delayed or new deployments fail while existing production deployments keep serving, as on August 18, September 30 and October 28, 2026. The Cloud dashboard can also fail to load on its own.

What to do about it

Check status.medusajs.com, which reports API, Build & Deploy, Dashboard, Compute, Database, Cache and Logs separately; the Cloud docs also show its status at the bottom right on wide screens. If only a deploy failed, read the build logs in the dashboard or with the mcloud CLI and redeploy once Build & Deploy is operational. Subscribe on the status page by email, Slack, Microsoft Teams or RSS.

Is it down for everyone, or just you?

If this page says Medusa 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

Medusa outage FAQ

Does a Medusa Cloud outage affect self-hosted Medusa stores?

No. Medusa's deployment docs say the Medusa application can run on any hosting provider that supports Node.js servers, with its own PostgreSQL database and Redis, and status.medusajs.com covers only the services Medusa Cloud runs. A self-hosted store depends on its own host, database and payment providers instead, so a Cloud incident leaves it untouched unless it uses a Cloud service directly.

Will a failed Medusa Cloud deployment take my store offline?

It did not in Medusa's recent build incidents. On August 18 and September 30, 2026 new deployments failed, and Medusa said existing production deployments were not affected. On October 28, 2026 a burst of events backed up the build queue for about 45 minutes, delaying builds. Redeploy once the Build & Deploy row on the status page is operational again.

What happened in the September 16, 2026 Medusa Cloud outage?

Applications in Medusa Cloud's EU region returned 502 or 503 errors for about 25 minutes, from 13:30 to 13:55 UTC. Medusa's postmortem says an upgrade of Knative Serving and Kourier brought a startup regression, so routing controllers failed their health checks and were restarted before loading routing state. The outage was partial, and applications in other Medusa Cloud regions were not affected.

Is my store affected when the Medusa Cloud dashboard is down?

Not in the last dashboard outage. On September 16, 2026 the Cloud dashboard was unavailable in an incident open for about eight minutes, caused by a faulty migration; Medusa said customer applications were not affected and no data was impacted. The dashboard is its own row on the status page, apart from Compute and Database, so a dashboard fault alone does not mean stores are down.

What does the check on this page measure?

It loads medusajs.com, Medusa's marketing site. It does not reach the Cloud dashboard at cloud.medusajs.com, the Cloud API, a build, or any store hosted on Medusa Cloud. A green result means the website answers. For hosting, build, database and cache faults on Medusa Cloud, read the matching rows on status.medusajs.com.

How we measure this

We request Medusa's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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 Medusa publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Medusa itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Medusa goes down

We check Medusa every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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