Maven Central had 6 outages in the last 2 years totaling 17h 54m of downtime — averaging 0.2 incidents per month.
There were 6 Maven Central outages since December 30, 2025 totaling 17h 54m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating a service outage affecting our main CDN and therefore access to repo1.maven.org.
An issue which lead to an outage atrepo1.maven.org has been resolved. CDN services should now be restored.
We are currently experiencing delays in publishing deployments due to an infrastructure issue. We are actively working on a fix and expect deployments to resume shortly. We appreciate your patience.
The infrastructure issue has been resolved and publishing is now proceeding. There is a backlog of deployments that will take some time to clear. We appreciate your patience.
The infrastructure issue has been resolved and publishing deployments are operating normally. Thank you for your patience.
We are currently investigating a service outage affecting search.maven.org.
An issue which lead to an outage at search.maven.org has been resolved. Search services should now be restored.
We are currently investigating a service outage affecting Nexus on one or more OSSRH hosts.
Services have been restored on one or more OSSRH hosts.
We are currently experiencing delays in publishing deployments due to a Jenkins infrastructure issue. A large publishing job kicked off earlier this afternoon can take several hours to complete. Once it finishes, the backlog will begin to clear. We are actively monitoring and will reach out to publishers if any manual intervention is needed. We appreciate your patience.
The Jenkins infrastructure issue has been resolved and publishing jobs are now running. There is a backlog of deployments that will take some time to clear. We appreciate your patience.
The Jenkins infrastructure issue has been resolved and publishing deployments are operating normally. Thank you for your patience.
We've seen a recent increase in 403 errors returned by our CDN. We are still trying to determine root cause and have engaged with the vendor's support team. Reports are showing that Github Actions are primarily impacted.
We worked with our CDN provider to override some security rules that were being triggered by Github Actions IP adresses, and our monitors are no longer showing 403s for legitimate build traffic.