MangaDex Outage History
8 incidents recorded over the last 365 days, 6 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded MangaDex Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | Maintenance of the websiteScheduled maintenance is currently in progress. We will provide updates as necessary. | 3h 30m | Scheduled |
| May 16, 2026 | Performance IssuesThis incident has been resolved. | 11h 56m | Resolved |
| Apr 18, 2026 | Performance issueThe incident was resolved and continuous observation shows no reoccurrence since. | 246h 18m | Resolved |
| Mar 6, 2026 | Network failureThis incident has been resolved. | 50 min | Resolved |
| Mar 5, 2026 | Image Delivery - Performance IssuesThis incident has been resolved. | 14h 2m | Resolved |
| Mar 4, 2026 | Network IssueThis incident has been resolved. | 24 min | Resolved |
| Dec 6, 2025 | Major database version upgradeThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Nov 18, 2025 | Intermittent image delivery failuresThings have been resolved. We will work towards more independence from third-parties in the future. | 2h 0m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next MangaDex incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This MangaDex Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before MangaDex acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single MangaDex outage in this window ran 10d 6h, against a mean recovery of 1d 10h. If you depend on MangaDex in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.