RedShelf Outage History

RedShelf is up right now

RedShelf had 1 outage in the last 2 years totaling 5h 15m of downtime — averaging 0 incidents per month.

There was 1 RedShelf outage since October 20, 2025 totaling 5h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.redshelf.com

Critical October 20, 2025

AWS Outage

Detected by Pingoru
Oct 20, 2025, 02:33 PM UTC
Resolved
Oct 20, 2025, 07:49 PM UTC
Duration
5h 15m
Affected: WebsiteeReaderManagement Tools
Timeline · 6 updates
  1. investigating Oct 20, 2025, 01:40 PM UTC

    We are currently investigating this issue.

  2. investigating Oct 20, 2025, 02:33 PM UTC

    Amazon Web Services (AWS) is experiencing an outage that is affecting all internet services. This will cause problems with the RedShelf eReader that cannot be fixed until the AWS problems have been solved. We apologize for any inconvenience and will update this hourly until the problem is solved.

  3. investigating Oct 20, 2025, 04:34 PM UTC

    Amazon Web Services (AWS) is experiencing an outage that is affecting all internet services. This will cause problems with the RedShelf eReader that cannot be fixed until the AWS problems have been solved. We apologize for any inconvenience and will update this hourly until the problem is solved.

  4. investigating Oct 20, 2025, 05:17 PM UTC

    Amazon Web Services (AWS) is experiencing an outage that is affecting all internet services. This will cause problems with the RedShelf eReader that cannot be fixed until the AWS problems have been solved. We apologize for any inconvenience and will update this hourly until the problem is solved.

  5. monitoring Oct 20, 2025, 07:30 PM UTC

    AWS services are beginning to recover. We apologize for any inconvenience and will continue to monitoring update this hourly until the problem is solved.

  6. resolved Oct 20, 2025, 07:49 PM UTC

    We've confirmed our upstream AWS issues have been resolved. Our services are recovering and should be fully operational. We're continuing to monitor.

Read the full incident report →