CMI functionality has been fully restored and this issue is considered resolved.
Posted Mar 31, 2025 - 15:36 UTC
Monitoring
A fix has been implemented and the CMI feature is responding normally. We will monitor for a short time before considering this resolved.
Posted Mar 31, 2025 - 14:08 UTC
Investigating
We are currently investigating an issue which impact the CMI feature, where requests return HTTP 401.
Posted Mar 31, 2025 - 13:15 UTC
This incident affected: AuraDB Virtual Dedicated Cloud (*.databases.neo4j.io) (AuraDB Virtual Dedicated Cloud on AWS (*.databases.neo4j.io), AuraDB Virtual Dedicated Cloud on Azure (*.databases.neo4j.io), AuraDB Virtual Dedicated Cloud on GCP (*.databases.neo4j.io)), AuraDS Enterprise (*.databases.neo4j.io) (AuraDS Enterprise on AWS (*.databases.neo4j.io), AuraDS Enterprise on Azure (*.databases.neo4j.io), AuraDS Enterprise on GCP (*.databases.neo4j.io)), and AuraDB Business Critical (*.databases.neo4j.io) (AuraDB Business Critical (*.databases.neo4j.io) on AWS, AuraDB Business Critical (*.databases.neo4j.io) on Azure, AuraDB Business Critical (*.databases.neo4j.io) on GCP).