Maven Central incident
403s being returned from CloudFlare when accessing repo.maven.apache.org/repo1.maven.org
Resolved after 1 hour 45 minutes, affecting CDN - repo1.maven.org, on January 6, 2026.
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.
Affected components
Update timeline
- investigating Jan 06, 2026, 02:18 PM UTC
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.
- resolved Jan 06, 2026, 04:04 PM UTC
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.
Your product runs on more than Maven Central
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services