devhunt / status

Is it down? Live status of 92 dev tools

5 of 92 with problems · checked 09:20 UTC

[post on x]

% fineavg 85% · today 93%

100500
aug 19today
  • oct 171%Replit partial, Bitbucket partial, MongoDB Atlas partial, Brevo partial, Ably partial +20
  • oct 2173%GitHub outage, Bitbucket outage, Sentry outage, Lovable partial, Cloudflare partial +19
  • nov 1273%ChatGPT outage, Fly.io outage, Claude partial, Cursor partial, Elastic Cloud partial +20

problems now

security30 days

all 92 tools14 days

AI APIs and chat

AI coding tools

Code hosting and registries

Hosting and cloud

Databases and backends

Payments and commerce

Authentication

Email and messaging

CI/CD and builds

Monitoring, analytics and flags

Collaboration and dev tools

Content and media

most days with problems90 days

  1. GitHub46
  2. Elastic Cloud44
  3. Cursor43
  4. Cloudflare43
  5. Twilio42
  6. Grafana Cloud40
  7. Replit35
  8. Snyk35

FAQ

Where does this status come from?+

From each tool’s official status page, through its public status API (Atlassian Statuspage, incident.io, Instatus, Status.io, or the tool’s own API for Heroku and Slack). DevHunt adds nothing and collects no user reports.

How fresh is it?+

DevHunt checks every official status page every 5 minutes, and this board refreshes itself every minute while you have it open. The time of the last check is shown at the top.

How is uptime calculated?+

From DevHunt’s own checks: the share of 5-minute checks in which the official status page reported no outage. A major outage counts as down, a partial outage as 30% down (the weighting Atlassian Statuspage uses), and degraded performance or maintenance as up. Days before DevHunt started checking are colored from the incidents the status page itself lists.

Does a tool with more problem days have worse uptime?+

Not necessarily. The count comes from each official status page, and tools that post every small incident rank higher than ones that post only big outages. A long list often means a more open status page, not a worse tool.

What goes in the security list?+

Only events a developer has to act on: a confirmed breach at a platform developers use (cloud, hosting, CI, registries, AI providers, dev tools), a malicious or compromised release of a widely used package or tool, and critical flaws in widely used developer software that are being exploited. Each has one line on what to do and a link to the report. They are picked from security news every 2 hours; general security news, research and appliance or enterprise IT flaws are left out.

A tool fails for me but shows as operational. What now?+

Status pages often lag a few minutes behind the start of an outage, and small regional problems may never be posted. Open the tool’s page here for its components and open incidents, then check your network, region and API keys.

Why isn’t my tool listed?+

Only tools whose official status page has a public JSON API are tracked, so the status shown is always the tool’s own. Tools without one are left out rather than guessed.