Sep <var data-var='date'>17</var>, <var data-var='time'>19:55</var> UTC Resolved - After deploying the fix, we monitored the impacted instances, operational metrics, and errors. This incident is now resolved. A post-mortem will be available as soon as it’s been completed. Sep <var data-var='date'>17</var>, <var data-var='time'>19:06</var> UTC Monitoring - A fix has been deployed to all affected environments. We will monitor the situation to ensure that the fix fully resolves the issue. Sep <var data-var='date'>17</var>, <var data-var='time'>17:11</var> UTC Identified - We have identified the issue and are working towards a solution. At this time, certain database operations, such as create, delete, and clone for customers using Neo4j Aura on Azure only, continue to be impacted. Sep <var data-var='date'>17</var>, <var data-var='time'>16:46</var> UTC Investigating - We are currently aware of an issue that is impacting certain database operations, such as create, delete, clone for customers using Aura on Azure.

Issue impacting certain database operations for Aura customers on Azure

Sep <var data-var='date'>16</var>, <var data-var='time'>14:31</var> UTC Resolved - A fix has been deployed and all functionality should now be recovered. Sep <var data-var='date'>16</var>, <var data-var='time'>12:29</var> UTC Update - Our support portal provider continues to roll out a fix. Sep <var data-var='date'>16</var>, <var data-var='time'>11:30</var> UTC Monitoring - A fix is being rolled out and the portal should become less impacted by errors over time. See details https://status.salesforce.com/incidents/20004433 Sep <var data-var='date'>16</var>, <var data-var='time'>10:11</var> UTC Update - Our support portal provider continues to work on addressing the issue. See details here https://status.salesforce.com/incidents/20004433 Sep <var data-var='date'>16</var>, <var data-var='time'>09:16</var> UTC Update - Our support portal provider is still working on addressing the issue. See details here https://status.salesforce.com/incidents/20004433 Sep <var data-var='date'>16</var>, <var data-var='time'>08:50</var> UTC Identified - Our service provider for the support portal is experiencing some outage - See https://status.salesforce.com/products/Salesforce_Services If you experience issues submitting a new support case, please send email to support@neo4j.com

Customer support portal issues

Sep <var data-var='date'> 9</var>, <var data-var='time'>13:39</var> UTC Resolved - All affected components are now fully recovered. Sep <var data-var='date'> 9</var>, <var data-var='time'>13:36</var> UTC Monitoring - We have deployed a fix and the affected services are recovering. Sep <var data-var='date'> 9</var>, <var data-var='time'>13:26</var> UTC Update - We have made good progress and are recovering the problematic component. Sep <var data-var='date'> 9</var>, <var data-var='time'>13:10</var> UTC Update - We continue to work on addressing the issue. Sep <var data-var='date'> 9</var>, <var data-var='time'>12:54</var> UTC Identified - We have identified the source of the issue and are currently working on a solution. Sep <var data-var='date'> 9</var>, <var data-var='time'>12:31</var> UTC Investigating - We are currently investigating an issue affecting the Aura console console.neo4j.io and the API api.neo4j.io

Console and API outage

Sep <var data-var='date'> 4</var>, <var data-var='time'>15:36</var> UTC Resolved - All instances are available, manual steps to unblock the remaining small number of instances was undertaken to resolve. Sep <var data-var='date'> 4</var>, <var data-var='time'>10:23</var> UTC Identified - The issue has been identified, instances remain available and steps to resolve for the instances impacted being reviewed currently. Sep <var data-var='date'> 3</var>, <var data-var='time'>16:43</var> UTC Investigating - We are currently investigating this issue.

A small number of Free Tier instances are experiencing issues updating

Aug <var data-var='date'>20</var>, <var data-var='time'>19:10</var> UTC Resolved - Since the last update, the investigation has moved on. The issue was identified, and we monitored the service as it recovered from degradation. We confirm the issue is now resolved. Aug <var data-var='date'>20</var>, <var data-var='time'>16:48</var> UTC Update - We continue to investigate the Aura metrics issue. Aug <var data-var='date'>20</var>, <var data-var='time'>16:18</var> UTC Update - We continue to investigate the Aura metrics issue. Aug <var data-var='date'>20</var>, <var data-var='time'>15:49</var> UTC Investigating - Our team has identified an issue with collecting the metrics for Aura instances. This will impact the metric visibility and forwarding. We are currently investigating the issue.

Aura metrics issue.

Aug <var data-var='date'> 7</var>, <var data-var='time'>15:34</var> UTC Resolved - We have monitored the fix and found the service to be stable. This incident is now considered resolved. Aug <var data-var='date'> 7</var>, <var data-var='time'>13:49</var> UTC Monitoring - The fix to resolve the issue has now completed deployment to the Aura service and we are monitoring the situation. Aug <var data-var='date'> 7</var>, <var data-var='time'>09:44</var> UTC Update - The fix to the trim() Cypher function has passed testing and validation and is now being deployed. Aug <var data-var='date'> 7</var>, <var data-var='time'>01:16</var> UTC Update - We are actively working on addressing the issue. The fix for the trim() Cypher function is undergoing testing and validation currently before deployment. Further updates will be provided before we begin deploying it to Aura instances. Aug <var data-var='date'> 7</var>, <var data-var='time'>01:15</var> UTC Update - Development has completed on the hot-fix for this issue, and we are finalizing the rollout plan for Aura. Aug <var data-var='date'> 6</var>, <var data-var='time'>14:54</var> UTC Update - The fix for the trim() Cypher function is undergoing testing and validation before deployment. Further updates will be provided before we begin deploying it to Aura instances. Aug <var data-var='date'> 6</var>, <var data-var='time'>11:17</var> UTC Update - We continue to validate the fix for the trim() Cypher function. Further updates will be provided before we begin deploying it to Aura instances. Aug <var data-var='date'> 6</var>, <var data-var='time'>07:39</var> UTC Update - We continue to validate the fix for the trim() Cypher function. Further updates will be provided before we begin deploying it to Aura instances. Aug <var data-var='date'> 6</var>, <var data-var='time'>07:13</var> UTC Update - We are actively validating the fix for the trim() Cypher function. Further updates will be provided before we begin deploying to Aura instances Aug <var data-var='date'> 6</var>, <var data-var='time'>00:58</var> UTC Update - We are testing the fix for the trim() Cypher function issue. We will update before we begin our deployment into the Aura environment. Aug <var data-var='date'> 5</var>, <var data-var='time'>19:27</var> UTC Identified - We have found the issue and are working on a fix. A small percentatge of queries using trim may still err. VDC customers with databases set to highest are not impacted at all unless they pause and start their instances. Aug <var data-var='date'> 5</var>, <var data-var='time'>17:31</var> UTC Investigating - We have identified an issue currently that could result in unexpected query failures when using the trim() Cypher function. Investigations into the cause are in progress.

Potential unexpected query failures.

Jul <var data-var='date'>24</var>, <var data-var='time'>15:56</var> UTC Resolved - All fixes have been deployed and issue is now marked as resolved. Jul <var data-var='date'>24</var>, <var data-var='time'>12:59</var> UTC Update - All identified instances have been fix, continuing to monitor. Contact customer support for any further issues. Jul <var data-var='date'>24</var>, <var data-var='time'>08:30</var> UTC Update - We are continuing to monitor for any further issues. Jul <var data-var='date'>24</var>, <var data-var='time'>06:00</var> UTC Update - We are continuing to monitor the situation closely for any further issues. Jul <var data-var='date'>24</var>, <var data-var='time'>02:56</var> UTC Update - We are continuing to monitor the situation closely for any further issues. Jul <var data-var='date'>24</var>, <var data-var='time'>01:02</var> UTC Update - We are continuing to monitor for any further issues. Jul <var data-var='date'>23</var>, <var data-var='time'>22:28</var> UTC Update - We are continuing to monitor for any further issues. Jul <var data-var='date'>23</var>, <var data-var='time'>19:39</var> UTC Update - We continue to fix a small subset of Free instances that are still impacted. Jul <var data-var='date'>23</var>, <var data-var='time'>18:07</var> UTC Update - We addressed the issue in all AuraDB Professional instances. Aura Free can still be affected. We will continue to monitor and fix the remaining databases. Jul <var data-var='date'>23</var>, <var data-var='time'>17:31</var> UTC Update - We continue to fix a small subset of instances that are still impacted under the AuraDB Professional and Free tiers. Jul <var data-var='date'>23</var>, <var data-var='time'>17:01</var> UTC Update - We continue to fix a subset of instances that are still impacted for AuraDB Professional and Free Jul <var data-var='date'>23</var>, <var data-var='time'>16:32</var> UTC Update - We continue to resolve the subset of instances that are still impacted for AuraDB Professional and Free Jul <var data-var='date'>23</var>, <var data-var='time'>15:57</var> UTC Update - We continue to resolve the subset of instances that are still impacted for AuraDB Professional and Free. Jul <var data-var='date'>23</var>, <var data-var='time'>15:29</var> UTC Update - We continue to resolve the subset of instances which are still impacted for AuraDB Professional and Free. Jul <var data-var='date'>23</var>, <var data-var='time'>15:03</var> UTC Update - AuraDB Virtual Dedicated Cloud and AuraDB Business Critical should all now be fixed. We continue to resolve the subset of instances which are still impacted for AuraDB Professional and Free. Jul <var data-var='date'>23</var>, <var data-var='time'>14:44</var> UTC Monitoring - We continue to resolve the subset of instances which are still impacted. Jul <var data-var='date'>23</var>, <var data-var='time'>14:27</var> UTC Update - We continue to resolve the subset of instances which are still impacted. Jul <var data-var='date'>23</var>, <var data-var='time'>14:07</var> UTC Update - We are continuing to resolve the subset of instances still impacted. Jul <var data-var='date'>23</var>, <var data-var='time'>13:35</var> UTC Update - We are continuing to resolve the subset of instances still impacted. Jul <var data-var='date'>23</var>, <var data-var='time'>13:09</var> UTC Update - We are continuing to resolve the subset of instances still impacted. Jul <var data-var='date'>23</var>, <var data-var='time'>12:49</var> UTC Update - With the configuration fix deployed, we are continuing to resolve the subset of instances still impacted. Jul <var data-var='date'>23</var>, <var data-var='time'>12:32</var> UTC Update - We have deployed a configuration fix and are now working to resolve the subset of instances impacted. Jul <var data-var='date'>23</var>, <var data-var='time'>12:11</var> UTC Update - We have identified the subset of instances impacted and continue to deploy the fix at this time. Jul <var data-var='date'>23</var>, <var data-var='time'>11:53</var> UTC Update - We are deploying the first part of the fix and continue actively working on rolling out the full solution. We expect an ETA in the order of 1hour from now. Jul <var data-var='date'>23</var>, <var data-var='time'>11:38</var> UTC Identified - We have identified the cause of the current issue and are actively working on the fix currently. Jul <var data-var='date'>23</var>, <var data-var='time'>11:24</var> UTC Update - We are working with engineering teams and continuing to make progress with the investigations at the current time. Jul <var data-var='date'>23</var>, <var data-var='time'>11:08</var> UTC Update - We are working with engineering teams and making progress with the investigations at the current time. Jul <var data-var='date'>23</var>, <var data-var='time'>10:52</var> UTC Investigating - We are currently investigating an issue at this time.

Issue impacting Aura instance operations

Jul <var data-var='date'>10</var>, <var data-var='time'>19:23</var> UTC Resolved - Services are confirmed to be operational and no further interruptions are expected. Jul <var data-var='date'>10</var>, <var data-var='time'>17:51</var> UTC Monitoring - The third-party service that Aura depends on has restored normal operations and the Neo4j Aura systems have recovered. Our team is actively monitoring the issue to confirm Aura Console is performing as expected. Jul <var data-var='date'>10</var>, <var data-var='time'>17:23</var> UTC Update - We are continuing to investigate this issue. Jul <var data-var='date'>10</var>, <var data-var='time'>17:18</var> UTC Investigating - We are currently investigating an issue affecting the Aura Console where some customers may be unable to see their instances. This issue is caused by a failure in a third-party service that Aura depends on. Affected instances continue to run normally, and database connectivity is not impacted. Our team is actively investigating the issue.

Aura Console Impacted - Instance View

Jun <var data-var='date'>30</var>, <var data-var='time'>17:45</var> UTC Resolved - The fix has been fully deployed to all impacted instances. This incident is now resolved. Jun <var data-var='date'>30</var>, <var data-var='time'>16:05</var> UTC Monitoring - A fix is rolling out and progressing well. We will update with progress. Jun <var data-var='date'>30</var>, <var data-var='time'>15:41</var> UTC Update - We are starting now to deploy a fix to address this issue and will provide an update soon on progress. Jun <var data-var='date'>30</var>, <var data-var='time'>14:45</var> UTC Identified - Running CREATE VECTOR INDEX fails with error 51N31 error: system configuration or operation exception - not supported. Creating a vector index with provided settings is not supported in V2026_02. Required version for operation is V2026_06. Please upgrade DBMS.. This only affects new index, existing VECTOR INDEX are unaffected. Any vector index created prior to 2026-06-30 at 09:00 continue to operate normally.

AuraDB issue: Errors when running CREATE VECTOR INDEX

Jun <var data-var='date'>24</var>, <var data-var='time'>09:14</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>24</var>, <var data-var='time'>09:14</var> UTC Update - We have checked and confirm that the issue is now fully addressed. Jun <var data-var='date'>23</var>, <var data-var='time'>19:27</var> UTC Update - Continuing to monitor the deployed changes. Next update expected 6/24/2026 10am UTC. Jun <var data-var='date'>23</var>, <var data-var='time'>15:43</var> UTC Monitoring - We are deploying a change. We will monitor and update. Jun <var data-var='date'>23</var>, <var data-var='time'>13:39</var> UTC Update - We are continuing to work on a fix for this issue. Jun <var data-var='date'>23</var>, <var data-var='time'>13:03</var> UTC Update - We are continuing to investigate a fix for the issue Jun <var data-var='date'>23</var>, <var data-var='time'>11:25</var> UTC Identified - Aura console is experiencing some intermittent errors: "Our system is experiencing problems right now. try again later or contact support if the problem persists." This may require you to reload or wait longer for navigating in the console Operations and the Aura API remain unaffected We are actively working on a fix

Aura console experiencing some intermittent errors

May <var data-var='date'>26</var>, <var data-var='time'>23:06</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>26</var>, <var data-var='time'>19:19</var> UTC Monitoring - The Aura Console issue has now been resolved. The root cause was a failure while fetching public certificates from Auth0. We are reaching out to the Auth0 team to gather more detailed information about the incident. May <var data-var='date'>26</var>, <var data-var='time'>18:23</var> UTC Investigating - Aura Console is currently not accessible. Our team is investigating the issue. Aura instances are running normally and are not impacted. They remain accessible via https://browser.neo4j.io/ and https://bloom.neo4j.io/ Console-related administration and configuration procedures may be unavailable. We will provide updates as soon as more information is available.

Aura Console Auth error

Mar <var data-var='date'> 6</var>, <var data-var='time'>16:06</var> UTC Resolved - While AWS continues working on this situation, we are closing this incident and invite our customers to monitor the AWS Status on our main Neo4j Status Page under AWS (Amazon Web Services). The latest information from AWS can be found at: https://health.aws.amazon.com/health/status Mar <var data-var='date'> 6</var>, <var data-var='time'>14:29</var> UTC Update - We continue to monitor the situation in the affected AWS Middle East regions. The latest information from AWS is available at: https://health.aws.amazon.com/health/status We will provide additional updates as more information becomes available. Please review the AWS recommendation on the website above. Mar <var data-var='date'> 6</var>, <var data-var='time'>02:08</var> UTC Update - We continue to monitor the situation in the affected AWS Middle East regions. The latest information from AWS is available at: https://health.aws.amazon.com/health/status We will provide additional updates as more information becomes available. Please review the AWS recommendation on the website above. Mar <var data-var='date'> 5</var>, <var data-var='time'>14:39</var> UTC Update - We continue to monitor the situation in the affected AWS Middle East regions. The latest information from AWS is available at: https://health.aws.amazon.com/health/status We will provide additional updates as more information becomes available. Please review the AWS recommendation on the website above. Mar <var data-var='date'> 5</var>, <var data-var='time'>02:42</var> UTC Update - We continue to monitor the situation in the affected AWS Middle East regions. The latest information from AWS is available at: https://health.aws.amazon.com/health/status We will provide additional updates as more information becomes available. Please review the AWS recommendation on the website above. Mar <var data-var='date'> 4</var>, <var data-var='time'>10:10</var> UTC Update - We continue to monitor the situation in the affected AWS Middle East regions. The latest information from AWS is available at: https://health.aws.amazon.com/health/status We will provide additional updates as more information becomes available. Please review the AWS recommendation on the website above. Mar <var data-var='date'> 3</var>, <var data-var='time'>22:43</var> UTC Update - We continue to monitor the situation in the affected AWS Middle East regions. The latest information from AWS is available at: https://health.aws.amazon.com/health/status We will provide additional updates as more information becomes available. Please review the AWS recommendation on the website above. Mar <var data-var='date'> 3</var>, <var data-var='time'>15:26</var> UTC Update - We continue to monitor the situation in the affected AWS Middle East regions. The most up-to-date information from AWS is available at: https://health.aws.amazon.com/health/status We will provide additional updates as soon as more information becomes available. Mar <var data-var='date'> 3</var>, <var data-var='time'>06:19</var> UTC Update - We continue to monitor the situation in the affected AWS Middle East regions. The most up-to-date information from AWS is available at: https://health.aws.amazon.com/health/status We will provide additional updates as soon as more information becomes available. Mar <var data-var='date'> 2</var>, <var data-var='time'>19:55</var> UTC Identified - We are aware of issues in the Middle East regions via our cloud partner AWS, affecting AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain). The most up-to-date information from AWS is available at: https://health.aws.amazon.com/health/status We are actively working to limit the impact on the Aura service. However, customers should expect that new deployments in the affected regions may be impaired. Additionally, existing services deployed in these regions may experience reduced availability. Customers with services in these or nearby regions who are concerned about potential operational impact are encouraged to contact Neo4j Customer Support through the usual channels. Our team is available to advise and assist as needed.

Middle East Availability - AWS

Mar <var data-var='date'> 6</var>, <var data-var='time'>10:25</var> UTC Resolved - We have checked and confirm that the issue is now fully addressed. Mar <var data-var='date'> 6</var>, <var data-var='time'>10:24</var> UTC Monitoring - We have made a code change and we believe the console is available again. Mar <var data-var='date'> 6</var>, <var data-var='time'>10:18</var> UTC Identified - We identified an issue with the availability of console.neo4j.io - we are investigating

Console is not available

Mar <var data-var='date'> 4</var>, <var data-var='time'>15:19</var> UTC Resolved - The fix has been fully deployed to all impacted instances. This incident is now resolved. Mar <var data-var='date'> 4</var>, <var data-var='time'>14:07</var> UTC Monitoring - The fix has now been deployed to those instances impacted and we are monitoring the situation. Mar <var data-var='date'> 4</var>, <var data-var='time'>04:52</var> UTC Update - The fix is being deployed and the status page will be updated upon completion of the full deployment Mar <var data-var='date'> 4</var>, <var data-var='time'>01:39</var> UTC Update - The fix is being deployed and the status page will be updated upon completion of the full deployment of the fix. Mar <var data-var='date'> 3</var>, <var data-var='time'>21:35</var> UTC Identified - A recent update resulted in MERGE queries which referenced the same merged property on both the left and right hand side of an ON MATCH SET or ON CREATE SET clause deleting that property from the node, or setting it to an invalid value during query runtime. The node being matched against must have had at least one property uniqueness constraint present. A fix has been identified and will be applied as soon as possible. Instances marked as "Production" are not impacted.

Subset of MERGE queries lead to setting unexpected property values

Jan <var data-var='date'>27</var>, <var data-var='time'>15:58</var> UTC Resolved - The fix has been fully deployed to all impacted instances. This incident is now resolved. Jan <var data-var='date'>27</var>, <var data-var='time'>14:51</var> UTC Update - We are continuing to monitor the situation at this time. Jan <var data-var='date'>27</var>, <var data-var='time'>11:10</var> UTC Monitoring - The fix has rolled out to the affected components, we are now monitoring the situation at this time. Jan <var data-var='date'>27</var>, <var data-var='time'>09:50</var> UTC Update - We are rolling out the fix and will update you when this is completed. Jan <var data-var='date'>27</var>, <var data-var='time'>01:37</var> UTC Update - We have identified a solution for this issue and will be rolling out in Aura. Once the update has been deployed we will update this tatus page. Jan <var data-var='date'>26</var>, <var data-var='time'>19:26</var> UTC Identified - We have identified an issue that may affect a limited set of Cypher 25 queries for AuraDB Free, Professional and AuraDS. This may affect: - Queries using the conditional query WHEN in combination with a non-grouping aggregation over null values result in an incorrect number of rows returned. - Queries using NEXT can produce an unexpected variable not defined error in some instances. We are actively working on a fix and will update this page as more information becomes available.

Limited set of queries impacted by Cypher 25 issue

Jan <var data-var='date'>16</var>, <var data-var='time'>19:36</var> UTC Resolved - All instances should have the fix applied and if not it should be in the next 60 minutes Jan <var data-var='date'>16</var>, <var data-var='time'>17:07</var> UTC Monitoring - The fix is currently rolling out to production. We will update you upon completion Jan <var data-var='date'>16</var>, <var data-var='time'>15:13</var> UTC Update - Our teams have a fix and initiated the work to get it ready to roll-out. No current ETA available. We will keep you updated soon. Jan <var data-var='date'>16</var>, <var data-var='time'>14:25</var> UTC Identified - Impact is that currently it is not possible to load data into GDS via native projection. Customers using Aura Graph Analytics are not impacted. We have identified a packaging issue with the latest release of Aura. Our engineering team is working on a fix.

Data science feature on AuraDS , AuraDSE and Aura Professional tiers - Native projection affected.

Dec <var data-var='date'>11</var>, <var data-var='time'>15:39</var> UTC Resolved - Cloud resources have become available in USEAST2 and no further customer impact has been detected. This incident is resolved. Dec <var data-var='date'>11</var>, <var data-var='time'>10:24</var> UTC Monitoring - Cloud resources have become available in USEAST2 and we will monitor for a few hours to ensure there is no further customer impact. Dec <var data-var='date'> 5</var>, <var data-var='time'>16:59</var> UTC Update - The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region. We are working with our cloud partner and will resume updates once we have an ETA to share. Dec <var data-var='date'> 5</var>, <var data-var='time'>10:20</var> UTC Update - The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, affecting the following operations: Create, Resize (CPU and Storage), Pause, Resume. If Azure resources are unavailable when requesting these types of Neo4j Aura operations, they will fail and the Neo4j Aura instance may become unavailable or degraded until Azure is able to provision additional resources. Dec <var data-var='date'> 4</var>, <var data-var='time'>09:52</var> UTC Update - The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, affecting the following operations: Create, Resize (CPU and Storage), Pause, Resume. If Azure resources are unavailable when requesting these types of Neo4j Aura operations, they will fail and the Neo4j Aura instance may become unavailable or degraded until Azure is able to provision additional resources. Dec <var data-var='date'> 3</var>, <var data-var='time'>10:52</var> UTC Update - The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, affecting the following operations: Create, Resize (CPU and Storage), Pause, Resume. If Azure resources are unavailable when requesting these types of Neo4j Aura operations, they will fail and the Neo4j Aura instance may become unavailable or degraded until Azure is able to provision additional resources. Dec <var data-var='date'> 2</var>, <var data-var='time'>10:03</var> UTC Update - The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, affecting the following operations: Create, Resize (CPU and Storage), Pause, Resume. If Azure resources are unavailable when requesting these types of Neo4j Aura operations, they will fail and the Neo4j Aura instance may become unavailable or degraded until Azure is able to provision additional resources. Dec <var data-var='date'> 1</var>, <var data-var='time'>09:54</var> UTC Update - The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, effecting the following operations: Create, Resize (CPU and Storage), Pause, Resume. If Azure resources are unavailable when requesting these types of Neo4j Aura operations, they will fail and the Neo4j Aura instance may become unavailable or degraded until Azure is able to provision additional resources. Nov <var data-var='date'>28</var>, <var data-var='time'>16:23</var> UTC Update - We continue to work with Microsoft Azure. No expected improvements in addressing the issues around cloud resources in the affected regions before next week. Aura operations affected: Create, Resize (CPU and Storage), Pause, Clone, Resume. We will resume updates after this weekend or earlier if we have more information. Nov <var data-var='date'>28</var>, <var data-var='time'>10:55</var> UTC Update - We continue to work with our cloud infrastructure provider. Aura operations affected: Create, Resize (CPU and Storage), Pause, Clone, Resume. Nov <var data-var='date'>28</var>, <var data-var='time'>08:54</var> UTC Update - We continue to work with our cloud infrastructure provider. Aura operations affected: Create, Resize (CPU and Storage), Pause, Clone, Resume. Nov <var data-var='date'>28</var>, <var data-var='time'>04:54</var> UTC Update - We continue to work with our cloud infrastructure provider. Aura operations affected: Create, Resize (CPU and Storage), Pause, Clone, Resume. Nov <var data-var='date'>28</var>, <var data-var='time'>00:09</var> UTC Update - We continue to work with our cloud infrastructure provider . Aura operations affected: Create, Resize (CPU and Storage), Pause, Clone, Resume. Nov <var data-var='date'>27</var>, <var data-var='time'>20:11</var> UTC Update - We continue to work with our cloud infrastructure provider. Aura operations affected: Create, Resize (CPU and Storage), Pause, Clone, Resume. Nov <var data-var='date'>27</var>, <var data-var='time'>17:07</var> UTC Update - The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, effecting the following operations: Create, Resize (CPU and Storage), Pause, Clone, Resume. As Azure resources become available when performing some Aura operations, the impacted instances may progressively recover and operations successfully complete. We continue to monitor progress, work with Microsoft Azure Infrastructure issues and will update. Nov <var data-var='date'>27</var>, <var data-var='time'>14:33</var> UTC Update - The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, effecting the following operations: Create, Resize (CPU and Storage), Pause, Resume. If Azure resources are unavailable when requesting these types of Neo4j Aura operations, they will fail and the Neo4j Aura instance will become unavailable until Azure is able to provision additional resources. Nov <var data-var='date'>27</var>, <var data-var='time'>10:52</var> UTC Update - The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, effecting the following operations: Create, Resize (CPU and Storage), Pause, Resume. If Azure resources are unavailable when requesting these types of Neo4j Aura operations, they will fail and the Neo4j Aura instance will become unavailable until Azure is able to provision additional resources. Nov <var data-var='date'>26</var>, <var data-var='time'>20:33</var> UTC Update - Neo4j continues working with Microsoft via an Azure cloud ticket and is awaiting updates on their resolution of the Azure Infrastructure issues. Some resources have been made available, and impacted Neo4j Services have resumed operation. Customers have been notified. The Neo4j Aura Service is impacted when performing the following operations: Create, Resize (CPU and Storage), Pause, Resume. If Azure resources are unavailable when requesting these types of Neo4j operations, the operation will fail, and the Neo4j instance will become unavailable until Azure is able to provision additional resources. Nov <var data-var='date'>26</var>, <var data-var='time'>15:47</var> UTC Identified - Neo4j opened a ticket with Azure and is awaiting updates on their resolution of the Azure Infrastructure issues. Impact on Neo4j Aura Services: Create, Resize (CPU and Storage), Pause, Resume.

Neo4j Aura Service impacted by Resource Shortage in Azure US East

Nov <var data-var='date'>18</var>, <var data-var='time'>16:39</var> UTC Resolved - After monitoring the fix for some time, we can confirm that the issue is resolved and normal operations have resumed. Nov <var data-var='date'>18</var>, <var data-var='time'>16:16</var> UTC Monitoring - We have released a fix to this issue and are monitoring to ensure all operations are back to normal. Nov <var data-var='date'>18</var>, <var data-var='time'>15:56</var> UTC Identified - We have identified an issue resulting in Pause, Resume and Delete operations to fail in both Console and Aura API across all tiers of Aura. We are actively working to resolve the issue and will report progress.

Pause / Resume / Destroy operations failing

Oct <var data-var='date'>20</var>, <var data-var='time'>21:28</var> UTC Resolved - Instance operations in AWS us-east-1 region are back to normal following the resolution of the AWS incident. We will continue to monitor but all data indicates that the issue is fully resolved at this time. Oct <var data-var='date'>20</var>, <var data-var='time'>19:14</var> UTC Update - We are continuing to monitor the AWS incident, and can report some slow improvement of impacted Aura instances in the AWS us-east1 region, though the service remains degraded in this region at this time. We are continuing to monitor progress in the AWS incident: https://health.aws.amazon.com/health/status Oct <var data-var='date'>20</var>, <var data-var='time'>16:43</var> UTC Identified - Many core operations for instances in AWS region us-east-1 are degraded as a result of AWS incident in that region: https://health.aws.amazon.com/health/status Core operations include create, pause, resume, clone, backup, among others. We continue to monitor the AWS incident and will provide updates accordingly.

Several operations degraded for AWS instances in region us-east-1

Oct <var data-var='date'>20</var>, <var data-var='time'>11:13</var> UTC Resolved - The underlying AWS incident has bene resolved and our services have now resumed and fully recovered Oct <var data-var='date'>20</var>, <var data-var='time'>10:32</var> UTC Update - We are continuing to see good recovery across the service. We will update when this is completed. Oct <var data-var='date'>20</var>, <var data-var='time'>09:58</var> UTC Monitoring - We see clear signs of recovery and our impacted service are progressively getting back to normal. We will monitor and update when we can confirm full recovery and normal operations. Oct <var data-var='date'>20</var>, <var data-var='time'>09:39</var> UTC Update - Operations such as Create, Pause, Resume, Clone are affected globally due to a dependency. Backups in the affected region of AWS us-est-1 will be impacted The affected AWS service is now starting to recover and we are monitoring the situation Oct <var data-var='date'>20</var>, <var data-var='time'>09:15</var> UTC Identified - An active issue on AWS us-east-1 is affecting Neo4j Aura operations in the regions where we have some dependency on an impacted AWS service. See more details https://health.aws.amazon.com/health/status Other regions not currently impacted.

Aura operations on AWS affected by an incident in US-EAST-1 region

Aug <var data-var='date'>27</var>, <var data-var='time'>16:46</var> UTC Resolved - The full fix for the solution has now been deployed across the estate and this issue is now resolved. Aug <var data-var='date'>27</var>, <var data-var='time'>11:16</var> UTC Update - The full fix for the solution is continuing to be deployed across the estate and are continuing to monitor the situation. Aug <var data-var='date'>27</var>, <var data-var='time'>06:36</var> UTC Update - We are continuing to monitor for any further issues. Aug <var data-var='date'>26</var>, <var data-var='time'>23:12</var> UTC Update - The full fix for the solution is starting to be deployed across the estate and are continuing to monitor the situation. Aug <var data-var='date'>26</var>, <var data-var='time'>20:13</var> UTC Update - The full fix for the solution is starting to be deployed across the estate and are continuing to monitor the situation. Aug <var data-var='date'>26</var>, <var data-var='time'>17:17</var> UTC Update - The full fix for the solution is starting to be deployed across the estate and are continuing to monitor the situation. Aug <var data-var='date'>26</var>, <var data-var='time'>14:48</var> UTC Update - We are continuing to monitor the situation. The full fix for the solution is currently undergoing final testing and will start deployment once testing is completed. Aug <var data-var='date'>26</var>, <var data-var='time'>10:53</var> UTC Update - We are continuing to monitor the situation whilst a full fix for the solution is prepared. Aug <var data-var='date'>26</var>, <var data-var='time'>04:06</var> UTC Update - We are continuing to investigate this issue. Aug <var data-var='date'>25</var>, <var data-var='time'>21:44</var> UTC Update - We continue to work towards the issue resolution. Aug <var data-var='date'>25</var>, <var data-var='time'>17:40</var> UTC Update - We continue to work towards the issue resolution. Aug <var data-var='date'>25</var>, <var data-var='time'>15:34</var> UTC Monitoring - The issue impact has been refined and currently could impact AuraDB Virtual Dedicated Cloud and Business Critical instances only. We have identified the cause and the faulty component has been reverted for the majority of instances. We will continue to monitor the situation, while the full fix is prepared. Aug <var data-var='date'>25</var>, <var data-var='time'>13:47</var> UTC Update - We are continuing to investigate this issue. Aug <var data-var='date'>25</var>, <var data-var='time'>13:36</var> UTC Update - We are aware of an issue that could result in a degradation in write performance for all Aura instance. We have identified the cause and are preparing a fix. Aug <var data-var='date'>25</var>, <var data-var='time'>13:34</var> UTC Investigating - We are currently investigating this issue.

Database instance write performance impacted

Aug <var data-var='date'>22</var>, <var data-var='time'>13:31</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>22</var>, <var data-var='time'>11:42</var> UTC Monitoring - A fix has been identified and implemented. Instances should be showing on the console and instance operations should now be available. You should now also be able to ingest metrics using CMI. We are continuing to monitor the status of these services. Aug <var data-var='date'>22</var>, <var data-var='time'>11:02</var> UTC Investigating - Engineers are investigating an issue whereby instance actions are not working. You may be unable to import data, pause, resume, create, delete or run manual backups for your instances. Regular Neo4j scheduled backups are continuing to run as normal. You may be unable to see your instances in the Aura Console. CMI is also experiencing an outage, you may be unable to ingest metrics from your Aura instances.

CMI & Instance Operations Unavailable

Aug <var data-var='date'>19</var>, <var data-var='time'>12:04</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>19</var>, <var data-var='time'>11:30</var> UTC Monitoring - The fix has been deployed and we will continue to monitor this incident. Aug <var data-var='date'>19</var>, <var data-var='time'>10:51</var> UTC Update - We continue to investigate and have identified the issue more clearly. Beyond backups, other operations are also affected: pause and clone. Operations may fail or take a long time to complete. Aug <var data-var='date'>19</var>, <var data-var='time'>10:34</var> UTC Update - We are continuing to investigate this issue. Aug <var data-var='date'>19</var>, <var data-var='time'>10:05</var> UTC Update - We are continuing to investigate the issue with backups. New backups after 0:00 last night are failing to complete. Existing backups are unaffected and remain available. Aug <var data-var='date'>19</var>, <var data-var='time'>09:19</var> UTC Investigating - We are currently investigating an issue with backups. We will update shortly as we get more details

Some issues with backups

Jul <var data-var='date'> 3</var>, <var data-var='time'>18:32</var> UTC Resolved - We have applied a fix and verified this is fully resolved. Jul <var data-var='date'> 2</var>, <var data-var='time'>05:17</var> UTC Update - We have identified the issue and a fix is being rolled out Jun <var data-var='date'>30</var>, <var data-var='time'>20:40</var> UTC Identified - We have identified an issue where the PUBLIC role cannot be modified on certain Business Critical instances. The public role is available to all database users, and contains a limited set of privileges outlined in our documentation: https://neo4j.com/docs/operations-manual/current/authentication-authorization/built-in-roles/#access-control-built-in-roles-public

Public role privilege modification impacted for some Business Critical instances

Jun <var data-var='date'>27</var>, <var data-var='time'>10:36</var> UTC Resolved - We have addressed the issue and rolled back a feature involved with this problem. Jun <var data-var='date'>27</var>, <var data-var='time'>09:48</var> UTC Investigating - AuraDB Business Critical customers may face issues with running queries. We are investigating Error returned: ACCESS on database 'neo4j' is not allowed for user 'neo4j' with roles [PUBLIC]

Is Neo4j Aura down?

Neo4j Aura status is UP

Lastest published events

Issue impacting certain database operations for Aura customers on Azure

Customer support portal issues

Console and API outage

Neo4j Aura Services, Components and Regions

Recent Neo4j Aura events

Issue impacting certain database operations for Aura customers on Azure

Customer support portal issues

Console and API outage

A small number of Free Tier instances are experiencing issues updating

Aura metrics issue.

Potential unexpected query failures.