Developer tools status
Platforms that stop software shipping when they go down. All 4 are checked every 20 minutes; the status beside each one is the result of its most recent check.
Developer platform outages do not break a website for the public - they stop new software shipping, which means the damage is invisible on the day and obvious a week later.
How reliable developer tools has been, last 30 days
Measured by our own checks, run every 20 minutes, not taken from any provider’s status page. 4 of 4 services have enough history to report.
| Service | Now | Uptime 30d | Downtime | Response |
|---|---|---|---|---|
| GitHub | Up | 100.0% | none | 160 ms |
| Netlify | Up | 100.0% | none | 130 ms |
| Vercel | Up | 100.0% | none | 203 ms |
| WordPress.com | Up | 100.0% | none | 166 ms |
Netlify has been the steadiest here over the last 30 days. Uptime is observed uptime: The share of measured time our checks got a usable answer. It excludes nothing, including announced maintenance.
Why developer tools services go down
These are the tools between writing code and running it: Source hosting, package registries, build pipelines, container registries. Almost nothing user-facing breaks when they fail, so they rarely appear in mainstream outage coverage. What stops is deployment, which means teams also lose the ability to fix their own unrelated problems during the same window.
Package registries deserve particular attention. A build that pulls dependencies at build time will fail when the registry is unavailable, even though the code is unchanged and the last build succeeded an hour ago. This is the most common way a developer outage surprises a team that thought it had no dependency on it.
What an outage here looks like
Builds fail with network errors on dependency steps. Pushes hang. The web interface often stays up and looks healthy while the API behind it is failing, which delays recognition considerably.
When these services are under most strain
Working hours in the US, and immediately before major release cycles. Failures cluster mid-week, when change volume across the industry is highest.
At a glance
- Typical duration
- 30 minutes to 3 hours
- Usual cause
- API capacity, registry storage, or a bad deploy
- Tell-tale sign
- Website fine, API and builds failing
- Hidden cost
- You also lose the ability to fix unrelated problems
What to do when developer tools is down
- Check the API, not the website. The web interface staying up tells you very little. The API is what your pipeline uses and it fails first.
- Stop retrying the build. Automatic retries against a degraded registry extend the outage for everyone and burn your own capacity.
- Know whether you can deploy without it. A team that cannot ship during a registry outage also cannot ship a hotfix for anything else. That is the real risk, and it is worth knowing in advance.
Still not sure whether it is them or you? Check the site from our servers - We are on a different network, a different resolver and a different route from you.