- 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 2026-01-22 01:37 UTC and 2026-01-22 01:37 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 → Jan 22, 01:45:03 GMT+0 - Resolved - This incident has been resolved, we are recovering Jan 22, 01:44:45 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jan 22, 01:37:20 GMT+0 - Investigating - We are currently investigating this incident.
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-4e6b95c952
Is fal still down?
No, this incident was resolved 2026-01-22 01:37 UTC. For fal's live state, see https://down.guide/fal.
How long did it last?
0m, from 2026-01-22 01:37 UTC to 2026-01-22 01:37 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.