GrapheneDB incident

Operational issue in AWS us-east-1 (N. Virginia)

Minor Resolved View vendor source →

GrapheneDB experienced a minor incident on October 20, 2025, lasting 11h 23m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 08:38 AM UTC
Resolved
Oct 20, 2025, 08:01 PM UTC
Duration
11h 23m
Detected by Pingoru
Oct 20, 2025, 08:38 AM UTC

Update timeline

  1. investigating Oct 20, 2025, 08:38 AM UTC

    We are currently experiencing issues in the AWS us-east-1 region due to an ongoing AWS operational issue. Impact (detected so far) - New deployments are failing or experiencing delays in us-east-1. - Database resume/pause operations are not completing successfully in us-east-1. - Users may experience intermittent issues authenticating to the Console We are actively monitoring the situation and AWS's status for updates. We will provide updates as more information becomes available.

  2. identified Oct 20, 2025, 09:39 AM UTC

    The root cause of the issues has been resolved by AWS. No operation or database was impacted during the outage.

  3. identified Oct 20, 2025, 02:44 PM UTC

    We're reopening this issue since there are still errors reported by AWS in us-east-1 affecting our service. No running database is affected but operations like creating new database, resuming database and adding replicas are affected. Updates to follow.

  4. resolved Oct 20, 2025, 08:01 PM UTC

    The issue in the AWS us-east-1 region has been resolved. All operations are functioning normally again. No running databases were impacted during the incident.