Hackage is the central package repository for the Haskell programming language. It is used by Haskell developers to publish, discover, and download libraries and tools, and to browse package documentation and metadata. The main surface is a public web registry and package index, along with package distribution files that can be consumed by Haskell build tools such as Cabal.
CheckUpstream has measured Hackage at 100.000% uptime over the last 90 days and 100.000% over the last 12 months. No incidents have been recorded for Hackage in the past 12 months. Status signals are polled from Hackage's official status feed, alongside independent probes and community reports.
Hackage is currently Operational. CheckUpstream tracks Hackage in real-time across the official status page, RSS / Atom feeds, and community telemetry — refresh this page for the latest reading.
Hackage has not had a resolved incident in the past 12 months on the surfaces CheckUpstream monitors.
›What's Hackage's 30-day uptime?
Hackage's 30-day customer-perceived uptime is 100.000%. The figure is weighted (full-outage = 1.0, degraded = 0.3) so component blips don't collapse the score the way a raw incident-count would.
›How do I monitor Hackage in production?
Sign up to CheckUpstream and add Hackage to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection — covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
›What does Hackage do?
Hackage is the central package repository for the Haskell programming language. It is used by Haskell developers to publish, discover, and download libraries and tools, and to browse package documentation and metadata. The main surface is a public web registry and package index, along with package distribution files that can be consumed by Haskell build tools such as Cabal.
›How does CheckUpstream track Hackage?
We poll Hackage's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.