Rewindex

CompaniesMaven CentralIncidents

Maven Central: Syncing to repo1.maven.org and search.maven.org impacted by AWS issues in us-east-1

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

AWS us-east-1 outage, Dec 7, 2021 · 71 vendors, 77 incidents

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

“…Syncing to repo1.maven.org and search.maven.org impacted by AWS issues in us-east-1 All services are working as intended. Artifacts data on http://repo1.maven.org and http://search.maven.org is now in…”

Swipe sideways to see the whole diagram.

AWS us-east-1own incident not archivedWithin an hour11 vendors, 9 blamed AWSAptible, Firebolt, Honeycomb +81 to 4 hours later16 vendors, 12 blamed AWSMaven Central, Pusher, Confluent +13Later3 vendors, 2 blamed AWSSegment, Confluent, DopplerMaven Central (this incident)posted +1 h 4 min
AWS us-east-1own incident not archivedWithin an hour11 vendors, 9 blamed AWSAptible, Firebolt, Honeycomb +81 to 4 hours later16 vendors, 12 blamed AWSMaven Central, Pusher,Confluent +13Later3 vendors, 2 blamed AWSSegment, Confluent, DopplerMaven Central (this incident)posted +1 h 4 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["AWS us-east-1<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>11 vendors, 9 blamed AWS<br/>Aptible, Firebolt, Honeycomb +8"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>16 vendors, 12 blamed AWS<br/>Maven Central, Pusher, Confluent +13"]:::blames
  root --> h4
  later["Later<br/>3 vendors, 2 blamed AWS<br/>Segment, Confluent, Doppler"]:::blames
  root --> later
  me["Maven Central (this incident)<br/>posted +1 h 4 min"]:::me
  h4 --- 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

    All services are working as intended. Artifacts data on http://repo1.maven.org and http://search.maven.org is now in sync.

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

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

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