Istoricul incidentelor Neo4j Aura

1. 3 septembrie 2026 la 16:43 UTCinvestigating

   În prezent investigăm această problemă.

2. 4 septembrie 2026 la 10:23 UTCidentified

   Problema a fost identificată, există în continuare cazuri disponibile și măsuri de soluționare a cazurilor cu impact care au fost revizuite în prezent.

3. 4 septembrie 2026 la 15:36 UTCresolved

   Toate cazurile sunt disponibile, au fost întreprinse etape manuale pentru a debloca numărul mic de cazuri rămase.

Traducere automată din actualizarea oficială a incidentului.

1. 20 august 2026 la 15:49 UTCinvestigating

   Echipa noastră a identificat o problemă cu colectarea indicatorilor pentru cazurile Aura. Acest lucru va afecta vizibilitatea metrică și transmiterea. În prezent investigăm problema.

2. 20 august 2026 la 16:48 UTCinvestigating

   Continuăm să investigăm problema cu Aura.

3. 20 august 2026 la 19:10 UTCresolved

   De la ultima actualizare, ancheta a trecut mai departe. Problema a fost identificată şi am monitorizat serviciul pe măsură ce s-a recuperat din degradare. Confirmăm că problema este rezolvată acum.

Traducere automată din actualizarea oficială a incidentului.

1. 5 august 2026 la 17:31 UTCinvestigating

   We have identified an issue currently that could result in unexpected query failures when using the trim() Cypher function. Investigations into the cause are in progress.

2. 5 august 2026 la 19:27 UTCidentified

   We have found the issue and are working on a fix. A small percentatge of queries using trim may still err. VDC customers with databases set to highest are not impacted at all unless they pause and start their instances.

3. 6 august 2026 la 00:58 UTCidentified

   We are testing the fix for the trim() Cypher function issue. We will update before we begin our deployment into the Aura environment.

4. 6 august 2026 la 07:13 UTCidentified

   We are actively validating the fix for the trim() Cypher function. Further updates will be provided before we begin deploying to Aura instances

5. 6 august 2026 la 11:17 UTCidentified

   We continue to validate the fix for the trim() Cypher function. Further updates will be provided before we begin deploying it to Aura instances.

6. 6 august 2026 la 14:54 UTCidentified

   The fix for the trim() Cypher function is undergoing testing and validation before deployment. Further updates will be provided before we begin deploying it to Aura instances.

7. 7 august 2026 la 01:15 UTCidentified

   Development has completed on the hot-fix for this issue, and we are finalizing the rollout plan for Aura.

8. 7 august 2026 la 01:16 UTCidentified

   We are actively working on addressing the issue. The fix for the trim() Cypher function is undergoing testing and validation currently before deployment. Further updates will be provided before we begin deploying it to Aura instances.

9. 7 august 2026 la 09:44 UTCidentified

   The fix to the trim() Cypher function has passed testing and validation and is now being deployed.

10. 7 august 2026 la 13:49 UTCmonitoring

    The fix to resolve the issue has now completed deployment to the Aura service and we are monitoring the situation.

11. 7 august 2026 la 15:34 UTCresolved

    We have monitored the fix and found the service to be stable. This incident is now considered resolved.

Traducere automată din actualizarea oficială a incidentului.

1. 23 iulie 2026 la 10:52 UTCinvestigating

   Investigăm o problemă în acest moment.

2. 23 iulie 2026 la 11:08 UTCinvestigating

   Lucrăm cu echipe de ingineri şi facem progrese cu investigaţiile în prezent.

3. 23 iulie 2026 la 11:24 UTCinvestigating

   Lucrăm cu echipe de ingineri şi continuăm să facem progrese cu investigaţiile în prezent.

4. 23 iulie 2026 la 11:38 UTCidentified

   Am identificat cauza problemei actuale și lucrăm activ la fix în prezent.

5. 23 iulie 2026 la 11:53 UTCidentified

   Implementăm prima parte a fixării și continuăm să lucrăm activ la găsirea soluției complete. Aşteptăm un ETA în ordine de 1 oră de acum.

6. 23 iulie 2026 la 12:11 UTCidentified

   Am identificat subgrupul de cazuri care au avut impact și continuă să se desfășoare fixarea în acest moment.

7. 23 iulie 2026 la 12:32 UTCidentified

   Am implementat o fixare a configuraţiei şi acum lucrăm la rezolvarea subsetului de cazuri afectate.

8. 23 iulie 2026 la 12:49 UTCidentified

   Odată cu configurarea fixată, continuăm să rezolvăm subgrupul de cazuri afectate.

9. 23 iulie 2026 la 14:07 UTCidentified

   Continuăm să rezolvăm subgrupul de cazuri afectate.

10. 23 iulie 2026 la 14:27 UTCidentified

    Continuăm să rezolvăm subgrupul de cazuri care sunt încă afectate.

11. 23 iulie 2026 la 14:44 UTCmonitoring

    Continuăm să rezolvăm subgrupul de cazuri care sunt încă afectate.

12. 23 iulie 2026 la 15:03 UTCmonitoring

    AuraDB Virtual Dedicate Cloud și AuraDB Business Critical ar trebui să fie acum toate fixe. Continuăm să rezolvăm subgrupul de cazuri care sunt încă afectate pentru AuraDB Professional și Free.

13. 23 iulie 2026 la 15:29 UTCmonitoring

    Continuăm să rezolvăm subgrupul de cazuri care sunt încă afectate pentru AuraDB Professional și Free.

14. 23 iulie 2026 la 15:57 UTCmonitoring

    Continuăm să rezolvăm subgrupul de cazuri care sunt încă afectate pentru AuraDB Professional și Free.

15. 23 iulie 2026 la 16:32 UTCmonitoring

    Continuăm să rezolvăm subgrupul de cazuri care sunt încă afectate pentru AuraDB Professional și Free

16. 23 iulie 2026 la 17:01 UTCmonitoring

    Continuăm să fixăm un subset de cazuri care sunt încă afectate pentru AuraDB Professional și Free

17. 23 iulie 2026 la 17:31 UTCmonitoring

    Continuăm să fixăm un subset mic de cazuri care sunt încă afectate de nivelurile profesionale și gratuite AuraDB.

18. 23 iulie 2026 la 18:07 UTCmonitoring

    Am abordat problema în toate cazurile profesionale AuraDB. Aura Free poate fi încă afectată. Vom continua să monitorizăm și să reparăm bazele de date rămase.

19. 23 iulie 2026 la 19:39 UTCmonitoring

    Continuăm să fixăm un subset mic de cazuri libere care sunt încă afectate.

20. 24 iulie 2026 la 06:00 UTCmonitoring

    Continuăm să monitorizăm îndeaproape situaţia pentru orice alte probleme.

21. 24 iulie 2026 la 08:30 UTCmonitoring

    Continuăm să monitorizăm orice alte probleme.

22. 24 iulie 2026 la 12:59 UTCmonitoring

    Toate cazurile identificate au fost rezolvate, continuând să monitorizeze. Contactaţi clienţii pentru orice alte probleme.

23. 24 iulie 2026 la 15:56 UTCresolved

    Toate remediile au fost implementate și problema este acum marcată ca rezolvată.

24. 29 iulie 2026 la 21:58 UTCpostmortem

    Ce s-a întâmplat? Joi, 23 iul, 2026 10:33 UTC a fost implementată o schimbare de configurație în Aura care a modificat involuntar modul în care alocările de memorie au fost calculate pentru cazurile de baze de date. Ca urmare, un subset de cazuri au primit memorie insuficientă, determinând unele cazuri de baze de date să devină indisponibile sau incapabile să completeze actualizările. Alocarea de memorie ajustată a dus la condiții out-of-memory, ceea ce a determinat cazuri de baze de date să repornească în mod repetat din cauza resurselor insuficiente de memorie sau să devină blocat actualizarea. Această problemă a afectat cazurile din rândul mai multor furnizori de cloud și al mai multor niveluri de produs. Odată ce problema a fost identificată, am revenit imediat schimbarea configurației, împiedicând orice situații suplimentare să primească configurația incorectă. O configuraţie corectată a fost trimisă la producţie până joi, 23 iul, 2026 11:56 UTC. Cu toate acestea, cazurile de baze de date care au primit deja configurația incorectă au necesitat acțiuni individuale de recuperare înainte ca acestea să poată reveni la funcționarea normală. Până joi, 23 iul, 2026 17:59 UTC, toate cazurile cunoscute de baze de date cu impact asupra clienților au fost recuperate. Monitorizarea a continuat până în ziua următoare, incidentul fiind complet rezolvat vineri, 24 iulie 2026 16:30 UTC. Cum a fost afectat serviciul Impactul principal al clientului a fost că mai multe cazuri din baza de date AuraDB au devenit indisponibile sau au intrat într-o stare degradată. Cazurile afectate nu au putut completa actualizările de rutină ale software-ului și, în unele cazuri, au fost reluate în mod repetat, deoarece memoria insuficientă fusese alocată. * ** Disponibilitatea serviciului:** Impactul clientului a variat în funcție de nivelul serviciilor. Cazuri profesionale AuraDB, care nu oferă disponibilitate ridicată, experimentat cel mai mare nivel de întrerupere a serviciului, cu un subset devenind indisponibil și incapabil să proceseze citiri sau scrie. Pentru cazurile afectate de AuraDB Business Critical and Virtual Dedicated Cloud \ (VDC\), impactul s-a limitat, în general, la o pierdere temporară a toleranței la defecțiuni în timp ce disponibilitatea serviciilor a fost menținută. Într-un număr mai mic de cazuri, cazurile critice de afaceri și cele VDC au devenit, de asemenea, indisponibile. * **Stuck actualizări**: Cazuri suplimentare au rămas disponibile, dar au fost blocate într-o stare de "actualizare," care a blocat operațiunile inițiate de client, cum ar fi redimensionări sau modificări de configurare. * **Cross-platform domeniu de aplicare**: Impactul a cuprins toți cei trei furnizori de cloud și mai multe regiuni sprijinite, afectând clienții la nivel mondial. Au fost ridicate cazuri de asistență a clienților și echipa noastră a triat și recuperat manual cazuri afectate în ordine prioritară. Majoritatea cazurilor de AuraDB au continuat să funcționeze normal. Impactul asupra clienților a fost atenuat pe deplin prin revenirea configurației și recuperarea manuală orientată a fiecărei situații afectate. Ce facem acum Am efectuat o analiză aprofundată a acestui incident și am identificat următoarele acțiuni: * **Prevenire** * ** Validarea implementării dovedită:** Ne consolidăm procesul de validare a eliberării pentru a identifica mai bine modificările de configurare. * **Decuplare Component**: Evaluăm îmbunătățirile aduse secvențierii implementării componentelor pentru a reduce riscul ca modificările nedorite să fie incluse în versiuni. * ** Strategia de lansare progresivă**: Revizuim procesul de lansare a componentelor afectate, pentru a le alinia la controalele de lansare utilizate pentru alte componente critice. * **Detecţie** * ** Mai bine alertarea**: Suntem îmbunătățirea monitorizării noastre pentru a detecta creșteri anormale ale ratelor de eșec \ (cum ar fi pierderea toleranței de defect sau disponibilitatea\) mai rapid și fiabil. * **Contenţionarea** * ** Desfășurarea configurației Safer:** Îmbunătățim modul în care sunt implementate schimbările de configurare a producției, astfel încât acestea să poată fi dezactivate sau laminate mai repede fără a necesita o versiune software mai largă. * **Recuperare manuală mai rapidă**: Ne îmbunătăţim instrumentele de recuperare pentru a reduce timpul necesar identificării şi recuperării manuale a cazurilor afectate. Recunoastem intreruperea acestui incident si ne cerem scuze pentru impactul asupra clientilor afectati. Am finalizat acțiunile corective imediate, iar îmbunătățirile pe termen lung descrise mai sus sunt deja în curs de desfășurare pentru a reduce probabilitatea și impactul unor incidente similare în viitor.

Traducere automată din actualizarea oficială a incidentului.

1. 10 iulie 2026 la 17:18 UTCinvestigating

   Investigăm în prezent o problemă care afectează Consola Aura, unde unii clienți ar putea fi în imposibilitatea de a vedea cazurile lor. Această problemă este cauzată de un eșec într-un serviciu terț de care depinde Aura. Cazurile afectate continuă să funcționeze normal, iar conectivitatea bazei de date nu este afectată. Echipa noastră investighează în mod activ problema.

2. 10 iulie 2026 la 17:23 UTCinvestigating

   Continuăm să investigăm această problemă.

3. 10 iulie 2026 la 17:51 UTCmonitoring

   Serviciul terţ de care depinde Aura a restabilit operaţiunile normale şi sistemele Neo4j Aura s-au recuperat. Echipa noastră monitorizează în mod activ problema pentru a confirma că Aura Console evoluează conform aşteptărilor.

4. 10 iulie 2026 la 19:23 UTCresolved

   Serviciile sunt confirmate a fi operaționale și nu se așteaptă alte întreruperi.

5. 27 iulie 2026 la 04:28 UTCpostmortem

   ## What happened Aura Console și alte componente Aura s-au confruntat cu întreruperi la 2026-07-10 la 16:14 UTC, ceea ce a dus la eșecuri și la prăbușiri. În consecință, un segment de clienți s-a confruntat cu probleme de vizibilitate în ceea ce privește cazurile lor. Acesta a fost cauzat de o pană de curent într-un serviciu extern al terților integrat cu Aura. În mod esențial, conectivitatea bazei de date a rămas necompromisă, iar cazurile afectate și-au continuat operațiunile normale. LansareÎntuneric serviciu a fost restaurat pentru a rezolva problema ## Cum serviciul a fost afectat Multiple componente Aura, inclusiv Aura Console, au suferit întreruperi. Utilizatorii au întâlnit erori HTTP 500 pe paginile și operațiunile legate de baze de date, deși organizațiile și proiectele ar putea fi încă accesate. Conexiunile directe la anumite cazuri de baze de date nu au fost afectate complet Avionul de control a devenit indisponibil, ceea ce a însemnat că utilizatorii nu au putut crea, șterge, redimensiona sau ajusta setările pentru situații prin intermediul API sau consola Aura. Cu toate acestea, cazurile existente au rămas operaționale. Problema a fost cauzată de o pană de curent la LaunchDarkly, iar serviciile noastre nu s-au ocupat cu graţie de această dependenţă în timpul startup-ului. Toate sistemele afectate au revenit la funcționarea normală până la 2026-07-10 la 17:07 UTC ## Ce facem acum Echipa de Inginerie Neo4j a diagnosticat rapid cauza rădăcină și a restaurat serviciul. În evaluarea acestui incident, am identificat domenii-cheie pentru accelerarea rezoluțiilor viitoare și atenuarea riscurilor de recurență: * Indicatori cheie analizați ai incidentelor, concentrându-se pe durata de alertă la răspuns pentru a identifica oportunitățile de accelerare a eficienței răspunsului * Desfășurat o retrospectivă cuprinzătoare evidențiind rezultate de succes, inclusiv analiza rapidă a cauzelor prin exploatarea transparentă, alinierea fără probleme prin intermediul instrumentului de gestionare a incidentelor, și degradarea rezilientă, grațioasă a mai multor componente care au păstrat intactă conectivitatea planului de date * Dezvoltarea în mod activ mai grațios Fallback implicits pentru steaguri caracteristică pentru a proteja operațiunile de bază în timpul descărcărilor vânzătorului * Consolidarea rezilienței arhitecturale prin integrarea practicilor avansate de planificare, inginerie haos, precum și testarea injecției de defecte la nivelul producției pentru a descoperi preventiv și a atenua potențialele căi de eșec * Limitările logice abordate în cacheul de pavilion caracteristică operatorului, subliniind necesitatea operatorilor de a stoca steaguri evaluate la nivel local pentru a menține continuitatea operațională în cazul în care dependențe externe nu.

Traducere automată din actualizarea oficială a incidentului.

1. 30 iunie 2026 la 14:45 UTCidentified

   Rularea VECTOR INDEX nu reușește cu eroare 51N31 eroare: configurarea sistemului sau excepția de funcționare - nu este susținută. Crearea unui indice vectorial cu setările furnizate nu este susținută în V2026 02. Versiunea necesară pentru operație este V2026 06. Vă rugăm să actualizați DBMS .. Aceasta afectează doar un nou indice, VECTOR INDEX existent nu este afectată. Orice indice vectorial creat înainte de 2026-06-30 la ora 09:00 continuă să funcționeze normal.

2. 30 iunie 2026 la 15:41 UTCidentified

   Începem acum să punem în aplicare un fix pentru a aborda această problemă și va oferi în curând o actualizare a progreselor înregistrate.

3. 30 iunie 2026 la 16:05 UTCmonitoring

   Un fix este de rulare și progresează bine. Vom face progrese.

4. 30 iunie 2026 la 17:45 UTCresolved

   Fixarea a fost pe deplin implementată în toate cazurile afectate. Acest incident este acum rezolvat.

5. 20 iulie 2026 la 08:40 UTCpostmortem

   ## What happened O problemă a fost identificată ca urmare a implementării versiunii 2026.06 la 2026-06-30 la ora 08:00 UTC, în cazul în care rulează VECTOR INDEX Acest eșec în generarea de indici a avut loc deoarece magazinul de bază și nucleul necesita actualizări suplimentare pentru a sprijini operațiunea Această problemă a afectat doar crearea de noi indici; indicii vectori existenţi nu sunt afectaţi. Orice indice vectoric creat înainte de ora 09:00 pe 2026-06-30 nu a fost afectat și a continuat să funcționeze normal. ## Cum serviciul a fost afectat Ca urmare a introducerii versiunii 2026.06, executarea declaraţiei CREATE VECTOR INDEX a eşuat, influenţând aplicaţiile care depind de adăugarea de noi indici vectori. Clienții afectați au primit eroarea: Crearea unui indice vectorial cu setările furnizate nu este suportată în V2026\ 02. Versiunea necesară pentru operare este V2026\ 06. Te rog upgrade DBMS . Indicele existent \ (creat înainte de acest incident\) și alte întrebări au rămas complet neafectate și complet funcționale. ## Ce facem acum Echipele Neo4j au identificat cauza rădăcină ca fiind o eroare în Planificatorul Cypher și au rezolvat problema cu o fixare de cod. Acest fix a fost implementat în toate cazurile Aura afectate, rezolvarea completă a erorii Pentru a preveni apariţiile viitoare, ne îmbunătăţim sistemele de monitorizare şi alertă pentru a detecta probleme similare mai devreme, în special în mediile de pregătire, înainte de apariţia rollout-urilor. Simultan, ne perfecționăm procesele de implementare pentru a minimiza impactul clienților și timpul de recuperare În plus, investigăm opțiuni de implementare a testelor automatizate de validare post-actualizare specifice operațiunilor critice, cum ar fi crearea de indici vectori

Traducere automată din actualizarea oficială a incidentului.

1. 23 iunie 2026 la 11:25 UTCidentified

   Aura consola se confruntă cu unele erori intermitente: "Sistemul nostru se confruntă cu probleme chiar acum. încearcă din nou mai târziu sau contactează suportul dacă problema persistă." Acest lucru vă poate cere să reîncărcați sau să așteptați mai mult pentru navigarea în consolă Operațiunile și Aura API rămân neafectate Lucrăm activ la o rezolvare

2. 23 iunie 2026 la 13:03 UTCidentified

   Continuăm să investigăm o rezolvare a problemei

3. 23 iunie 2026 la 13:39 UTCidentified

   Continuăm să lucrăm la o soluție pentru această problemă.

4. 23 iunie 2026 la 15:43 UTCmonitoring

   Derulăm o schimbare. Vom monitoriza și actualiza.

5. 23 iunie 2026 la 19:27 UTCmonitoring

   Continuarea monitorizării modificărilor implementate. Următoarea actualizare aşteptată la 6/24/2026 10am UTC.

6. 24 iunie 2026 la 09:14 UTCmonitoring

   Am verificat și confirmăm faptul că problema este acum pe deplin abordată.

7. 24 iunie 2026 la 09:14 UTCresolved

   Acest incident a fost rezolvat.

8. 10 iulie 2026 la 14:50 UTCpostmortem

   ## What happened La aproximativ 12:00 UTC pe 22 ianuarie 2026, utilizatorii au întâlnit bannere intermitente de eroare în consola Aura care afișează: "Avem o problemă. Încercați din nou.," care a apărut alături de 500 de erori de la criteriile finale ale consolei API. Aceste întreruperi au fost tranzitorii și cauzate de sincronizare internă API în timpul procesului de strângere de mână TLS, de obicei rezolva în aproximativ 10 secunde sau după o reîmprospătare pagină ## Cum serviciul a fost afectat Aura Console și Aura API au experimentat performanțe degradate, care s-au manifestat ca bannere intermitente de eroare în consola Aura UI. O anchetă a identificat cauza rădăcină ca fiind utilizarea ridicată a procesorului și trepidarea în consola API. Această problemă a fost determinată în primul rând de liste repetate de entități mari și cereri costisitoare de reconciliere Pentru a aborda această problemă, au fost implementate cu succes soluții specifice atât pentru consola Aura, cât și pentru Aura API. Acest lucru a fost urmat de ajustări ale configurației resurselor pentru a crește sediul operațional și a asigura stabilitatea ## Ce facem acum Au fost puse în aplicare următoarele măsuri reactive și proactive pentru a reduce probabilitatea unor incidente similare: * Dezvoltat un tablou de bord de monitorizare pentru a observa picăturile de cerere bazate pe datele interne API jurnal pentru a implementa monitorizarea automată și alertarea la probleme de captură înainte ca acestea să apară * Implementat o întârziere stagnată între cererile de reconciliere paginate pentru a atenua consumul ridicat de resurse și pentru a îmbunătăți stabilitatea API * Calcule de resurse pentru îmbunătăţirea performanţei * A introdus un nou filtru pentru întrebări bazate pe niveluri de service pentru a optimiza cheltuielile CPU pentru fiecare apeluri efectuate de conciliator * Deactivat cerere redundantă de procesare Middleware pentru a optimiza apeluri API

Traducere automată din actualizarea oficială a incidentului.

1. 26 mai 2026 la 18:23 UTCinvestigating

   Aura Console is currently not accessible. Our team is investigating the issue. Aura instances are running normally and are not impacted. They remain accessible via https://browser.neo4j.io/ and https://bloom.neo4j.io/ Console-related administration and configuration procedures may be unavailable. We will provide updates as soon as more information is available.

2. 26 mai 2026 la 19:19 UTCmonitoring

   The Aura Console issue has now been resolved. The root cause was a failure while fetching public certificates from Auth0. We are reaching out to the Auth0 team to gather more detailed information about the incident.

3. 26 mai 2026 la 23:06 UTCresolved

   This incident has been resolved.

4. 9 iunie 2026 la 16:50 UTCpostmortem

   **What Happened** During the incident window, users attempting to log in to the Aura Console were unable to do so. Auth0, the authentication provider for Aura Console, experienced an issue that prevented new authentication requests from completing. Existing sessions with valid cached tokens were largely unaffected. Aura database instances were running normally throughout and were not impacted, and access via the Aura API to database instances was also unaffected. **How the service was affected** Authentication requests from the Aura Console to Auth0 began failing, preventing new logins and session refreshes. Affected users received 503 errors when accessing the Aura Console. Once Auth0 recovered, access was restored. **What are we doing now** We've made two changes as a result of this incident: * Client identification: Authentication requests now include a clearer client identifier, reducing the chance of requests being incorrectly blocked in the future. * Observability: We've improved logging and alerting for authentication failures, including better visibility into errors from external services,so we can detect and escalate issues like this faster.

1. 6 martie 2026 la 10:18 UTCidentified

   We identified an issue with the availability of console.neo4j.io - we are investigating

2. 6 martie 2026 la 10:24 UTCmonitoring

   We have made a code change and we believe the console is available again.

3. 6 martie 2026 la 10:25 UTCresolved

   We have checked and confirm that the issue is now fully addressed.

4. 30 martie 2026 la 07:25 UTCpostmortem

   ## What Happened On March 6, at 10:04 AM UTC,  the Aura Console became inaccessible following a recent deployment. The deployment included changes related to user organizations and switching to an org memberships entity. This change caused the console to become inaccessible for a short period. ## How the service was affected A deployment to the Aura Console introduced an issue that caused an unexpected increase in backend requests related to access validation. This led to elevated CPU usage, which impacted the availability of the console and dependent services. We rolled back to a previous version to restore access. The rollback ensured the full restoration of access to the Aura Console, resolving the core issue within the incident window ## What are we doing now We are currently implementing a comprehensive strategy to bolster system resilience and prevent future recurrence. Our immediate actions include integrating stricter and more robust safeguards into the deployment pipeline. Crucially, we are significantly enhancing our validation processes to proactively detect and flag any potential performance impacts _before_ code is promoted to the production environment

1. 3 martie 2026 la 21:35 UTCidentified

   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.

2. 4 martie 2026 la 01:39 UTCidentified

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

3. 4 martie 2026 la 04:52 UTCidentified

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

4. 4 martie 2026 la 14:07 UTCmonitoring

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

5. 4 martie 2026 la 15:19 UTCresolved

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

6. 8 aprilie 2026 la 06:39 UTCpostmortem

   ## What Happened An issue was introduced in the Neo4j 2026.02 release where MERGE queries that referenced the same property on both the left and right sides of an `ON MATCH SET` or `ON CREATE SET` clause could potentially delete that property from the node or set it to an invalid value during query execution. This behaviour was observed specifically when the node being matched had at least one property uniqueness constraint. ## How the service was affected A change in the Neo4j 2026.02 release introduced a potential risk of writes failing or invalid data being returned for queries using MERGE together with `ON MATCH`. This issue affected instances across Aura tiers and required immediate investigation by Neo4j Engineering. The team identified the root cause and deployed a fix in version 2026.02.1. ## What are we doing now The following proactive measures have been implemented to reduce the likelihood of similar incidents: * We have strengthened test coverage for `ON CREATE` and `ON MATCH` clauses, particularly those involving more complex expressions. * We are investigating additional safeguards to improve our ability to control MergeInto/MergeUnique behaviour more flexibly, as well as potential rollback capabilities to support recovery in future incidents

1. 2 martie 2026 la 19:55 UTCidentified

   We are aware of issues in the Middle East regions via our cloud partner AWS, affecting AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain). The most up-to-date information from AWS is available at: https://health.aws.amazon.com/health/status We are actively working to limit the impact on the Aura service. However, customers should expect that new deployments in the affected regions may be impaired. Additionally, existing services deployed in these regions may experience reduced availability. Customers with services in these or nearby regions who are concerned about potential operational impact are encouraged to contact Neo4j Customer Support through the usual channels. Our team is available to advise and assist as needed.

2. 3 martie 2026 la 15:26 UTCidentified

   We continue to monitor the situation in the affected AWS Middle East regions. The most up-to-date information from AWS is available at: https://health.aws.amazon.com/health/status We will provide additional updates as soon as more information becomes available.

3. 6 martie 2026 la 14:29 UTCidentified

   We continue to monitor the situation in the affected AWS Middle East regions. The latest information from AWS is available at: https://health.aws.amazon.com/health/status We will provide additional updates as more information becomes available. Please review the AWS recommendation on the website above.

4. 6 martie 2026 la 16:06 UTCresolved

   While AWS continues working on this situation, we are closing this incident and invite our customers to monitor the AWS Status on our main Neo4j Status Page under AWS (Amazon Web Services). The latest information from AWS can be found at: https://health.aws.amazon.com/health/status

5. 29 martie 2026 la 15:16 UTCpostmortem

   ## What Happened On March 1, at 12:51 PM UTC, AWS services in the ME-CENTRAL-1 & ME-SOUTH-1 Region were impacted. Connectivity and power issues affected APIs and AWS core services essential to run Neo4j Aura prompting AWS to initiate an investigation ## How the service was affected Operations \(clone, backup, resuming/pausing, resizing\) that require additional resources like EC2 Instances, EBS Volumes, and other resources were impaired in the ME-CENTRAL-1 and ME-SOUTH-1 Region. Other AWS Services also experienced error rates and latencies for some workflows. Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts to infrastructure. A detailed summary of the AWS regional incident can be found here:[ https://health.aws.amazon.com/health/status](https://health.aws.amazon.com/health/status) ## What are we doing now We are actively working to limit the impact on the Neo4j Aura service. However, customers should expect that new deployments in the affected regions may be impaired. Additionally, existing services deployed in these regions may experience reduced availability. Customers with services in these or nearby regions who are concerned about potential operational impact are encouraged to contact Neo4j Customer Support through the usual channels Please visit AWS Status page for more info:[https://health.aws.amazon.com/health/status](https://health.aws.amazon.com/health/status)

1. 26 ianuarie 2026 la 19:26 UTCidentified

   Am identificat o problemă care poate afecta un set limitat de întrebări Cypher 25 pentru AuraDB Free, Professional și AuraDS. Acest lucru poate afecta: - Queries using the conditional interoction When in combination with a non-grouping agregation over nul Values caducing to a correct number of rands returned. - Queries using NEXT poate produce o variabilă neașteptată nu eroare definită în unele cazuri. Lucrăm activ la un fix și vom actualiza această pagină pe măsură ce devin disponibile mai multe informații.

2. 27 ianuarie 2026 la 01:37 UTCidentified

   Am identificat o soluţie pentru această problemă şi vom pleca în Aura. Odată ce actualizarea a fost implementată vom actualiza această pagină tatus.

3. 27 ianuarie 2026 la 09:50 UTCidentified

   Noi suntem de rulare fix și vă va actualiza atunci când acest lucru este finalizat.

4. 27 ianuarie 2026 la 11:10 UTCmonitoring

   Fixa a rulat la componentele afectate, suntem acum monitorizarea situaţiei în acest moment.

5. 27 ianuarie 2026 la 14:51 UTCmonitoring

   Continuăm să monitorizăm situaţia în acest moment.

6. 27 ianuarie 2026 la 15:58 UTCresolved

   Fixarea a fost pe deplin implementată în toate cazurile afectate. Acest incident este acum rezolvat.

7. 2 iulie 2026 la 04:22 UTCpostmortem

   Ce s-a întâmplat? Neo4j a început desfăşurarea versiunii 2026.01.1 către Aura la data de 07:49 AM UTC la 26 ianuarie 2026. După detectarea defecțiunilor de interogare în timpul testării interne, rollout-ul a fost oprit înainte de a ajunge la niveluri superioare Aura. Eșecurile au avut loc la întrebări condiționale \(de exemplu, CÂND ... ATUNCI ...\) după faza planificatorului să se comporte diferit în cazul agregării față de valorile nule. Am identificat cauza principală și am elaborat o rezoluție, care a fost integrată în versiunea 2026.01.2. La 27 ianuarie 2026, am început să trimitem 2026.012.2 în toate cazurile Aura, modernizând cu succes toate mediile afectate la versiunea corectată ## Cum serviciul a fost afectat Interogările care utilizează CÂND în 2026.01.1 în combinație cu agregarea valorilor nule primesc un număr incorect de rânduri returnate. Interogările folosind Next pot produce în unele cazuri o variabilă neașteptată care nu este definită eroare. Acest lucru a determinat interogarea rescrisă să se comporte diferit în cazul agregării față de valorile nule. Interogarea condiționată ar trebui să primească rândurile care conțin valori nule și să se agregare asupra valorilor fără a utiliza un grup. Clienții au primit un rezultat incorect în cazul în care au utilizat proiectul de interogare condiționată din Cypher 25 \ [a se vedea [https://neo4j.com/docs/aura/managing-stances/cypher-version/] [https://neo4j.com/docs/aura/managing-instances/cypher-versiune/)\], un impact limitat la un număr limitat de cazuri Aura. ## Ce facem acum Ne-am consolidat procedurile de testare pentru a asigura o acoperire cuprinzătoare în toate domeniile de produse. Printre acestea se numără dezvoltarea unor noi cazuri de testare menite să abordeze atât aspectele identificate, cât și scenariile viitoare potențiale. Mai mult decât atât, am integrat testul de interogare Cypher în cadrul Aura ca o componentă standard a suitei noastre de testare de regresie. Aceste controale sunt acum etape obligatorii în cadrul conductei noastre de integrare continuă și medii de pregătire înainte de orice lansare a producției.

Traducere automată din actualizarea oficială a incidentului.

1. 16 ianuarie 2026 la 14:25 UTCidentified

   Impact is that currently it is not possible to load data into GDS via native projection. Customers using Aura Graph Analytics are not impacted. We have identified a packaging issue with the latest release of Aura. Our engineering team is working on a fix.

2. 16 ianuarie 2026 la 15:13 UTCidentified

   Our teams have a fix and initiated the work to get it ready to roll-out. No current ETA available. We will keep you updated soon.

3. 16 ianuarie 2026 la 17:07 UTCmonitoring

   The fix is currently rolling out to production. We will update you upon completion

4. 16 ianuarie 2026 la 19:36 UTCresolved

   All instances should have the fix applied and if not it should be in the next 60 minutes

5. 23 aprilie 2026 la 13:27 UTCpostmortem

   ### **What happened** On January 15, 2026 at 22:12 UTC we began rolling out an update that included an incompatible version of a key component, affecting customers using the GDS plugin. This issue was reported on January 16 at 12:59 UTC, and a fix was deployed within hours, restoring functionality for the majority of affected users by 20:03 UTC.  The issue occurred because Neo4’s packaging automation process selected the wrong version of the GDS component. GDS 2.25 should have been selected but instead GDS 2.24 was included in the bundle, which caused a compatibility issue. Although a corrected package was created and labeled separately, the release pipeline selected the incorrect package for deployment.  This issue highlighted a gap in the release validation process, where incompatible component versions were not detected before rollout. ### **How customers were affected** Customers using the GDS plugin were unable to use any of the functionality the plugin provides during the incident window.  The system configuration has been updated to ensure compatibility with the intended component versions, restoring full functionality. ### **What we are doing now** The following mitigations have been implemented:  * Enhanced testing procedures to automatically verify compatibility between Neo4j and all bundled components before release. * Improved release processes to ensure that only explicitly validated and correctly labeled packages can be selected for deployment.

1. 26 noiembrie 2025 la 15:47 UTCidentified

   Neo4j opened a ticket with Azure and is awaiting updates on their resolution of the Azure Infrastructure issues. Impact on Neo4j Aura Services: Create, Resize (CPU and Storage), Pause, Resume.

2. 26 noiembrie 2025 la 20:33 UTCidentified

   Neo4j continues working with Microsoft via an Azure cloud ticket and is awaiting updates on their resolution of the Azure Infrastructure issues. Some resources have been made available, and impacted Neo4j Services have resumed operation. Customers have been notified. The Neo4j Aura Service is impacted when performing the following operations: Create, Resize (CPU and Storage), Pause, Resume. If Azure resources are unavailable when requesting these types of Neo4j operations, the operation will fail, and the Neo4j instance will become unavailable until Azure is able to provision additional resources.

3. 27 noiembrie 2025 la 14:33 UTCidentified

   The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, effecting the following operations: Create, Resize (CPU and Storage), Pause, Resume. If Azure resources are unavailable when requesting these types of Neo4j Aura operations, they will fail and the Neo4j Aura instance will become unavailable until Azure is able to provision additional resources.

4. 27 noiembrie 2025 la 17:07 UTCidentified

   The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, effecting the following operations: Create, Resize (CPU and Storage), Pause, Clone, Resume. As Azure resources become available when performing some Aura operations, the impacted instances may progressively recover and operations successfully complete. We continue to monitor progress, work with Microsoft Azure Infrastructure issues and will update.

5. 28 noiembrie 2025 la 00:09 UTCidentified

   We continue to work with our cloud infrastructure provider . Aura operations affected: Create, Resize (CPU and Storage), Pause, Clone, Resume.

6. 28 noiembrie 2025 la 10:55 UTCidentified

   We continue to work with our cloud infrastructure provider. Aura operations affected: Create, Resize (CPU and Storage), Pause, Clone, Resume.

7. 28 noiembrie 2025 la 16:23 UTCidentified

   We continue to work with Microsoft Azure. No expected improvements in addressing the issues around cloud resources in the affected regions before next week. Aura operations affected: Create, Resize (CPU and Storage), Pause, Clone, Resume. We will resume updates after this weekend or earlier if we have more information.

8. 1 decembrie 2025 la 09:54 UTCidentified

   The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, effecting the following operations: Create, Resize (CPU and Storage), Pause, Resume. If Azure resources are unavailable when requesting these types of Neo4j Aura operations, they will fail and the Neo4j Aura instance may become unavailable or degraded until Azure is able to provision additional resources.

9. 5 decembrie 2025 la 10:20 UTCidentified

   The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, affecting the following operations: Create, Resize (CPU and Storage), Pause, Resume. If Azure resources are unavailable when requesting these types of Neo4j Aura operations, they will fail and the Neo4j Aura instance may become unavailable or degraded until Azure is able to provision additional resources.

10. 5 decembrie 2025 la 16:59 UTCidentified

    The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region. We are working with our cloud partner and will resume updates once we have an ETA to share.

11. 11 decembrie 2025 la 10:24 UTCmonitoring

    Cloud resources have become available in USEAST2 and we will monitor for a few hours to ensure there is no further customer impact.

12. 11 decembrie 2025 la 15:39 UTCresolved

    Cloud resources have become available in USEAST2 and no further customer impact has been detected. This incident is resolved.

13. 4 februarie 2026 la 15:18 UTCpostmortem

    ### **What Happened** Starting at 13:26 UTC on November 24th Microsoft Azure region eastus experienced a stock out situation, which impacted operations for all tiers of Neo4j Aura in that specific region. Additional capacity was requested straight away, but not until 17:06 UTC on December 10th did enough additional resources become available to resume all normal operations. **How the service was affected** All tiers within the Neo4j Aura Service were impacted when performing the following operations during this incident: Create, Resize \(CPU and Storage\), Clone, Pause and Resume. If Microsoft Azure resources were unavailable when requesting these types of Neo4j operations, the operation would fail, and the Neo4j instance would become unavailable until Azure was able to provision additional resources.  ### **What are we doing now** To mitigate the scope of impact of future regional stock out issues, Neo4j is implementing the following measures: * Closely monitoring resource capacity to improve stockout predictions. * Regular calls with with our Cloud Service Provider to: * Learn about where regional resource capacity restrictions are forecast. * Plan for more resources in restricted regions. * Investigating other deployment models to allow us to keep Aura running in situations where 3 Availability Zones are not available.

1. 18 noiembrie 2025 la 15:56 UTCidentified

   We have identified an issue resulting in Pause, Resume and Delete operations to fail in both Console and Aura API across all tiers of Aura. We are actively working to resolve the issue and will report progress.

2. 18 noiembrie 2025 la 16:16 UTCmonitoring

   We have released a fix to this issue and are monitoring to ensure all operations are back to normal.

3. 18 noiembrie 2025 la 16:39 UTCresolved

   After monitoring the fix for some time, we can confirm that the issue is resolved and normal operations have resumed.

4. 14 ianuarie 2026 la 14:05 UTCpostmortem

   ### What happened 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. ### How customers were affected During the incident, some users experienced service disruptions when accessing the Console. Impacts included: * Intermittent connectivity issues * Inability to log in * Temporary unavailability of specific Console features 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. ### What we are doing now Neo4j takes service reliability seriously and is strengthening safeguards to prevent similar incidents. New mitigations being deployed include: * Enhanced monitoring to detect related issues earlier * Additional automated checks to block faulty configurations before deployment * Improvements to overall service resilience to better tolerate similar failures We apologize for the disruption and appreciate our customers’ patience as we continue to harden our systems.

1. 20 octombrie 2025 la 16:43 UTCidentified

   Many core operations for instances in AWS region us-east-1 are degraded as a result of AWS incident in that region: https://health.aws.amazon.com/health/status Core operations include create, pause, resume, clone, backup, among others. We continue to monitor the AWS incident and will provide updates accordingly.

2. 20 octombrie 2025 la 19:14 UTCidentified

   We are continuing to monitor the AWS incident, and can report some slow improvement of impacted Aura instances in the AWS us-east1 region, though the service remains degraded in this region at this time. We are continuing to monitor progress in the AWS incident: https://health.aws.amazon.com/health/status

3. 20 octombrie 2025 la 21:28 UTCresolved

   Instance operations in AWS us-east-1 region are back to normal following the resolution of the AWS incident. We will continue to monitor but all data indicates that the issue is fully resolved at this time.

4. 15 ianuarie 2026 la 17:48 UTCpostmortem

   ### **What Happened** Between 08:41 UTC on October 20th and 09:00 UTC on October 21st, Neo4j Aura experienced service disruptions affecting the us-east-1 \(N. Virginia\) region in AWS. The incident was triggered by a broad AWS regional outage impacting Identity and Access Management \(IAM\) and the EC2 control plane. This resulted in delayed backups, temporary loss of database fault tolerance for a subset of users, and internal delays in administrative actions due to toolchain failures. A detailed summary of the AWS regional incident can be found here: [https://aws.amazon.com/message/101925/](https://aws.amazon.com/message/101925/) ### **How the service was affected** The primary cause was several AWS regional service disruptions in us-east-1. We will cover how each of these affected Neo4j Aura and its users. Neo4j Aura is designed to isolate regional failures. This is achieved through deploying customer instances in Orchestras that have instances in three availability zones and no cross region dependencies. AWS IAM and Identity Center became unresponsive, preventing Neo4j Aura’s automated systems from authenticating with AWS resources in us-east-1. This affected Neo4j Aura backups to be written to AWS S3 buckets. Customers were also not able to resume paused instances during this period as the resume process was not able to authenticate with AWS S3 buckets to retrieve the paused data set. Neo4j Aura’s inability to authenticate with Route53 to create new DNS entries affected Neo4j Aura DB creation, as new databases were created. AWS Network Load Balancer health check system failures and AWS EC2 “request limit exceeded” or “insufficient capacity” errors in us-east-1 were false negatives with the NLB heath checks which resulted in some Neo4j Aura DB clusters in us-east-1 losing fault tolerance \(1 out of 3 cluster members unavailable\). When this happened instances were removed by kubernetes and we were not able to provision new ones due to the EC2 failures noted earlier, leaving the clusters without fault tolerance for a prolonged period of time. All of these clusters still had full availability of the other two cluster members. ### **What are we doing now** Largely Neo4j Aura responded as designed to these events, isolating failures to us-east-1, with no to minimal cross system failure propagation. The cross cloud impact of creating DNS records for new instances was the main outlier.  To mitigate the scope of impact of future regional outages, Neo4j is implementing the following measures: * Full Neo4j Aura reviews to ensure Neo4j Aura design is implemented as intended across all sub-systems to surface any cross region dependencies.  * Remove identified cross-region dependencies.

1. 20 octombrie 2025 la 09:15 UTCidentified

   An active issue on AWS us-east-1 is affecting Neo4j Aura operations in the regions where we have some dependency on an impacted AWS service. See more details https://health.aws.amazon.com/health/status Other regions not currently impacted.

2. 20 octombrie 2025 la 09:39 UTCidentified

   Operations such as Create, Pause, Resume, Clone are affected globally due to a dependency. Backups in the affected region of AWS us-est-1 will be impacted The affected AWS service is now starting to recover and we are monitoring the situation

3. 20 octombrie 2025 la 09:58 UTCmonitoring

   We see clear signs of recovery and our impacted service are progressively getting back to normal. We will monitor and update when we can confirm full recovery and normal operations.

4. 20 octombrie 2025 la 10:32 UTCmonitoring

   We are continuing to see good recovery across the service. We will update when this is completed.

5. 20 octombrie 2025 la 11:13 UTCresolved

   The underlying AWS incident has bene resolved and our services have now resumed and fully recovered

6. 15 ianuarie 2026 la 17:34 UTCpostmortem

   ### **What Happened** Between 08:41 UTC on October 20th and 09:00 UTC on October 21st, Neo4j Aura experienced service disruptions affecting the us-east-1 \(N. Virginia\) region in AWS. The incident was triggered by a broad AWS regional outage impacting Identity and Access Management \(IAM\) and the EC2 control plane. This resulted in delayed backups, temporary loss of database fault tolerance for a subset of users, and internal delays in administrative actions due to toolchain failures. A detailed summary of the AWS regional incident can be found here: [https://aws.amazon.com/message/101925/](https://aws.amazon.com/message/101925/) ### **How the service was affected** The primary cause was several AWS regional service disruptions in us-east-1. We will cover how each of these affected Neo4j Aura and its users. Neo4j Aura is designed to isolate regional failures. This is achieved through deploying customer instances in Orchestras that have instances in three availability zones and no cross region dependencies. AWS IAM and Identity Center became unresponsive, preventing Neo4j Aura’s automated systems from authenticating with AWS resources in us-east-1. This affected Neo4j Aura backups to be written to AWS S3 buckets. Customers were also not able to resume paused instances during this period as the resume process was not able to authenticate with AWS S3 buckets to retrieve the paused data set. Neo4j Aura’s inability to authenticate with Route53 to create new DNS entries affected Neo4j Aura DB creation, as new databases were created. AWS Network Load Balancer health check system failures and AWS EC2 “request limit exceeded” or “insufficient capacity” errors in us-east-1 were false negatives with the NLB heath checks which resulted in some Neo4j Aura DB clusters in us-east-1 losing fault tolerance \(1 out of 3 cluster members unavailable\). When this happened instances were removed by kubernetes and we were not able to provision new ones due to the EC2 failures noted earlier, leaving the clusters without fault tolerance for a prolonged period of time. All of these clusters still had full availability of the other two cluster members. ### **What are we doing now** Largely Neo4j Aura responded as designed to these events, isolating failures to us-east-1, with no to minimal cross system failure propagation. The cross cloud impact of creating DNS records for new instances was the main outlier.  To mitigate the scope of impact of future regional outages, Neo4j is implementing the following measures: * Full Neo4j Aura reviews to ensure Neo4j Aura design is implemented as intended across all sub-systems to surface any cross region dependencies.  * Remove identified cross-region dependencies.

1. 25 august 2025 la 13:34 UTCinvestigating

   We are currently investigating this issue.

2. 25 august 2025 la 13:36 UTCinvestigating

   We are aware of an issue that could result in a degradation in write performance for all Aura instance. We have identified the cause and are preparing a fix.

3. 25 august 2025 la 13:47 UTCinvestigating

   We are continuing to investigate this issue.

4. 25 august 2025 la 15:34 UTCmonitoring

   The issue impact has been refined and currently could impact AuraDB Virtual Dedicated Cloud and Business Critical instances only. We have identified the cause and the faulty component has been reverted for the majority of instances. We will continue to monitor the situation, while the full fix is prepared.

5. 25 august 2025 la 21:44 UTCmonitoring

   We continue to work towards the issue resolution.

6. 26 august 2025 la 04:06 UTCmonitoring

   We are continuing to investigate this issue.

7. 26 august 2025 la 10:53 UTCmonitoring

   We are continuing to monitor the situation whilst a full fix for the solution is prepared.

8. 26 august 2025 la 14:48 UTCmonitoring

   We are continuing to monitor the situation. The full fix for the solution is currently undergoing final testing and will start deployment once testing is completed.

9. 26 august 2025 la 23:12 UTCmonitoring

   The full fix for the solution is starting to be deployed across the estate and are continuing to monitor the situation.

10. 27 august 2025 la 06:36 UTCmonitoring

    We are continuing to monitor for any further issues.

11. 27 august 2025 la 11:16 UTCmonitoring

    The full fix for the solution is continuing to be deployed across the estate and are continuing to monitor the situation.

12. 27 august 2025 la 16:46 UTCresolved

    The full fix for the solution has now been deployed across the estate and this issue is now resolved.

13. 6 octombrie 2025 la 13:32 UTCpostmortem

    ### **What happened** Between August 22 and August 28, 2025, a performance issue affected some of our database services following a recent update. Our team quickly responded and discovered that the problem was due to a bug in the latest update, which caused certain memory settings to be incorrectly configured. We promptly applied the previous version of those settings to stabilize the affected databases. By August 28, all databases were successfully transferred to a new, stable version, and the incident was fully resolved. The issue was caused by a misconfiguration in the system's data processing module. Specifically, an incorrect parameter setting in the data pipeline led to a bottleneck, which slowed down the processing speed. This misconfiguration affected the way data was being queued and processed, resulting in delays. Our technical team has identified the root cause and implemented a fix to ensure that the data pipeline operates efficiently, preventing future occurrences of this issue. ### **How the service was affected** Some customers reported a performance change on their instance.  ### **What we are doing now** Neo4j remains committed to providing reliable service and is implementing additional safeguards to prevent similar incidents in the future. New mitigations being deployed: * Enhancing our monitoring systems to detect similar issues faster * Implementing additional automated checks to prevent service disruptions * Improving our service resilience to handle similar scenarios * Introducing dynamic configuration management to ensure seamless updates * Enabling multiple configuration defaults to better manage database priorities * Improving notification systems for faster response to potential issues * Enhancing our tools to streamline database management and transfers

1. 22 august 2025 la 11:02 UTCinvestigating

   Engineers are investigating an issue whereby instance actions are not working. You may be unable to import data, pause, resume, create, delete or run manual backups for your instances. Regular Neo4j scheduled backups are continuing to run as normal. You may be unable to see your instances in the Aura Console. CMI is also experiencing an outage, you may be unable to ingest metrics from your Aura instances.

2. 22 august 2025 la 11:42 UTCmonitoring

   A fix has been identified and implemented. Instances should be showing on the console and instance operations should now be available. You should now also be able to ingest metrics using CMI. We are continuing to monitor the status of these services.

3. 22 august 2025 la 13:31 UTCresolved

   This incident has been resolved.

4. 12 septembrie 2025 la 15:45 UTCpostmortem

   ### What happened On August 22, 2025, from 10:10 to 11:27 UTC, users experienced an issue with the Aura Console where instance operations were unavailable. This was due to a timing issue with refreshing security keys that affected the visibility and operations of instances in the Aura Console and also caused an outage in the Customer Metrics Integration \(CMI\) and Aura API. The issue was identified within 5 minutes and efforts to resolve it began promptly. The problem was traced back to a recent update and issues with authentication were resolved by refreshing the system cache, with the service fully restored by 11:27 UTC.  The issue arose because of a timing mismatch between the creation of new security keys and their recognition by our system. When new keys were generated, they were quickly used by the Console API. However, another part of our system, the database manager, was still using an older set of keys to verify requests. This mismatch caused requests to fail because the database manager could not recognize the new keys. No unauthorized operations were allowed and this did not affect the security of the service in any way. After approximately an hour, the system automatically updated its keys, and everything started working correctly again. ### How customers were affected Aura Console features were impacted, including the visibility of instances and therefore ability to connect to instances through the console. Driver connections to instances were not impacted. The issue also impacted the use of parts of the service including Customer Metrics Integration \(CMI\) and the Aura API. ### What we are doing now Neo4j remains committed to providing reliable service and is implementing additional safeguards to prevent similar incidents in the future. We are taking steps to prevent similar issues in the future by improving our processes and monitoring systems. Changes we are making: * Enhancing our caching mechanisms to ensure seamless updates and prevent similar issues in the future. * Designing a robust process for updating service accounts and keys to guarantee uninterrupted service reliability.

1. 19 august 2025 la 09:19 UTCinvestigating

   We are currently investigating an issue with backups. We will update shortly as we get more details

2. 19 august 2025 la 10:05 UTCinvestigating

   We are continuing to investigate the issue with backups. New backups after 0:00 last night are failing to complete. Existing backups are unaffected and remain available.

3. 19 august 2025 la 10:34 UTCinvestigating

   We are continuing to investigate this issue.

4. 19 august 2025 la 10:51 UTCinvestigating

   We continue to investigate and have identified the issue more clearly. Beyond backups, other operations are also affected: pause and clone. Operations may fail or take a long time to complete.

5. 19 august 2025 la 11:30 UTCmonitoring

   The fix has been deployed and we will continue to monitor this incident.

6. 19 august 2025 la 12:04 UTCresolved

   This incident has been resolved.

7. 12 septembrie 2025 la 19:41 UTCpostmortem

   ### What happened On August 18, 2025, at 19:18 UTC, the release of a faulty component in Neo4j Aura impacted the ability to perform backups of customer instances. The problem was identified when a critical component was updated without aligning with another dependent component, leading to failed backup attempts. This resulted in Neo4j not being able to take backups of customer instances for a period of approximately 17 hours. Our team quickly identified the root cause and began mitigation efforts early on August 19, 2025. By 11:54 UTC, the issue was fully resolved, and normal backup operations resumed. We apologize for any inconvenience this may have caused and are taking steps to prevent similar issues in the future. The issue arose because the deployment of the neo4j-backup system was not properly synchronized with the deployment of the neo4j-operator. This misalignment led to critical changes being introduced that impacted the ability to create new backups effectively. Essentially, the two components were not updated in harmony, which caused disruptions in the backup process. ### How customers were affected Customers were unable to  get successful backups of their instances for 17 hours. We promptly addressed the issue by reverting the recent backup changes that caused disruptions and ensured the stability of our service by cleaning up old, failing backups. ### What we are doing now Neo4j remains committed to providing reliable service and is implementing additional safeguards to prevent similar incidents in the future. New mitigations being deployed: * Enhancing our monitoring systems to detect similar issues faster * Implementing additional automated checks to prevent service disruptions * Improving our service resilience to handle similar scenarios