Skip to main content
MangaDex logo

Is MangaDex Down?

No — MangaDex is up

Reachable from all 8 checked regions

Average response time: 461ms

Last checked · checks run every 6 hours

Official status page: https://status.mangadex.org

MangaDex uptime

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

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

30-day history

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

ams
358ms
DNS 281ms TCP 6ms TLS 14ms TTFB 345ms
arn
502ms
DNS 359ms TCP 27ms TLS 35ms TTFB 468ms
bom
485ms
DNS 205ms TCP 59ms TLS 65ms TTFB 415ms
cdg
252ms
DNS 167ms TCP 9ms TLS 16ms TTFB 232ms
dfw
356ms
DNS 251ms TCP 21ms TLS 28ms TTFB 332ms
ewr
411ms
DNS 96ms TCP 7ms TLS 19ms TTFB 390ms
syd
216ms
DNS 12ms TCP 0ms TLS 9ms TTFB 209ms
yyz
1115ms
DNS 188ms TCP 76ms TLS 87ms TTFB 537ms

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 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

S
SoundCloud
C
Crunchyroll
I
IMDb
Discord (for communities)
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.
  • 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 MangaDex 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 MangaDex goes down

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

Start Free Monitoring
Free plan available No credit card required