Flox logo

Is Flox Down?

Developer ToolsLive status, outages, and incident history

No. Flox is up right now.

Every monitored Flox system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 2m agoLive · every 60s

Know the moment Flox breaks

Flox is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Flox status page
How we know: the official Flox status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Flox Status Summary

As of 04:51 UTC on 14 November 2026, Flox is operational. PulsAPI checked Flox's official status page and found 5 of 5 components operational, with no active incidents. The latest incident, "Degraded catalog response time and increased error rate", was on Oct 29, 2026 and lasted 21h 9m.

Cite as: PulsAPI, “Flox status”, checked 14 November 2026, 04:51 UTC. https://www.pulsapi.com/services/flox

Flox Component Status

The main Flox systems on this page. All 5 are operational right now.

5operational
api.flox.dev
Operational
downloads.flox.dev
Operational
flox.dev
Operational

2 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking hub.flox.dev, shipit.flox.dev.

See all of them free

Component statuses may change independently during partial outages.

Recent Flox Outages & Incidents

Incident history from the official Flox status page, including resolution updates.

Degraded catalog response time and increased error rateResolved Oct 29, 2026 · 21h 9mResolved

Response times and error rates have returned to and remained at baseline for the past 12 hours. --- [2026-10-29T20:31:01Z] (monitoring) We've identified the cause, applied several mitigations and will continue to monitor performance. --- [2026-10-29T16:14:10Z] (investigating) We have identified an increased rate of 502 errors in response to catalog requests and are investigating. You may get "Service Unavailable" or "Bad Gateway" error using the CLI. A retry should proceed normally.

Flox Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Flox incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Flox Outage Reports

Problems reported by engineers using Flox. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Flox problems reported yet.

Something wrong with Flox on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Flox

Flox's status page at status.flox.dev lists 5 components, such as api.flox.dev, downloads.flox.dev and flox.dev. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Flox's side or yours.

Flox Status FAQ

Is Flox down right now?

The verdict at the top of this page comes from the latest poll of the official Flox status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Flox is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Flox recovers.

How do I check Flox uptime history?

PulsAPI tracks Flox uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Flox changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Flox outages?

PulsAPI reads the official Flox status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Flox components?

Yes. PulsAPI monitors 5 individual Flox components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Flox goes down?

Yes. Create a free account and subscribe to Flox: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Flox to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Flox problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Flox?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Flox plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Flox with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services