On November 18, 2025, some customers experienced issues with the delete, pause, and resume operations in the Console. These actions failed due to a temporary system issue introduced during a sequence of updates. While the updates were intended to improve functionality, they unintentionally reintroduced a previously resolved defect.
The issue was identified quickly, and our teams acted immediately to restore normal operation.
The root cause was a misconfiguration in the data processing module. An outdated schema caused the data parsing logic to misinterpret certain input parameters, leading to incorrect behavior and data display within the Console. We have since corrected the schema and added stricter validation to ensure compatibility moving forward.
During the incident, some users experienced service disruptions when accessing the Console. Impacts included:
No customer data was lost.
To prevent a recurrence, we have improved our release process to ensure updates are deployed in the correct order, eliminating overlapping or out-of-sequence changes.
Neo4j takes service reliability seriously and is strengthening safeguards to prevent similar incidents.
New mitigations being deployed include:
We apologize for the disruption and appreciate our customers’ patience as we continue to harden our systems.