Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Outage in Neo4j Aura

Subset of MERGE queries lead to setting unexpected property values

Resolved Minor
March 03, 2026 - Started about 2 months ago - Lasted about 18 hours
Official incident page

Incident Report

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.

Trusted by 1,000+ teams

Be the First to Know When Vendors Go Down

Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.

IsDown status aggregator dashboard
Latest Updates ( sorted recent to last )
RESOLVED about 2 months ago - at 03/04/2026 03:19PM

The fix has been fully deployed to all impacted instances. This incident is now resolved.

MONITORING about 2 months ago - at 03/04/2026 02:07PM

The fix has now been deployed to those instances impacted and we are monitoring the situation.

IDENTIFIED about 2 months ago - at 03/04/2026 04:52AM

The fix is being deployed and the status page will be updated upon completion of the full deployment

IDENTIFIED about 2 months ago - at 03/04/2026 01:39AM

The fix is being deployed and the status page will be updated upon completion of the full deployment of the fix.

IDENTIFIED about 2 months ago - at 03/03/2026 09:35PM

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.

Be the First to Know When Vendors Go Down

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 6320 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook