A fraction of new containers are experiencing errors

What to do

• Check whether your product depends on Modal. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 5h 13m it lasted.

  Anything that failed between 2026-02-20 13:30 UTC and 2026-02-20 18:43 UTC may need a replay.

• Subscribe to Modal's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=modal works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Modal 5

1. updateFeb 20, 2026, 1:30 PM UTC

   We have identified the root cause and are taking action to mitigate.

   provider

2. updateFeb 20, 2026, 2:44 PM UTC

   Issues with some image builds getting stuck have been resolved.

   provider

3. updateFeb 20, 2026, 5:01 PM UTC

   New containers are working normally. We are continuing to investigate possible lingering effects for recently started containers. At 13:30 UTC a bad change went out causing new containers to potentially get stuck or experience errors. At 14:44 UTC a the bad change was fully reverted and the disruption mitigated. We experienced a secondary, lesser problem with similar symptoms between approximately 16:00 and 16:15 UTC as part of the mitigations put in place during the response.

   provider

4. updateFeb 20, 2026, 6:01 PM UTC

   Functions are fully restored. We are still investigating possible lingering effects for a small number of Sandboxes that were launched between 13:30-14:44 UTC.

   provider

5. resolvedFeb 20, 2026, 6:43 PM UTC

   All issues have been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.