Shelf.io incident

Degraded performance in Content service

Major Resolved View vendor source →

Shelf.io experienced a major incident on August 22, 2025 affecting Making Changes to Content, lasting 8h 51m. The incident has been resolved; the full update timeline is below.

Started
Aug 22, 2025, 09:27 AM UTC
Resolved
Aug 22, 2025, 06:19 PM UTC
Duration
8h 51m
Detected by Pingoru
Aug 22, 2025, 09:27 AM UTC

Affected components

Making Changes to Content

Update timeline

  1. investigating Aug 22, 2025, 09:27 AM UTC

    We're currently experiencing an issue with a third-party service provider that may impact some users' experience. Our team is actively working with the provider to resolve the situation as quickly as possible.

  2. investigating Aug 22, 2025, 09:27 AM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 22, 2025, 10:42 AM UTC

    We have identified that the issue is limited to gem listing updates. Specifically, some gems may continue to appear in their previous location after being moved or archived. Our team is actively working on a fix to ensure updates are reflected correctly. We will share another update as soon as we have progress to report. Thank you for your understanding.

  4. identified Aug 22, 2025, 12:48 PM UTC

    Core issue is isolated, we are working on the fix

  5. identified Aug 22, 2025, 03:10 PM UTC

    Our Team is actively working on a resolution. We will provide further updates as soon as more information becomes available. Thank you for your patience.

  6. identified Aug 22, 2025, 03:43 PM UTC

    We have begun applying fixes to address the issue. While progress has been made, the issue is not yet fully resolved. Our team continues to work toward a complete resolution, and we will share updates as they become available.

  7. identified Aug 22, 2025, 03:50 PM UTC

    Some functionalities have been successfully restored. We are continuing to work on bringing full service back online and will provide updates as progress continues.

  8. resolved Aug 22, 2025, 06:19 PM UTC

    The issue has been fully resolved and all functionalities are now restored. Thank you for your patience throughout this incident.