outages.live
Live
Black Forest LabsIncident · 2026-08-25 04:51 UTC

Please avoid cluster specific endpoints.

ResolvedOfficial update

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

The latest update from Black Forest Labs.

State

Resolved

Started

69 d ago

2026-08-25 04:51 UTC

Lasted

1 min

until 2026-08-25 04:51 UTC

Worst impact

Notice

Timeline

1 update
04:5104:5104:5104:5204:52
NoticeUpdate postedTimes in UTC

Resolved

1 min 100%

Updates

Times in UTC

As posted by Black Forest Labs

Resolved2026-08-25 04:51 UTC

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 in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

9

Days with an incident

8

Median duration

4 h 51 min

This incident

100% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

20 h 15 min
median 4 h 51 min
90 days agoToday

Other Black Forest Labs incidents

All incidents

Black Forest Labs·EU cluster increased latencies

This incident has been resolved.

Resolvedresolved 33 d ago

Black Forest Labs·US region increased latencies

This incident has been resolved.

Resolvedresolved 55 d ago

Black Forest Labs·EU region cluster outage

Full capacity restored to api.eu.bfl.ai

Resolvedresolved 74 d ago

Black Forest Labs·Cluster Down - FLUX.2 [flex] Traffic Impacted

FLUX.2 [flex] restored - vendor mitigation in place with full recover observed

Resolvedresolved 74 d ago

Black Forest Labs·Extended flux-3-video generation times

Observing full recovery.

Resolvedresolved 75 d ago

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.

Prompt
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.cc/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.

RSS
https://outages.cc/feed.xml?providers=blackforestlabs
Slack
/feed subscribe https://outages.cc/feed.xml?providers=blackforestlabs

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane