Skip to main content

Is fal Down?

No — fal is up

Reachable from all 8 checked regions

Average response time: 366ms

Last checked · checks run every 6 hours

Official status page: https://status.fal.ai

fal uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
270ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 26 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

26-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: 100.00% uptime, 16 checks
Aug 27: 100.00% uptime, 32 checks
Aug 28: 100.00% uptime, 32 checks
Aug 29: 100.00% uptime, 32 checks
Aug 30: 100.00% uptime, 32 checks
Aug 31: 100.00% uptime, 24 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 32 checks
Sep 3: 100.00% uptime, 32 checks
Sep 4: 100.00% uptime, 30 checks
Sep 5: 100.00% uptime, 28 checks
Sep 6: 100.00% uptime, 30 checks
Sep 7: 100.00% uptime, 32 checks
Sep 8: 100.00% uptime, 40 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 32 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 24 checks
Sep 16: 100.00% uptime, 31 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 24 checks
Aug 22 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
1083ms
DNS 916ms TCP 8ms TLS 26ms TTFB 1082ms
arn
402ms
DNS 251ms TCP 1ms TLS 10ms TTFB 400ms
bom
317ms
DNS 86ms TCP 3ms TLS 7ms TTFB 315ms
cdg
301ms
DNS 162ms TCP 9ms TLS 18ms TTFB 299ms
dfw
223ms
DNS 77ms TCP 0ms TLS 94ms TTFB 221ms
ewr
111ms
DNS 65ms TCP 1ms TLS 19ms TTFB 110ms
fra
271ms
DNS 152ms TCP 1ms TLS 9ms TTFB 269ms
yyz
224ms
DNS 110ms TCP 12ms TLS 33ms TTFB 221ms

What fal does

fal runs generative AI models as a hosted inference service, weighted toward image, video and audio generation. Developers call its API rather than provisioning GPUs themselves, and applications that generate media embed it directly in a product flow. An incident therefore surfaces as a feature that will not produce output inside someone else's application.

What an outage looks like

Generation requests fail or hang, and queued asynchronous jobs stop returning results, so a product feature that creates images or video sits spinning. Because inference is already the slowest step in most flows, a fault reads as ordinary slowness well before it reads as an outage. Dashboard and REST surfaces can fail separately from inference itself.

What to do about it

Check fal's status page and read which group is affected: Model API and Serverless API sit under API, while Dashboard and Serverless Dashboard form the website group. These fail independently, and fal has reported incidents hitting the REST API and web platform without affecting inference. Poll asynchronous jobs already submitted rather than resubmitting them.

Is it down for everyone, or just you?

If this page says fal is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

fal outage FAQ

My generations are slow. Is fal down?
Hard to tell from latency alone, which is why this page measures reachability separately. Inference is inherently slow, so a degraded service and a large model look similar from inside your application. Check the Model API and Serverless API components, and compare against the response times you normally see rather than an absolute number.
Are queued jobs lost during an outage?
Not necessarily. fal's asynchronous inference places requests on a queue you poll for results, so a job accepted before the incident can still complete. Resubmitting the same work during an incident costs money twice and adds load to a recovering queue. Poll the original request first, then resubmit only what genuinely failed.
Can the dashboard be down while inference works?
Yes, and fal has reported exactly that. A DNS incident affecting the REST API and web platform was documented as not affecting inference services. If the dashboard will not load, your production traffic may be entirely unaffected, so check the API group before treating it as a customer-facing outage.
Does an outage affect my stored files and models?
An availability incident stops requests being served; it is not a data loss event. Outputs already generated and stored remain. What you lose is the ability to produce new ones for the duration. Applications that cache generated media for reuse ride out short incidents far better than those regenerating on every request.

How we measure this

  • We request fal's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where fal publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when fal goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required