Is JitPack down or not working?

What happened to JitPack, why did the service go down and not work? Here you can see who else is having the same problem with JitPack, as well as possible solutions. According to our statistics, the following most often do not work: DNS, Domains, File Access, File Sharing, Hosting, Login, Server, Website.

Current status: No failures

At the moment, according to our data, JitPack is working fine, but single failures are possible. If JitPack does not work for you, then report your problem and write a comment.
Add comment

JitPack outage reports in the last 24 hours

User reports by hour (UTC), last 24 hours

Hour
Weight 0 0 0 0 0 0
Hour
Weight 0 0 0 0 0 0
Hour
Weight 0 0 0 0 0 0
Hour
Weight 0 0 0 0 0 0

Total weight in 24 hours: 0 Busiest hour: 23:00 UTC (weight 0)

How this score compares

Current 24-hour weight is 0. Warnings start at 20, Failed at 50. Median services on this language today is 0.

Other services in this category

Official links

  • Twitter: http://www.twitter.com/jitpack
JitPack builds software packages straight from GitHub repositories. When it has problems, dependency downloads can fail or stall. This page tracks current status, so you can tell quickly whether an issue is on JitPack's side or somewhere in your own setup.
JitPack is a package registry that turns Git repositories into ready-to-use libraries for JVM projects and other ecosystems. You point it at a repository and a version tag, and it builds the artifact on demand. Most builds happen automatically, which makes it popular for open-source projects that do not want to host their own artifact server. When JitPack misbehaves, the usual signs are failed Gradle or Maven downloads, long build queues, or timeouts when resolving a dependency. Builds can also fail for reasons unrelated to the platform, such as broken build scripts or missing configuration in the repository itself. First check whether other projects resolve correctly. If they do, the problem is likely in the specific repository or tag. Verify the tag exists, confirm the build log on JitPack's site, and make sure your build tool is pointing at the right repository URL. Cached failures can also linger, so clearing local caches sometimes helps.

Questions

Is JitPack down right now?

According to reports on this page, JitPack looks fine for most people. Isolated failures still happen — report yours if you are stuck.

When was the last mass outage?

We do not have a recorded mass outage for JitPack yet.

Why does my dependency fail to resolve even though JitPack is up?

A failing build is not always a platform outage. Broken build scripts, missing tags, or wrong repository URLs are common causes. Check the build log on the JitPack site for the exact error before assuming a service problem.

How do I know if my build failed on my side or on JitPack's?

Try resolving a different JitPack dependency. If that works, your setup and network are fine and the issue is with the specific repository build. If several dependencies fail at once, this status page will show whether JitPack is affected.

JitPack - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.
  • No registration required.
  • Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
  • Active links in the text of the message are not published, but displayed in plain text.
  • It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.