Sonatype Outage History

Sonatype is up right now

Sonatype had 5 outages in the last 2 years totaling 57m of downtime — averaging 0.2 incidents per month.

There were 5 Sonatype outages since October 4, 2024 totaling 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.sonatype.com

Minor September 23, 2026

Increased Response Times for Application Evaluations

Detected by Pingoru
Sep 23, 2026, 01:02 PM UTC
Resolved
Sep 23, 2026, 01:14 PM UTC
Duration
11m
Affected: Data Services
Timeline · 2 updates
  1. investigating Sep 23, 2026, 01:02 PM UTC

    We are currently investigating reports of degraded performance for application evaluations

  2. resolved Sep 23, 2026, 01:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 29, 2025

Data Services Incident

Detected by Pingoru
Aug 29, 2025, 04:01 AM UTC
Resolved
Aug 29, 2025, 04:20 AM UTC
Duration
19m
Affected: Data Services
Timeline · 2 updates
  1. investigating Aug 29, 2025, 04:14 AM UTC

    We are currently investigating reports of degraded performance.

  2. resolved Aug 29, 2025, 04:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 24, 2025

Degraded Web UI experience due to system errors

Detected by Pingoru
Jul 24, 2025, 08:37 AM UTC
Resolved
Jul 24, 2025, 08:41 AM UTC
Duration
3m
Affected: Data Services
Timeline · 2 updates
  1. investigating Jul 24, 2025, 08:37 AM UTC

    We are currently investigating reports of degraded performance.

  2. resolved Jul 24, 2025, 08:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 7, 2024

Increased Request Latency and Error Rate

Detected by Pingoru
Oct 07, 2024, 07:28 PM UTC
Resolved
Oct 07, 2024, 07:50 PM UTC
Duration
22m
Affected: Data Services
Timeline · 2 updates
  1. investigating Oct 07, 2024, 07:41 PM UTC

    We are currently investigating reports of degraded performance.

  2. resolved Oct 07, 2024, 07:49 PM UTC

    This incident has been resolved.

Read the full incident report →