Modrinth Outage History

20 incidents recorded over the last 365 days, 20 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.

Live Modrinth status98.87% uptime history

Every Recorded Modrinth Incident

Modrinth incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 2, 2026API is down58h 40mResolved
Oct 14, 2026API is down531h 9mResolved
Oct 3, 2026API and Version API are down780h 44mResolved
Sep 26, 2026API and Version API are down952h 31mResolved
Sep 14, 2026API, Version API, and 1 other service are down1232h 44mResolved
Sep 1, 2026API, Version API, and 1 other service are down1565h 5mResolved
Aug 1, 2026Search is down2196h 12mResolved
Jul 31, 2026API is down1475h 34mResolved
Jul 27, 2026Search is down1566h 18mResolved
Jul 22, 2026API is down1689h 33mResolved
Jul 21, 2026Website is down1709h 1mResolved
Jul 18, 2026API and Search are down1784h 18mResolved
Jul 17, 2026API and Search are down1806h 31mResolved
Jul 15, 2026Version API is down1857h 37mResolved
Jun 24, 2026Version API is down1651h 56mResolved
Jun 21, 2026Search is down1715h 14mResolved
Jun 19, 2026Search is down1755h 15mResolved
Jun 17, 2026Search is down1820h 25mResolved
Jun 12, 2026Version API and Search are down1929h 38mResolved
Jun 3, 2026Version API and Search are down2147h 14mResolved

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 Modrinth 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 Modrinth 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 Modrinth 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 Modrinth outage in this window ran 91d 12h, against a mean recovery of 62d 23h. If you depend on Modrinth 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.