New Multi-region uptime checks and custom-domain status pages

Is GitHub Packages down?

Check official GitHub Packages status and related incidents before investigating package downloads, publishing failures or registry authentication problems.

Operational

GitHub lists Packages as operational.

Official GitHub component evidence · Source checked · Refresh status

A component indicator does not confirm every account, region or request is unaffected. Community reports are available on the overall GitHub page.

Current Packages incidents

No active incident explicitly naming this component appears in the latest verified source.

Recent resolved Packages incidents

Up to five provider-backed records that explicitly name this component. This is not a complete downtime history or an uptime measurement.

No qualifying component-specific resolved records are available here yet.

Explore all GitHub provider history

What this status covers

Packages hosts package and container registries. A failed publish, install or pull can also depend on the package address, visibility and credentials. Repository availability does not establish registry availability.

If you are having a problem

  1. Record whether the failure affects publishing or downloading and which registry is involved.
  2. Check the package name, registry address and access permissions without sharing tokens.
  3. Keep the response code and time of the request. A permissions error and an unavailable registry require different follow-up.

GitHub Packages documentation

A quiet status page does not rule out a new or account-specific issue. Save the error and its time before contacting your administrator or GitHub Support.

Other GitHub components