Developer-tool outages break builds, deploys, and on-call. This page tracks the services engineering teams ask about first: GitHub, GitLab, npm, Docker Hub, PyPI, and their peers. Each card shows the current HTTP probe result, the most recent community reports, and — where the vendor publishes one — the official status page indicator. If you're debugging a failing CI pipeline, this is the page to check before you dig into your own code.
The most common culprits are CDN/registry outages, authentication problems, and upstream cloud provider incidents. A package registry being slow is very different from a git host being unreachable; the specific service matters more than the overall category.
Cache aggressively where you can (local registry mirrors, pinned dependencies), subscribe to your vendor's status channel, and monitor your own critical endpoints on WebsiteDown so your team gets pinged before the issue surfaces in production.
If your product depends on one of these services, set up a WebsiteDown monitor and get an email when the probe flips. Free plan includes 1 monitor with 5-minute checks.
