Maven Central outage on August 13 — 2h 54m disruption
Aug 13, 11:08 PM → Aug 14, 02:03 AM · 2h 54m · medium
Maven Central experienced an outage beginning on August 13, 2026, which was detected through user reports. The incident resulted in a disruption of service for approximately 2 hours and 54 minutes. Service was fully restored on August 14, 2026, at 02:03 UTC.
Impact
During the outage, users reported issues primarily related to API functionality, accounting for 75 of the 77 total reports received. A small number of users also reported the website being down. While no specific regional impact was recorded, the incident was correlated with disruptions in registry probes, indicating widespread connectivity or access issues. The service disruption lasted for 2 hours and 54 minutes.
Top reported issues
- API issues75
- Website down2
Incident timeline
- Aug 13, 11:08 PM
PulseWatch detected elevated report volume (medium severity)
- Aug 13, 11:13 PM
Status updated: major issue
- Aug 13, 11:15 PM
Peak of 10 reports in 15 minutes (baseline 1.3)
- Aug 13, 11:18 PM
Status updated: possible issue
- Aug 13, 11:23 PM
Status updated: major issue
- Aug 13, 11:28 PM
Status updated: major issue
- Aug 13, 11:38 PM
Status updated: possible issue
- Aug 13, 11:43 PM
Status updated: major issue
- Aug 13, 11:58 PM
Status updated: major issue
- Aug 14, 12:03 AM
Status updated: possible issue
- Aug 14, 12:08 AM
Status updated: possible issue
- Aug 14, 12:13 AM
Status updated: possible issue
- Aug 14, 12:18 AM
Status updated: possible issue
- Aug 14, 12:23 AM
Status updated: possible issue
- Aug 14, 12:28 AM
Status updated: major issue
- Aug 14, 12:43 AM
Status updated: possible issue
- Aug 14, 12:53 AM
Status updated: possible issue
- Aug 14, 12:58 AM
Status updated: major issue
- Aug 14, 01:08 AM
Status updated: possible issue
- Aug 14, 01:13 AM
Status updated: possible issue
- Aug 14, 01:23 AM
Status updated: possible issue
- Aug 14, 01:28 AM
Status updated: possible issue
- Aug 14, 01:33 AM
Status updated: possible issue
- Aug 14, 01:38 AM
Status updated: possible issue
- Aug 14, 01:43 AM
Status updated: possible issue
- Aug 14, 02:03 AM
Report volume returned to baseline — incident resolved