Is MangaDex Down?

No — MangaDex is up

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

Right now

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

MangaDex's status page

status.mangadex.org · read 3 minutes ago · checked every 3 minutes

Operational

MangaDex's components, as its status page reports them
Component	Status
Website	Operational
API	Operational
Core	Operational
MangaDex @ Home	Operational

Open their status page

FlareWarden checks

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

Reachable

Regions up: 8 of 8
Response: 435 ms
Checked: 4 hours ago

By region

Amsterdam reachable, 224 ms
Dallas reachable, 1104 ms
Newark reachable, 462 ms
Paris reachable, 234 ms
San Jose reachable, 391 ms
Stockholm reachable, 379 ms
Sydney reachable, 137 ms
Toronto reachable, 556 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	32 ms	2 ms	9 ms	220 ms
Dallas	1001 ms	21 ms	26 ms	1079 ms
Newark	140 ms	2 ms	8 ms	439 ms
Paris	143 ms	10 ms	17 ms	215 ms
San Jose	163 ms	9 ms	15 ms	380 ms
Stockholm	243 ms	26 ms	32 ms	347 ms
Sydney	21 ms	1 ms	8 ms	135 ms
Toronto	203 ms	20 ms	25 ms	533 ms

We check that api.mangadex.org loads, not every feature behind it. Test it yourself

History

Incidents MangaDex reported

Since Oct 22, 15 days · from status.mangadex.org

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

No incidents reported in this window.

MangaDex website availability

Measured by FlareWarden · api.mangadex.org

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

Last 30 days

57-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

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

What MangaDex does

MangaDex is a community-run manga reading site hosting fan translations across a large catalogue of series. Readers use the website or third-party apps built on its public API. The chapter images themselves are served by MangaDex at Home, a network of volunteer-operated servers that spreads bandwidth across the community instead of paying for a single central origin.

What an outage looks like

A chapter opens but the pages never appear, leaving blank panels or a spinner while search, your follows and the chapter list all work normally. At other times the site itself fails to load, or the API returns errors so third-party reader apps break while the website is fine. Older chapters commonly fail to load before recent ones do.

What to do about it

Read status.mangadex.org, which reports Website, API, CDN, Core and MangaDex at Home as separate components. Match the symptom to the row: blank pages on a working site point at MangaDex at Home or CDN rather than at the site. Reloading a failing chapter repeatedly adds load to the same volunteer servers without helping, so give it time instead.

Is it down for everyone, or just you?

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

SoundCloud

Crunchyroll

IMDb

Discord (for communities)

MangaDex outage FAQ

The site loads but no images appear. Is MangaDex down?

Partly, and the component that matters is a separate row. MangaDex at Home is a network of volunteer-run servers that serve the chapter images, and the status page reports it separately from Website, API and Core. So browsing, search and your reading list can all work while pages refuse to load. Check the MangaDex at Home and CDN rows rather than assuming the whole site is affected.

Why do older chapters fail while new ones load fine?

Because they are served differently. Older chapters are distributed across the volunteer MangaDex at Home network, so a shortage of healthy servers holding a particular chapter shows up on older material first while recently added chapters continue to load. This is why a friend can read one series normally while another refuses to open for you, without either of you having a local problem.

Is MangaDex down for everyone or just me?

Compare scope before assuming either. A blocked DNS resolver, a school or workplace network filter, or a VPN exit that particular servers reject affects one person while the service is healthy. A MangaDex incident shows on status.mangadex.org and affects the same component for everyone. Trying a different network or mobile data separates the two faster than clearing your browser cache.

Do third-party MangaDex apps stop working during an outage?

They depend on the API component, which is reported separately from the Website. So an API incident breaks reader apps while the website continues to serve, and a website incident can leave apps working normally. If your app fails, checking the site in a browser is a quick way to tell which of the two is affected before you reinstall anything.

Will I lose my follows or reading history?

Data already recorded is not erased by a service incident, so follows and reading progress saved before an outage remain. What can be lost is activity during the incident itself, where marking a chapter as read may not reach the Core component and simply does not register. MangaDex does not publish behaviour for every failure mode, so re-check anything you marked during an incident.

How we measure this

We request MangaDex'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 MangaDex 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 MangaDex 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 MangaDex goes down

We check MangaDex 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