GrapheneDB Outage History

GrapheneDB is up right now

GrapheneDB had 3 outages in the last 2 years totaling 13h 18m of downtime — averaging 0.1 incidents per month.

There were 3 GrapheneDB outages since October 15, 2024 totaling 13h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://graphenedb.com/status/

Minor October 20, 2025

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

Detected by Pingoru
Oct 20, 2025, 08:38 AM UTC
Resolved
Oct 20, 2025, 08:01 PM UTC
Duration
11h 23m
Timeline · 4 updates
  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.

Read the full incident report →

Minor November 11, 2024

Issue affecting Console and Public API

Detected by Pingoru
Nov 11, 2024, 07:30 AM UTC
Resolved
Nov 11, 2024, 09:13 AM UTC
Duration
1h 43m
Timeline · 3 updates
  1. investigating Nov 11, 2024, 07:32 AM UTC

    We're currently experiencing an issue that is affecting our Console and Public API. Our team is already looking into it, and we'll provide updates once we identify the problem. We apologize for any inconvenience this may have caused.

  2. identified Nov 11, 2024, 08:18 AM UTC

    We've identified the issue and we're working on a fix. We'll provide update once issue is fully resolved.

  3. resolved Nov 11, 2024, 09:13 AM UTC

    The issue has been resolved.

Read the full incident report →

Minor October 15, 2024

Issue affecting Console

Detected by Pingoru
Oct 15, 2024, 03:05 PM UTC
Resolved
Oct 15, 2024, 03:17 PM UTC
Duration
11m
Timeline · 2 updates
  1. investigating Oct 15, 2024, 03:06 PM UTC

    We have identified and issue that is affecting Console, Operations and Public API. The team is investigating, and we'll provide update as soon as we have further info to share. We apologize for any inconvenience this may have caused.

  2. resolved Oct 15, 2024, 03:17 PM UTC

    Issue has been resolved, we appreciate your understanding.

Read the full incident report →