Storj incident

Elevated error levels on Storj US1

Major Resolved View vendor source →

Storj experienced a major incident on June 18, 2025 affecting US1 - API and US1 - Linksharing and 1 more component, lasting 6h 27m. The incident has been resolved; the full update timeline is below.

Started
Jun 18, 2025, 07:59 AM UTC
Resolved
Jun 18, 2025, 02:27 PM UTC
Duration
6h 27m
Detected by Pingoru
Jun 18, 2025, 07:59 AM UTC

Affected components

US1 - APIUS1 - LinksharingUS1 - GatewayUS1 - Select

Update timeline

  1. investigating Jun 18, 2025, 07:59 AM UTC

    Some requests to Storj US1 are failing with error 500. We are investigating the issue.

  2. monitoring Jun 18, 2025, 09:55 AM UTC

    We identified high lock time in the database and we scaled it up. We are already seeing reduced error levels as we continue to monitor.

  3. monitoring Jun 18, 2025, 01:58 PM UTC

    Our additional analysis spotted a problem with the Redis cache. We restarted Redis and saw the remaining errors clearing.

  4. resolved Jun 18, 2025, 02:27 PM UTC

    No more errors have been observed since the last intervention.