GrapheneDB Outage History

GrapheneDB is up right now

Pingoru has recorded 17 incidents for GrapheneDB: 4 in the last 12 months and 2 in the last 90 days.

Source: graphenedb.com

17incidents recorded
4last 12 months
2last 90 days
under a minutetypical duration

Incidents, newest first

Minor September 29, 2026 GrapheneDB now speaks MCP –

Started Sep 29, 2026, 10:00 AM UTC· resolved Sep 29, 2026, 10:00 AM UTC

  1. resolved Sep 29, 2026, 10:00 AM UTC

    Connect Claude, Codex, Cursor, and any MCP-compatible AI assistant directly to your GrapheneDB account — metrics, logs, and Cypher queries, without leaving the chat.

Read the full incident report →

Minor August 26, 2026 Introducing GDB Explorer –

Started Aug 26, 2026, 10:00 AM UTC· resolved Aug 26, 2026, 10:00 AM UTC

  1. resolved Aug 26, 2026, 10:00 AM UTC

    Connect to any Neo4j database and explore its data — build Cypher visually or write it yourself, then save and share queries as Views.

Read the full incident report →

Minor March 17, 2026 AWS Private Link support –

Started Mar 17, 2026, 10:00 AM UTC· resolved Mar 17, 2026, 10:00 AM UTC

  1. resolved Mar 17, 2026, 10:00 AM UTC

    Connect to your GrapheneDB databases privately over AWS PrivateLink with the new Private Endpoint Service, with no exposure to the public internet.

Read the full incident report →

Minor February 1, 2026 Introducing the Read Operator Role –

Started Feb 01, 2026, 10:00 AM UTC· resolved Feb 01, 2026, 10:00 AM UTC

  1. resolved Feb 01, 2026, 10:00 AM UTC

    Meet the Read Operator role: give team members full visibility into logs, metrics and connection settings of your environments, without control.

Read the full incident report →

Minor October 20, 2025 Operational issue in AWS us-east-1 (N. Virginia) 11h 23m

Started Oct 20, 2025, 08:38 AM UTC· resolved Oct 20, 2025, 08:01 PM UTC

  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 March 6, 2025 Introducing Dark Mode –

Started Mar 06, 2025, 10:00 AM UTC· resolved Mar 06, 2025, 10:00 AM UTC

  1. resolved Mar 06, 2025, 10:00 AM UTC

    Dark Mode is here: a sleek, eye-friendly look for the GrapheneDB Console. See why we built it and how to switch it on in a couple of clicks.

Read the full incident report →

Minor December 2, 2024 Read-replicas for Neo4j Community –

Started Dec 02, 2024, 02:10 PM UTC· resolved Dec 02, 2024, 02:10 PM UTC

  1. resolved Dec 02, 2024, 02:10 PM UTC

    Increase availability and read capacity with our newest addition to Neo4j Community.

Read the full incident report →

Minor November 11, 2024 Issue affecting Console and Public API 1h 43m

Started Nov 11, 2024, 07:30 AM UTC· resolved Nov 11, 2024, 09:13 AM UTC

  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 →