Flux 3 Launch Traffic
We have completed initial scaling and optimizations to enable more traffic through on the flux-3-video api. The BFL team are excited to see what everyone creates!
The latest update from Black Forest Labs.
State
Resolved
Started
89 d ago
2026-08-04 22:01 UTC
Lasted
17 h 43 min
until 2026-08-05 15:44 UTC
Worst impact
Partial outage
Timeline
3 updatesIdentified
4 h 39 min 26%
Monitoring
13 h 5 min 74%
Updates
Times in UTCAs posted by Black Forest Labs
We have completed initial scaling and optimizations to enable more traffic through on the flux-3-video api. The BFL team are excited to see what everyone creates!
A fix has been implemented and we are monitoring the results.
We are experiencing significant traffic from our Flux 3 launch and are working to serve all customers. We appreciate your understanding and are working to lower generation times and give everyone the chance to experience our new video models!
Black Forest Labs in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
8
Median duration
4 h 51 min
This incident
3.7× the median
Other Black Forest Labs incidents
All incidentsBlack Forest Labs·EU cluster increased latencies
This incident has been resolved.
Black Forest Labs·US region increased latencies
This incident has been resolved.
Black Forest Labs·Please avoid cluster specific endpoints.
After the maintenance on our US3 cluster, the regional endpoint api.us3.bfl.ai is no longer valid, however we are still receiving traffic from certain users. Please ensure to only ever use the global api.bfl.ai or regional api. .bfl.ai endpoints as specified in the docs, not cluster specific ones like api.us3.bfl.ai, to avoid using internal domains that may be removed at any time. https://docs.bfl.ai/api_integration/integration_guidelines#api-endpoints-overview
Black Forest Labs·EU region cluster outage
Full capacity restored to api.eu.bfl.ai
Black Forest Labs·Cluster Down - FLUX.2 [flex] Traffic Impacted
FLUX.2 [flex] restored - vendor mitigation in place with full recover observed
Follow Black Forest Labs
Your coding agent knows when Black Forest Labs is down, and tells you when a failure is theirs, not yours. You can also get Black Forest Labs incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "blackforestlabs" and tell me if Black Forest Labs has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=blackforestlabs/feed subscribe https://outages.live/feed.xml?providers=blackforestlabsFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane