Release monitor
Is FLUX 3 Image released yet?
A scheduled check reads the official FLUX 3 API schema every 15 minutes and records what it found. This page is that record, newest first.
Monitor live· 6 min ago
Yes — an image endpoint is published.
The last successful check found a FLUX 3 image path in the official API schema. It is listed in the paths table below.
- Last checked
- 2 Oct 2026, 00:00 UTC6 min ago
- Checks, last 24h
- 96
- Failed checks, last 24h
- 0
- Watching since
- 21 Aug 2026, 09:00 UTC42d ago
- Check interval
- Every 15 minutes
| Path | First seen | Kind |
|---|---|---|
/v1/flux-3-video | 21 Aug 2026, 09:00 UTC | Not image |
/v1/flux-3-image | 1 Oct 2026, 18:15 UTC | Image |
| Checked (UTC) | Ago | Result | HTTP | FLUX 3 paths found |
|---|---|---|---|---|
| 2 Oct 2026, 00:00 UTC | 6 min ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 23:45 UTC | 21 min ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 23:30 UTC | 36 min ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 23:15 UTC | 51 min ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 23:00 UTC | 66 min ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 22:45 UTC | 81 min ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 22:30 UTC | 2h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 22:15 UTC | 2h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 22:00 UTC | 2h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 21:45 UTC | 2h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 21:30 UTC | 3h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 21:15 UTC | 3h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 21:00 UTC | 3h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 20:45 UTC | 3h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 20:30 UTC | 4h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 20:15 UTC | 4h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 20:00 UTC | 4h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 19:45 UTC | 4h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 19:30 UTC | 5h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 19:15 UTC | 5h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 19:00 UTC | 5h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 18:45 UTC | 5h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 18:30 UTC | 6h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
| 1 Oct 2026, 18:15 UTC | 6h ago | Read OK | 200 | /v1/flux-3-video/v1/flux-3-image |
How the check works
- Every 15 minutes a scheduled job fetches the API schema Black Forest Labs publishes and collects the paths that name FLUX 3.
- One row is written per check, whatever happened. A failed fetch is recorded as a failure rather than skipped, so a broken monitor cannot pass for a quiet week.
- First seen is the first check that saw a path — when this monitor noticed it, not necessarily when it shipped.
- The log keeps 45 days. All times are UTC.
Same data as JSON: /flux-3-status.json
Get one release-status email
Leave your email. We’ll send one concise update when FLUX 3 is available here.