Estado de Neo4j Aura

Estado oficial verificado

All systems operational

Incidente oficial resuelto

Issue impacting certain database operations for Aura customers on Azure — Our engineers have successfully deployed a fix, and the issue is now resolved. Aura customers on Azure can now download database snapshots without issues.

Incidente oficial resuelto

Snapshot Downloads Return Blank Dumps — # What happened On Fri, 18 Sep 2026 14:33 UTC, we identified that snapshot downloads for Aura instances hosted on Azure were returning files of approximately 24KB instead of the expected multi-gigabyte size. The underlying backups stored in Azure were the correct size, but the download path in the console was serving near-empty files. The root cause was an Azure credential issue that occurred during a deployment and prevented backup data from being served for download. An initial fix was deployed on Mon, 21 Sep 2026 10:31 UTC, restoring correct download sizes. However, the same credential issue recurred on Tue, 06 Oct 2026 08:20 UTC, again producing blank snapshot downloads across all Azure tiers. Our engineering team identified the recurrence, linked it to the same root cause, deployed a targeted credential fix to production, and verified that downloads returned to their expected size. We did not post to the status page on September 18 because a small number of customers were affected, and we worked with them directly. We posted on October 6 at 09:22 UTC, about an hour after the recurrence began, once it was clearly broader. # How the service was affected Snapshot downloads were impacted for AuraDS Professional and Enterprise, AuraDB Professional, Business Critical and Virtual Dedicated Cloud instances running on Azure. * Snapshot downloads returned unusable files. When customers downloaded snapshots from the console, they received files of roughly 24KB instead of the actual backup data, which could be several gigabytes in size. This made the downloaded snapshots unusable for offline restore or migration purposes. * Backups themselves were not lost. The underlying backup artifacts stored in Azure remained intact and correctly sized. The issue was strictly in the download path, not in the backup capture or storage process. * Restoring via the console was unaffected. In-platform restore operations \(as opposed to downloading a dump file\) continued to function because they accessed the backup data directly rather than through the affected download path. # What we are doing now We have taken multiple steps to resolve the issue and have implemented safeguards to prevent recurrence. * Credential fix deployed. We corrected the Azure credential issue in production, which immediately restored snapshot downloads for all affected instances. * Preventing unintended credential rotation. A code change has been submitted to revert the logic that was triggering Azure credential rotation on every deployment. This ensures that future deployments will not inadvertently invalidate existing credentials, which was the mechanism that caused both the initial incident and its recurrence. * Ongoing monitoring. We are monitoring Azure snapshot downloads across all tiers to confirm they remain stable. We have asked affected customers to verify that their downloads now return the expected file sizes. These changes address both the immediate symptom and the underlying deployment behavior that allowed the issue to recur

Incidente oficial resuelto

AuraDS affected by issues when attempting to restore from snapshot — # What happened A software defect in a central management component of Neo4j Aura snapshot restores to fail for AuraDS Professional and AuraDS Enterprise instances hosted on AWS. When a restore was requested, the system looked up the instance using an incorrect resource type and returned an error. The incident was declared on Monday, 05 Oct 2026 21:52 UTC. Our engineering team identified the root cause, developed and validated a fix, and deployed it to production on Tuesday, 06 Oct 2026 13:37 UTC. # How the service was affected The impact was scoped to snapshot restore operations for AuraDS Professional and AuraDS Enterprise instances. Affected customers were unable to restore snapshots via the Aura Console or the Aura API for the duration of the issue. * Restore attempts returned errors, disrupting workflows that depend on snapshot restores. * Instances remained available throughout this event. Data integrity was not impacted. Restoring from full and exported backups remained available as a workaround. # What we are doing now * We have fixed the defect in Aura's management layer that affected AuraDS Professional and AuraDS Enterprise snapshot restores and deployed the fix to production. * Deployment pipeline optimization: During this incident, the deployment pipeline took longer than ideal due to sequential test instance creation. We have evaluated parallelizing test instance creation to reduce wait times during critical rollouts. This improvement aims to shorten the time it takes to validate and ship a fix in future incidents, reducing customer-facing impact