Skip to main content
Vendor reliability

Vendor record

Hackage

Vendor reports Operational

Checked

Front door check counts and Hackage’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We have no front door checks against Hackage in the last 30 days. That does not show whether it was reachable.

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Hackage product, region or your app worked.

How we count front door checks

Hackage says

Incident posts from Hackage’s status page, with its titles, impact levels and times. They say what Hackage chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

0

incidents Hackage posted, last 1 year

All vendors’ incidents

Most recent records · all dates

No incidents recorded

Hackage has posted nothing we recorded. That is an empty history, not evidence of uninterrupted service.

Your code, your dependencies

See which of your code paths call Hackage

Connect GitHub or GitLab to find where your public or private repository uses Hackage. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Hackage status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · HackageStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/hackage-registry?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Hackage status badge"></iframe>

Frequently Asked Questions

Is Hackage currently down?

Hackage's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Hackage last have an outage?

We have no closed incident record for Hackage in the past 12 months. Missing records do not establish that the service had no incidents.

Does CheckUpstream publish an uptime percentage for Hackage?

No. CheckUpstream does not run front door checks against Hackage. The incident history on this page is what Hackage reported, not a measure of how often it was available.

How do I monitor Hackage in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

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?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.