Rewindex

CompaniesMaven CentralIncidents

Maven Central: Manually setting CDN/repo1.maven.org service to degraded because of continuing CloudFlare issues

MinorStatus: resolvedStarted Resolved (2.8 h)1 updatestatus.maven.org (opens in new tab)
Part of an outage event

Cloudflare outage, Nov 18, 2025 · 77 vendors, 81 incidents

Maven Central’s incident blames Cloudflare as the cause. (hop 1, posted +5 h 1 min vs the first vendor naming Cloudflare)

“…Manually setting CDN/repo1.maven.org service to degraded because of continuing CloudFlare issues The CloudFlare CDN dependency for repo1.maven.org is still reporting as partially degraded, but the lat…”

Swipe sideways to see the whole diagram.

Cloudflareown incident not archivedWithin an hour13 vendors, 13 blamed CloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamed CloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, Maven Central +4Maven Central (this incident)posted +5 h 1 min
Cloudflareown incident not archivedWithin an hour13 vendors, 13 blamedCloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamedCloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, MavenCentral +4Maven Central (this incident)posted +5 h 1 min
Maven Central is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>13 vendors, 13 blamed Cloudflare<br/>Stytch, Zed, NordLayer +10"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>19 vendors, 19 blamed Cloudflare<br/>GitLab, Gorgias, Cursor +16"]:::blames
  root --> h4
  later["Later<br/>7 vendors, 7 blamed Cloudflare<br/>RudderStack, Brex, Maven Central +4"]:::blames
  root --> later
  me["Maven Central (this incident)<br/>posted +5 h 1 min"]:::me
  later --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    The CloudFlare CDN dependency for repo1.maven.org is still reporting as partially degraded, but the latest update on https://www.cloudflarestatus.com/ states that all CloudFlare services have been restored. We will mark this incident as resolved, but we will also continue to monitor for any issues with downloading artifacts from Maven Central.

From Maven Central’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Impact, status and times are the vendor’s own, as last archived. View on status.maven.org (opens in new tab).

Maven Central profileRecent Maven Central incidentsMarkdownJSON