Maven Central: repo1.maven.org is down

CriticalStatus: resolvedStarted 2024-07-18 22:46 UTCResolved 2024-07-18 22:46 UTC (0 min)1 updatestatus.maven.org

Part of an outage event

Azure central us outage, Jul 18, 2024 · 9 vendors, 9 incidents

Maven Central’s incident started in the same window without naming Azure (timing only, not evidence of a link). (timing only, posted +46 min vs the first vendor naming Azure)

Swipe sideways to see the whole diagram.

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["Azure central us<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>5 vendors, 1 blamed Azure<br/>MongoDB Atlas, Confluent, GitHub, GitHub Copilot +1"]:::blames
  root --> h1
  later["Later<br/>1 vendor<br/>Contentstack"]:::names
  root --> later
  me["Maven Central (this incident)<br/>posted +46 min"]:::me
  root -.->|"same window"| 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

resolved2024-07-18 22:46 UTC
An issue which lead to an outage atrepo1.maven.org has been resolved. CDN services should now be restored.

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 profile Recent Maven Central incidents Markdown JSON