Skip to main content

Is fal Down?

No — fal is up
fal's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 259 ms

Right now

The verdict is the worse of these two. How we decide

fal's status page

status.fal.ai · read · checked every 3 minutes

Operational
fal's components, as its status page reports them
ComponentStatus
APIOperational
WebsiteOperational
Official ModelsOperational
Model APIOperational
Serverless APIOperational
DashboardOperational
Serverless DashboardOperational
Open their status page

FlareWarden checks

api.fal.ai from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
259 ms
Checked

By region

  • Ashburn reachable, 71 ms
  • Chicago reachable, 86 ms
  • Johannesburg reachable, 539 ms
  • London reachable, 150 ms
  • Los Angeles reachable, 428 ms
  • San Jose reachable, 227 ms
  • Singapore reachable, 375 ms
  • Tokyo reachable, 201 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Ashburn40 ms2 ms7 ms70 ms
Chicago18 ms1 ms26 ms86 ms
Johannesburg208 ms1 ms62 ms539 ms
London46 ms2 ms8 ms150 ms
Los Angeles320 ms2 ms22 ms428 ms
San Jose139 ms2 ms9 ms227 ms
Singapore122 ms2 ms6 ms375 ms
Tokyo26 ms3 ms6 ms201 ms
We check that api.fal.ai loads, not every feature behind it. Test it yourself

History

Incidents fal reported

Since Oct 27, 10 days · from status.fal.ai

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

fal website availability

Measured by FlareWarden · api.fal.ai

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

Last 30 days

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

Measured by FlareWarden's own checks of api.fal.ai from multiple regions every 6 hours. fal's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 72 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Replicate
Replicate
Groq
Groq
Pinecone
Pinecone
ClickHouse Cloud
ClickHouse Cloud

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • 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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of fal itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when fal goes down

We check fal every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required