# Changes and updates to Neptune Analytics
<a name="doc-history"></a>

The following table lists important releases relating to Neptune Analytics.

| Change | Description | Date | 
| --- |--- |--- |
| [General improvements](#doc-history) | Performance and availability improvements | March 9, 2026 | 
| [Neptune Analytics regional expansion](#doc-history) | Neptune Analytics is now available in 14 additional regions: `us-west-1` US West (N. California), `ap-northeast-2` Asia Pacific (Seoul), `ap-northeast-3` Asia Pacific (Osaka), `eu-north-1` Europe (Stockholm), `eu-west-3` Europe (Paris), `sa-east-1` South America (São Paulo), `ap-east-1` Asia Pacific (Hong Kong), `me-south-1` Middle East (Bahrain), `me-central-1` Middle East (UAE), `il-central-1` Israel (Tel Aviv), `af-south-1` Africa (Cape Town), `ca-west-1` Canada West (Calgary), `ap-southeast-5` Asia Pacific (Malaysia), and `eu-central-2` Europe (Zurich). Note that the `ap-northeast-2d` Availability Zone is not available for Neptune Analytics in the `ap-northeast-2` region. | February 25, 2026 | 
| [Performance Improvement](#doc-history) | Improved `vectors.topK.byEmbedding` algorithm performance | December 22, 2025 | 
| [Issue fix](#doc-history) | Fixed an issue where queries returned an `Operation terminated (internal error)` in some cases. | December 22, 2025 | 
| [Performance Improvement](#doc-history) | Reduced the memory requirement for all Neptune Analytics graphs. With this release, graph analytics may be performed in smaller capacity units (m-NCUs). | November 10, 2025 | 
| [Performance Improvement](#doc-history) | Improvements to the running time of queries using distinct aggregation. Improvements to the memory use of many queries, particularly those using “CALL” and “DISTINCT”. | November 10, 2025 | 
| [Graph algorithm updates](#doc-history) | Added `degreeDistribution` algorithm. Added support for multiple vertex label filtering for `.degree`, `.degree.mutate`, `.louvain`, and `.louvain.mutate` algorithms. Added `vectors.distance.byNode`, `vectors.distance.byEmbedding`, `vectors.topK.byNode`, algorithms. Deprecated `vectors.distance`, `vectors.distancebyEmbedding`, `vectors.topKbyNode`, `vectors.topKbyEmbedding` algorithms. | November 10, 2025 | 
| [Data operations bug fix](#doc-history) | Fixed bug causing engine crash for some queries using “OPTIONAL MATCH” or “DISTINCT”. | November 10, 2025 | 
| [Neptune Analytics is now available in two new regions](#doc-history) | Neptune Analytics available in the `ca-central-1` Canada (Central) and `ap-southeast-2` Asia Pacific (Sydney) regions. | October 10, 2025 | 
| [Neptune Analytics available in Asia Pacific (Mumbai) region](#doc-history) | Neptune Analytics is now available in the `ap-south-1` Asia Pacific (Mumbai) region. | September 26, 2025 | 
| [Start/Stop API](#doc-history) |  Neptune Analytics now offers Start graph API and Stop graph API. For more information see [Managing your Neptune Analytics graph](https://docs.aws.amazon.com//neptune-analytics/latest/userguide/managing.html).  | August 25, 2025 | 
| [Query update](#doc-history) |  Resolved an issue where using a `WITH` clause that contained an asterisk (`*`) and aliasing expressions caused incorrect query parsing in OpenCypher.  | April 28, 2025 | 
| [Graph algorithm updates](#doc-history) |  Neptune Analytics now offers the Louvain algorithm. Additionally, the `personalization` parameter has been added to the pageRank algorithm.  | April 28, 2025 | 
| [Graph algorithm bug fix](#doc-history) |  Resolved an issue in `pg_info` where labelless vertices were being counted incorrectly.  | April 28, 2025 | 
| [Data operations bug fix](#doc-history) |  Resolved an issue in the bulk loader that caused `failOnError` to behave incorrectly when parsing embeddings.  | April 28, 2025 | 
| [Data operations bug fix](#doc-history) |  The error messages in bulk load are now more user friendly.  | April 28, 2025 | 
| [Data operations bug fix](#doc-history) |  Neptune Analytics is now reporting an error message if the csv lines are too long to load. Example error message: [ETL] Could not form a complete line for parsing. Please check if you are loading lines longer than 65535.  | April 28, 2025 | 
| [Data operations bug fix](#doc-history) |  An issue was resolved that caused the database to be shut down when users tried to access files in Amazon S3 without the proper permissions.  | April 28, 2025 | 
| [Query `REDUCE` function](#doc-history) |  Added support for the OpenCypher `REDUCE` function, allowing a list of values to be combined using a user-defined expression.  | February 26, 2025 | 
| [Improved memory management in Closeness Centrality algorithm](#doc-history) |  In the Closeness Centrality algorithm, a memory/performance tradeoff has been added to enable execution on smaller instances.  | February 26, 2025 | 
| [Fixed incorrect results while setting Map properties from a nested map](#doc-history) |  An issue has been resolved where incorrect results occurred when setting map properties from nested maps in Amazon Neptune (e.g. `WITH {struct: {prop: "val"}} as row MATCH (n:label) SET n+=row.struct RETURN n`). This fix ensures that map properties are correctly assigned and retrieved, providing accurate and reliable data handling when working with complex nested structures in graph queries.  | February 26, 2025 | 
| [Vertex lookup](#doc-history) |  Improved vertex lookup performance and memory footprint.  | November 15, 2024 | 
| [Snapshot creation issue](#doc-history) |  Fixed an issue that prevented statistics from being included in graph snapshots. Graphs created by restoring such a snapshot will not initially have statistics available, and may experience degraded query performance.  | November 15, 2024 | 
| [Query plan cache update](#doc-history) |  Disabled query plan cache by default for parameterized mutation queries to avoid potential InternalFailureException.  | November 15, 2024 | 
| [Query improvement - Internal failure](#doc-history) |  Fixed an issue where using COLLECT(DISTINCT()) returned an InternalFailureException in some cases.  | November 15, 2024 | 
| [Query improvement - Internal failure](#doc-history) |  Fixed InternalFailureException when user uses a value of unsupported type with aggregation functions (ie sum(<string>)).  | November 15, 2024 | 
| [Query improvement - ID match](#doc-history) |  Correct `~id` match behavior. Invalid `~id` values like null or non-string types lead to zero match for MATCH (ie. `MATCH (n {`~id`: null})` ) or type error thrown for MERGE/CREATE (ie. `CREATE (n {`~id`: null})`).  | November 15, 2024 | 
| [Query improvement](#doc-history) |  Fixed an issue where some limit queries only return partial results during execution.  | November 15, 2024 | 
| [Property support over mixed type entities](#doc-history) |  Support for property/properties over ambiguous/mixed type entities. This avoids the error for queries failing with "Property access/properties over ambiguous type not supported in this release".  | November 15, 2024 | 
| [Performance improvement](#doc-history) |  Improved performance for queries that use numeric algorithm output for result ordering.  | November 15, 2024 | 
| [Performance improvement](#doc-history) |  Improved performance for queries which use large static lists or maps. Certain queries related to vector upsert or search algorithms, where a static list of float values is passed as an embedding, have seen significant performance enhancements. A sample vector.upsert query can be seen [here](https://docs.aws.amazon.com//neptune-analytics/latest/userguide/vectors-upsert.html#vectors-upsert-query-example).  | November 15, 2024 | 
| [CALL subquery support](#doc-history) |  Added Support for `CALL` subquery, allowing execution of operations within a defined scope. A `CALL` subquery is executed once for each incoming row and the variables returned in a subquery are available to the outer scope of the enclosing query. Variables from outer scope can be imported into a `CALL` subquery using an importing WITH clause.  | November 15, 2024 | 
| [Algorithm parameter handling fix](#doc-history) |  Fixed an issue where passing concurrency=0 to algorithms returned an error.  | November 15, 2024 | 
| [Byte handling](#doc-history) |  Previously, when data was loaded using the `Byte` data type it was erroneously stored as an unsigned byte, this has been updated to store the data a signed byte. Previously loaded data and queries will not be impacted.  | July 29, 2024 | 
| [Updated float serialization](#doc-history) | Float serialization changed to use a lesser number of digits for higher precision. This will change the float values that are returned from the server. | June 20, 2024 | 
| [UNWIND performance improvement](#doc-history) | Improved the UNWIND operations (e.g. transform a list of values within a property into individual vertices or edges) to help prevent out of memory (OOM) situations. | June 20, 2024 | 
| [Query plan cache update](#doc-history) |  Fixed an issue in query plan cache when `skip` or `limit` is used in an inner `WITH` clause and parameterized. This fix ensures that parameter values for `SKIP` and `LIMIT` are now properly handled, providing accurate results for every execution. If you disabled the query plan cache, you can now remove the query hint `QUERY:PLANCACHE "disabled"` when submitting a query.  | June 20, 2024 | 
| [Increased efficiency when handling special characters](#doc-history) | Fixed an issue with handling of node and relationship labels, node identifiers, and property names containing the “Ā” character (Latin uppercase letter A with Macron, unicode code point U\$10100). | June 20, 2024 | 
| [Datetime formats](#doc-history) |  Extended support for datetime formats.  | June 20, 2024 | 
| [Condition key - neptune-graph:PublicConnectivity](#doc-history) | [ neptune-graph:PublicConnectivity](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonneptuneanalytics.html#amazonneptuneanalytics-policy-keys) filters access by the value of the public connectivity parameter provided in the request or its default value, if unspecified. All access to graphs is IAM authenticated. | April 29, 2024 | 
| [StartImportTask available](#doc-history) | Neptune Analytics now allows you to efficiently import large datasets into an already provisioned graph database using the `StartImportTask` API. This API facilitates the direct loading of data from an Amazon S3 bucket into an **empty** Neptune Analytics graph. This is designed for loading data into existing empty clusters. | March 30, 2024 | 
| [Neptune Analytics available in Europe (London) region](#doc-history) | Neptune Analytics is now available in the `eu-west-2` Europe (London) region. | March 14, 2024 | 
| [Column delimiter `;` is now supported in values](#doc-history) | When a column delimiter presents in the values, e.g. for `'two;words'`, two values \$1'two','words'\$1 will be inserted. However, if the column delimiter is escaped by a backslash `'\'`, the value will be inserted as a whole with the escape character removed, e.g. `'one\;word'` will be inserted as 'one;word'. | February 27, 2024 | 
| [Graph provisioning time reduced to five minutes or less](#doc-history) | Neptune Analytics graphs are now provisioned and ready to be used in five minutes or less. | February 19, 2024 | 
| [Query improvements - Data Plane SDK](#doc-history) | The Neptune Analytics data API provides support for data operations including query execution, query status checking, query cancellation, and graph summarizing via the HTTPS endpoint, the AWS CLI, and the SDK. | February 2, 2024 | 
| [Initial release](#doc-history) | Initial release of Neptune Analytics. | November 29, 2023 |