Is it down? Live status of 67 dev tools

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.

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.

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.

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.

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 6 hours; general security news, research and appliance or enterprise IT flaws are left out.

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.

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.