Skip to main content
fal

fal.run is unreachable for synchronous requests

Degraded Lasted 0m · started · fal's page

Level
confirmed
Worst impact
Degraded
Components
Model API
Down Index
11of 100

What to do

  • Check whether you use fal Model API. 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-09-04 13:58 UTC and 2026-09-04 13:58 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

  1. resolved

    Type: Incident Duration: 30 minutes Affected Components: Model API Sep 4, 14:28:00 GMT+0 - Resolved - This incident has been resolved. Sep 4, 14:21:00 GMT+0 - Identified - Identified the issue Sep 4, 13:58:00 GMT+0 - Investigating - We are not processing requests calling directly to [fal.run](http://fal.run) domain.

    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-3f0626939f

Is fal still down?

No, this incident was resolved 2026-09-04 13:58 UTC. For fal's live state, see https://down.guide/fal.

How long did it last?

0m, from 2026-09-04 13:58 UTC to 2026-09-04 13:58 UTC, by the times fal posted.

What was affected?

fal named Model API.

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.