Modal Outage History

23 incidents recorded over the last 365 days, 23 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 Modal status99.99% uptime history

Every Recorded Modal Incident

Modal incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 5, 2026Function and Sandbox execution degraded122h 18mResolved
Sep 16, 2026Dashboard and sandbox outage582h 43mResolved
Sep 4, 2026Storage is degraded866h 49mResolved
Aug 27, 2026Snapshot restores are degraded1080h 10mResolved
Aug 26, 2026Increased function latency1082h 29mResolved
Aug 19, 2026Degraded latency on .spawn() calls1249h 35mResolved
Aug 3, 2026Some services are down572h 47mResolved
Jul 30, 2026Some services are down1496h 28mResolved
Jul 24, 2026Flash Proxy (us-west) is down1644h 47mResolved
Jul 23, 2026modal.com is degraded1675h 40mResolved
Jun 29, 2026Storage degraded - impacting app creation1514h 57mResolved
Jun 16, 2026Image builds are down1830h 41mResolved
Jun 16, 2026Container scheduling / app deploys down1831h 7mResolved
Jun 16, 2026CLI volume operations disrupted1832h 39mResolved
Jun 3, 2026auth subsystem failures causing multiple issues2146h 56mResolved
Jun 1, 2026Database incident affecting services2191h 20mResolved
Jun 1, 2026Web endpoints and Image builds are down2192h 18mResolved
May 31, 2026Authorization System Restart30 minResolved
May 19, 2026CPU functions, GPU functions, and 5 other services are down1762h 21mResolved
May 11, 2026Storage refactor following AWS us-east-1c issues1h 30mResolved
May 8, 2026Internal data stores are failing2039h 29mResolved
May 7, 2026Container Scheduling and RPC errors2040h 1mResolved
May 7, 2026H200 Scheduling is degraded2043h 47mResolved

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 Modal 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 Modal 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 Modal 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 Modal outage in this window ran 91d 8h, against a mean recovery of 57d 14h. If you depend on Modal 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.