- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on fal. 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 0m it lasted.
Anything that failed between 2025-10-23 23:20 UTC and 2025-10-23 23:20 UTC may need a replay.Subscribe to fal's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=fal works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from fal 1
- resolved
Type: Incident Duration: 8 minutes Affected Components: Official Models, API → Oct 24, 00:21:04 GMT+0 - Resolved - Queues have cleared Oct 23, 23:27:33 GMT+0 - Resolved - This incident has been resolved. Oct 23, 23:20:00 GMT+0 - Identified - We are saw elevated levels of queuing and new runners not scheduling correctly
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-17e9826ae4
Is fal still down?
No, this incident was resolved 2025-10-23 23:20 UTC. For fal's live state, see https://down.guide/fal.
How long did it last?
0m, from 2025-10-23 23:20 UTC to 2025-10-23 23:20 UTC, by the times fal posted.
What caused it?
fal hasn't published a root cause. If it does, it shows here.
Where does this come from?
fal's official status page, https://status.fal.ai, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.