Istoricul incidentelor Exalate

1. 27 august 2026 la 04:36 UTCinvestigating

   Atlassian se confruntă cu o problemă cu Jira și alte sisteme - detalii aici: https://status.atlassian.com/ Acest lucru poate afecta conexiunile Exalate dacă vă conectați la un caz Jira.

2. 27 august 2026 la 04:44 UTCidentified

   Problema a fost identificată și se pune în aplicare o soluție.

3. 27 august 2026 la 05:09 UTCmonitoring

   Atlassian au pus un fix în loc pentru a rezolva problema. Sincronizarea dvs. ar trebui să fie deja din nou la normal, dar vă rugăm să ajungeți pentru a sprijini în cazul oricăror probleme.

4. 27 august 2026 la 05:27 UTCresolved

   Toate sistemele Atlassiene au revenit la normal, iar sincronizarea funcţionează conform aşteptărilor. În caz de probleme cu sincronizarea, vă rugăm să creați un bilet de sprijin și vom fi bucuroși să vă ajutăm.

5. 8 septembrie 2026 la 05:41 UTCpostmortem

   N/A

Traducere automată din actualizarea oficială a incidentului.

1. 24 iulie 2026 la 06:12 UTCidentified

   În urma unei modificări neadvertite a numelui de aplicație care determină ca utilizatorul proxy să fie afișat cu numele complet al aplicației în loc de "Exalat." Acest lucru este deja notificat Atlassian și așteptăm acțiunea necesară pentru a reveni schimbarea. Impact: Actualizările făcute de Exalate vor afișa "Exalate Classic Conector for Jira (Two-way Sync) " ca utilizator care face schimbarea.

2. 24 iulie 2026 la 09:15 UTCidentified

   Continuăm să investigăm cea mai bună abordare pentru a rezolva această problemă cu ajutorul sprijinului atlassian.

3. 24 iulie 2026 la 12:39 UTCidentified

   Lucrăm activ cu sprijinul Atlassian pentru a determina cea mai bună rezoluție pentru această problemă cât mai curând posibil.

4. 24 iulie 2026 la 15:47 UTCidentified

   Lucrăm activ cu sprijinul Atlassian pentru a determina cea mai bună rezoluție pentru această problemă cât mai curând posibil. Vom furniza următoarea actualizare în 6 ore sau de îndată ce vom avea orice informații relevante.

5. 24 iulie 2026 la 16:33 UTCresolved

   Numele de utilizator proxy a fost returnat înapoi la Exalate. Considerăm incidentul ca fiind rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 16 iulie 2026 la 11:28 UTCinvestigating

   Unele noduri Jira Cloud se confruntă cu instabilitate în ultimele 30 de minute. Problema este limitată și afectează doar unii clienți. Vom furniza o actualizare în curând.

2. 16 iulie 2026 la 12:03 UTCidentified

   Vom acţiona în vederea îmbunătăţirii stabilităţii. Impactul asupra nodului va fi limitat la o repornire cu nodul fiind indisponibil pentru câteva minute. Neplăcerile sunt regretate.

3. 16 iulie 2026 la 13:38 UTCidentified

   Repornirea nodurilor este în desfăşurare. Veți experimenta o scurtă repornire pe nodurile JCloud. Vă vom ţine la curent cu progresul nostru.

4. 16 iulie 2026 la 15:15 UTCidentified

   Repornirea este încă în curs și merge fără probleme. Vă vom actualiza imediat ce va fi gata.

5. 16 iulie 2026 la 15:57 UTCmonitoring

   Toate nodurile au revenit la normal. Continuăm să monitorizăm îndeaproape situaţia.

6. 16 iulie 2026 la 17:18 UTCresolved

   După o monitorizare atentă, problema este considerată ca fiind pe deplin rezolvată. Vom posta un RCA aici în timp util.

Traducere automată din actualizarea oficială a incidentului.

1. 13 iulie 2026 la 22:15 UTCinvestigating

   Am primit mai multe rapoarte de sincronizare în buclă după actualizarea noii aplicații Jira Cloud Forge. Investigația noastră inițială ne face să credem că acest lucru se întâmplă din cauza schimbării în contul utilizatorului Proxy. Lucrăm în mod activ la determinarea cauzei profunde și aplicarea unui fix.

2. 13 iulie 2026 la 23:48 UTCinvestigating

   Continuăm să investigăm această problemă cu inginerii noştri pentru a determina cauza principală.

3. 14 iulie 2026 la 04:58 UTCidentified

   Cauza principală a fost identificată şi lucrăm la o soluţie. Vă rugăm să așteptați o altă actualizare într-o oră.

4. 14 iulie 2026 la 07:05 UTCidentified

   Fixarea este în prezent validată pentru a găsi cea mai bună abordare înainte. Vom furniza o altă actualizare într-o oră.

5. 14 iulie 2026 la 08:11 UTCidentified

   Din păcate, testarea fix a dezvăluit o problemă neașteptată și suntem acum fin de ajustare fix în scopul de a asigura că include toate cazurile posibile de utilizare. Vom avea o actualizare pentru tine într-o oră.

6. 14 iulie 2026 la 09:09 UTCidentified

   Noul fix a fost creat și testele inițiale sunt promițătoare. Suntem adânc în QA cu noul fix și va oferi o actualizare într-o oră despre rezultate. Neplăcerile sunt regretate.

7. 14 iulie 2026 la 10:11 UTCidentified

   Încă mai testăm fix-ul şi rezultatele sunt încă bune. Suntem aproape de finalizarea acestuia. Următoarea actualizare va fi într-o oră.

8. 14 iulie 2026 la 11:39 UTCidentified

   Fix este gata și lucrăm la abordarea de implementare cu impact minim pentru clienți. Acesta va fi rulat sistematic tuturor clienților. Vom furniza o actualizare în următoarea oră despre desfăşurare.

9. 14 iulie 2026 la 12:51 UTCidentified

   Am implementat fix la câțiva clienți selectați și rezultatele validate în continuare. Lansarea în masă este planificată chiar acum. Vă vom actualiza în următoarea oră despre progres.

10. 14 iulie 2026 la 14:24 UTCidentified

    Suntem încă pe curs pentru implementarea plasturelui și eliberarea trece prin validarea QA suplimentară acum (necesară pentru o desfășurare completă a producției). Ne aşteptăm la următoarea actualizare într-o oră.

11. 14 iulie 2026 la 16:11 UTCidentified

    QA şi testarea durează puţin mai mult decât ne aşteptam, dar ne aşteptăm să începem desfăşurarea în următoarea oră. Vă vom actualiza înainte de a începe acest lucru.

12. 14 iulie 2026 la 17:41 UTCmonitoring

    Implementarea hotfixului: Exalate Classic 5.35.4 - Jira Cloud, în curs de desfășurare (https://comunity.exalate.com/t/jira-cloud-version-5-35-4/8215). Desfășurarea este monitorizată îndeaproape pentru orice anomalii. Te vom actualiza într-o oră.

13. 14 iulie 2026 la 18:55 UTCmonitoring

    Desfășurarea continuă neîntrerupt. Vă vom actualiza în timp util de îndată ce este complet.

14. 14 iulie 2026 la 22:14 UTCresolved

    Punerea în aplicare a fost finalizată cu succes, iar problema raportată rămâne pe deplin rezolvată. Un RCA detaliat va fi publicat în timp util.

15. 28 iulie 2026 la 20:00 UTCpostmortem

    **Impact:** Unele Exalate Clasice pentru conexiunile Jira Cloud au experimentat sincronizări repetate, duplicate în urma unei migrații a infrastructurii către platforma Forge a Atlassian. Pe conexiunile afectate clienții au văzut: * ** Activitatea Duplicată** * ** Redeschise / probleme înviat** * **Distorted dashboards and reports** condus de volumul de modificări duplicate. * **Automatizaţii şi validări ale fluxului de lucru** * **Stuck or failed sincrons**, and in some case a conecte going down, retries retries manual or recuperare. * Crescut ** efort manual** pentru echipe pentru a descifra sincronizarea și corect problemele afectate. Nu toţi clienţii au fost afectaţi de impactul depinzând de configuraţia conexiunii. Cele mai expuse au fost conexiuni locale și probleme care au fost create anterior sau actualizate sub identitatea originală "Exalată" și au fost apoi atinse sub cea redenumită. **Summary:** Ca parte a mutării Exalate Classic pentru Jira Cloud la platforma Forge Atlassian, numele prezentat pentru utilizatorul de integrare Exalate în Jira s-a schimbat \[de la "Exalate" la o variantă mai lungă\). Exalate a folosit acest nume pentru a-și recunoaște propriile actualizări și pentru a evita re-sincronizarea acestora. Odată ce numele s-a schimbat, aplicația nu și-a mai recunoscut propriile scrieri pe conexiunile afectate și le-a reprocesat ca și cum ar fi noi modificări externe Aceeași schimbare de identitate a rupt și automatizările clienților și validările care au făcut referire la utilizatorul "Exalat" după nume. **Rezolution:** A patch \ (5.35.4\) that recognoscește propriile actualizări ale Exalate de către un identificator de utilizator stabil, mai degrabă decât numele de afișare a fost validat pe mediile de clienți afectate și a fost implementat în întreaga flotă Jira Cloud. Sincronizarea a revenit la normal odată ce implementarea a fost finalizată. Atlassian a restaurat și a confirmat numele utilizatorului de integrare ca "Exalate," și este acum stabil În cazul în care buclele au creat elemente duplicate sau redeschise, lucrăm cu clienții afectați pentru a identifica și corecta problemele afectate. ** Măsuri preventive:** Prevenirea buclei nu mai depinde de un nume de afișare care poate fi schimbat; adăugăm o evaluare a impactului și o etapă de notificare în jurul modificărilor bazate pe platformă și actualizări ale aplicațiilor, precum și detectarea automată a buclelor de sincronizare și saturarea bazei de date, astfel încât recuperarea nu depinde de rapoartele clienților. Ne cerem scuze pentru întrerupere şi rămânem devotaţi fiabilităţii platformei Exalate.

Traducere automată din actualizarea oficială a incidentului.

1. 23 iunie 2026 la 09:10 UTCinvestigating

   În prezent investigăm o problemă atunci când încercăm să încărcați conexiunea de la Exalate. pagina aplicației primește o eroare. Conexiunea și sincronizarea nu sunt afectate de pană, ele sunt încă de lucru, dar în acest moment nu este posibil pentru a vedea sau modifica conexiunea de la exalate. pagina aplicației. Vom furniza o actualizare în 2 ore.

2. 23 iunie 2026 la 09:26 UTCmonitoring

   Problema a fost rezolvată. Exalate Dashboard nu este din nou on-line și stabil. Vom continua monitorizarea sistemului.

3. 23 iunie 2026 la 12:47 UTCresolved

   Acest incident a fost rezolvat.

4. 7 iulie 2026 la 08:49 UTCpostmortem

   **Duraţie:** 11:10 CEST - 11:26 CEST \(aproximativ 16 minute\). Stabilitate deplină confirmată la 14:47 CEST. **Impact:** Paginile Exalate.appe și tabloul de bord au fost inaccesibile în timpul acestei ferestre. Sincronizarea problemelor nu a fost afectată - integrarea a continuat să se desfăşoare în mod normal. Nu s-au pierdut date. **Summary:** Pe 23 iunie 2026, interfața Exalate.app a devenit inaccesibilă după ce o componentă de autentificare internă nu s-a conectat la baza sa de date. Eșecul a fost cauzat de o necorelare credibilă introdusă în timpul desfășurării producției. **Timeline:** * 11:10 CEST - Problemă detectată, anchetă inițiată * 11:26 CEST - Fix desfăşurat, service restaurat * 14:47 CEST - Stabilitate deplină confirmată **Root Cause:** În timpul unei campanii de producție pe 19 iunie, o bază de date a fost configurată independent în două sisteme. A fost introdusă o neconcordanță subtilă în timpul unei actualizări ulterioare a configurației. Nepotrivirea a rămas latentă deoarece cererea a menținut conexiunile existente în baza de date. Un eveniment de întreținere de rutină GKE pe 23 iunie a reciclat cererea, forțând noi conexiuni care au expus neconcordanța. **Rezoluție:** Baza de date a fost aliniată și aplicația a fost reluată. Serviciul a revenit la funcționarea completă fără pierderi de date. ** Măsuri preventive:** * Verificarile de autentificare post-angajare au fost adaugate in registrul de implementare * Alertarea pentru eşecurile de conectivitate ale bazei de date a aplicaţiilor a fost implementată * Procesul de configurare credibilă este consolidat pentru a elimina riscul de neconcordanță dual-sistem Ne cerem scuze pentru întrerupere. Rămânem devotaţi fiabilităţii platformei Exalate.

Traducere automată din actualizarea oficială a incidentului.

1. 4 mai 2026 la 13:24 UTCinvestigating

   We have reports of some Exlate cloud nodes being unavailable. Our team is currently investigating the issue.

2. 4 mai 2026 la 13:42 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 mai 2026 la 14:50 UTCidentified

   Our cloud team has identified the root cause and is actively engaged in rectifying it.

4. 4 mai 2026 la 15:53 UTCidentified

   affected nodes are recovering while our cloud team continues to work on the issue.

5. 4 mai 2026 la 18:50 UTCmonitoring

   All nodes are operational, our cloud team continues to review the affected cluster and work on its maintenance.

6. 4 mai 2026 la 21:28 UTCresolved

   The system has been under close observation and it has been stable. We will provide a post-mortem to the incident in due course.

1. 15 aprilie 2026 la 09:03 UTCinvestigating

   În prezent investigăm o problemă în care pagina spaţiilor de lucru nu se încarcă. Sincronizarea nu este afectată, doar UI de New Exalate nu este de încărcare.

2. 15 aprilie 2026 la 09:04 UTCidentified

   Am identificat cauza principală a problemei și lucrăm în prezent la o soluție.

3. 15 aprilie 2026 la 10:16 UTCmonitoring

   Problemele tehnice au fost rezolvate pe deplin, iar aplicaţia funcţionează acum. Monitorizăm îndeaproape situaţia.

4. 15 aprilie 2026 la 12:16 UTCresolved

   Aplicația a funcționat fără probleme și nu vedem anomalii. O autopsie va fi furnizată în timp util.

5. 7 iulie 2026 la 12:41 UTCpostmortem

   **Incident:** Exalate.app Nu se încarcă spații de lucru - 15 aprilie 2026 **Duraţie:** 11:03 CEST **Impact:** Exalate.app UI a fost inaccesibil în timpul acestei ferestre. Sincronizarea problemelor nu a fost afectată. Nu s-au pierdut date. ** Sumar:** Pe 15 aprilie 2026, interfața Exalate.app a devenit inaccesibilă în urma unei actualizări credibile planificate a infrastructurii. O dependență secundară de configurare nu a fost actualizată ca parte a modificării, prevenind conectarea aplicației la baza sa de date. **Timeline:** * 11:03 CEST - Problema detectată, ancheta iniţiată * 11:04 CEST - Cauza root identificat * 12:16 CEST - Fix desfăşurat, serviciu restaurat **Root Cause:** O dependență de configurare omisă în timpul unei actualizări credibile a lăsat aplicația incapabilă să se autentifice în baza sa de date. Acest lucru a fost legat de incidentul din 6 aprilie; dependența suplimentară a fost acum identificată și încorporată în procedura de rotație. **Rezoluție:** Configuraţia afectată a fost regenerată şi aplicaţia a fost reluată. Serviciul a revenit la funcționarea completă fără pierderi de date. ** Măsuri preventive:** * Toate dependențele credibile au fost cartografiate complet și procedura de rotație actualizat pentru a le acoperi ca o singură operațiune atomică Ne cerem scuze pentru întrerupere. Rămânem devotaţi fiabilităţii platformei Exalate.

Traducere automată din actualizarea oficială a incidentului.

1. 6 aprilie 2026 la 11:07 UTCinvestigating

   Investigăm în prezent o problemă atunci când spaţiile de lucru nu încarcă informaţiile. Sincronizarea nu este afectată, dar UI de la New Exalate nu se încarcă.

2. 6 aprilie 2026 la 11:28 UTCmonitoring

   Am identificat și a fost implementată o soluție. Exalat.app este în prezent operaţională şi funcţionează conform aşteptărilor, vom continua monitorizarea situaţiei şi vom oferi în curând o actualizare.

3. 6 aprilie 2026 la 15:31 UTCresolved

   Acest incident a fost rezolvat.

4. 7 iulie 2026 la 12:30 UTCpostmortem

   **Incident:** Exalate.app Nu se încarcă spații de lucru - 6 aprilie 2026 **Duraţie:** 13:07 CEST - 13:28 CEST \(aproximativ 21 minute\). **Impact:** Exalate.app UI a fost inaccesibil în timpul acestei ferestre. Sincronizarea problemelor nu a fost afectată - integrarea a continuat să se desfăşoare în mod normal. Nu s-au pierdut date. **Summary:** La 6 aprilie 2026, interfața Exalate.app a devenit inaccesibilă după ce o acreditare de infrastructură a fost rotită ca parte a unui program planificat de îmbunătățire a securității. Componenta responsabilă pentru conectivitatea bazei de date înregistrează acreditări la pornire și nu le reîncărca automat. Credința anterioară a fost eliminată înainte ca componenta să fie repornită pentru a o ridica pe cea nouă, cauzând eșecuri de autentificare. **Timeline:** * 13:07 CEST - Problema detectată, ancheta iniţiată * 13:28 CEST - Fix desfăşurat, serviciu restaurat **Root Cause:** O rotaţie credibilă terminată din secvenţă - vechea acreditare a fost îndepărtată înainte ca componenta consumatoare să fie repornită cu cea nouă. **Rezoluție:** Componentele afectate au fost reluate cu acreditările corecte. Serviciul a revenit la funcționarea completă fără pierderi de date. ** Măsuri preventive:** * S-a stabilit o procedură de rotaţie credibilă prin aplicarea unei secvenţe obligatorii: actualizarea, repornirea consumatorilor, verificarea, apoi eliminarea vechilor acreditări * Monitorizarea directă a eşecurilor de autentificare a conectivităţii bazei de date este implementată * Migraţia la managementul automat de acreditare care elimină rotaţia manuală pentru acest volum de muncă este în curs de desfăşurare Ne cerem scuze pentru întrerupere. Rămânem devotaţi fiabilităţii platformei Exalate.

Traducere automată din actualizarea oficială a incidentului.

1. 2 aprilie 2026 la 15:41 UTCinvestigating

   We are investigating some Exalate nodes being unavailable. We will be providing an update shortly on the investigation. Next update within 2 hours - or as soon as we have any relevant updates

2. 2 aprilie 2026 la 16:37 UTCidentified

   The issue was identified and we are currently working on restoring the nodes as soon as possible. Next update within 2 hours or as soon as we have any relevant updates

3. 2 aprilie 2026 la 18:25 UTCidentified

   We continue with the restoration efforts. Some nodes are already available. Next update will be within 2 hours or as soon as we have any relevant update.

4. 2 aprilie 2026 la 19:18 UTCmonitoring

   All nodes have been successfully restored. Our team is closely monitoring the system to ensure continued stability.

5. 2 aprilie 2026 la 21:26 UTCresolved

   This incident has been resolved.

1. 16 martie 2026 la 15:13 UTCinvestigating

   We are investigating reports by some users that the Exalate app is not available right now.

2. 16 martie 2026 la 15:56 UTCidentified

   We have identified the problem and the team is working to rectify this. We will provide an update of progress shortly.

3. 16 martie 2026 la 16:09 UTCmonitoring

   The services are fully functional again. We are very closely monitoring the situation.

4. 16 martie 2026 la 17:13 UTCresolved

   All systems are functional. We will be providing a post-mortem of the incident here in due course.

5. 31 martie 2026 la 09:44 UTCpostmortem

   **Incident:** Exalate Application Unavailability — March 16, 2026 **Duration:** 16:13 CET – 17:09 CET \(approximately 56 minutes\) **Impact:** The Exalate UI was inaccessible during this window. Issue synchronisation was not affected — integrations continued to run normally throughout. No data was lost. **Summary:** On March 16, 2026, the Exalate application became unavailable following a production infrastructure configuration change. A resource allocation adjustment applied to a critical authentication component proved insufficient under production load, causing repeated service interruptions. **Timeline:** * 16:13 CET — Issue reported, investigation initiated * 16:56 CET — Root cause identified, remediation initiated * 17:09 CET — Fix deployed, service restored * 18:13 CET — Full stability confirmed **Root Cause:** A resource limit adjustment deployed without cross-team review under-provisioned a critical authentication component. Under production load, the platform repeatedly terminated the component, rendering the application inaccessible. **Resolution:** Resource limits were corrected, restoring service. A further optimisation was applied during a subsequent scheduled maintenance window following joint engineering review. **Preventive Measures:** * All production infrastructure configuration changes now require joint sign-off from infrastructure and engineering leads before deployment * Resource and capacity parameters validated against production load baselines prior to deployment

1. 13 martie 2026 la 11:56 UTCinvestigating

   We are currently investigating an issue causing the Exalate website to be temporarily unavailable. Our team is actively working to identify the root cause and restore access as quickly as possible. This issue is strictly isolated to the Exalate.com webpage. Please note that Exalate.app and individual Nodes are not affected, and there is no impact on active integrations. We will provide an update within 4 hours, or sooner if new information becomes available.

2. 13 martie 2026 la 13:03 UTCinvestigating

   Update: We are continuing to investigate the performance issues affecting Exalate.com. We have identified an ongoing incident with our hosting provider, Hostinger, and are currently verifying the extent of the impact on our services. You can track their status directly here: https://statuspage.hostinger.com We will provide another update as soon as we have more information, or within the next 4 hours.

3. 13 martie 2026 la 14:31 UTCmonitoring

   We have identified and mitigated the issue that was causing performance degradation and intermittent unavailability of the Exalate.com website. After implementing mitigation measures, the website is now fully accessible and performing as expected. We have confirmed that Exalate.app, individual Nodes, and all active integrations remained unaffected throughout this incident. Our team will continue to monitor the situation closely to ensure continued stability. We will provide further updates only if the situation changes.

4. 13 martie 2026 la 18:19 UTCresolved

   This incident has been resolved.

5. 31 martie 2026 la 09:46 UTCpostmortem

   **Date:** March 17, 2026 **Duration:** 12:10 CET - 15:00 CET \(2 hours, 50 minutes\) **Impact:** The [exalate.com](http://exalate.com) website was completely inaccessible to all users for the duration of the incident. **Summary:** The hosting environment experienced resource exhaustion triggered by a sudden surge in web traffic. This was further exacerbated by a malfunctioning security plugin. **Timeline:** 12:10 CET: Incident start \(resource exhaustion begins\) 12:28 CET: Issue detected 14:40 CET: Root cause identified 15:00 CET: Service fully restored **Root Cause:** A spike in unique visitors has led to resource depletion on the hosting server. During the investigation, it was discovered that an installed security plugin was behaving inefficiently under high load, significantly compounding the CPU and memory usage, preventing the server from recovering. **Resolution:** Identified and blocked specific IP addresses responsible for an anomalous volume of requests. Deactivated and removed the problematic security plugin. Implemented an alternative solution to handle the plugin's core functionality without the performance overhead. **Preventive Measures:** Investigate and implement automated rate-limiting and IP blocking solutions \(e.g., WAF rules\) to handle traffic spikes.

1. 9 martie 2026 la 06:59 UTCinvestigating

   We have reports of some Exlate cloud nodes being unavailable. Our team is currently investigating the issue.

2. 9 martie 2026 la 07:11 UTCidentified

   Our cloud team has identified the root cause and is actively engaged in rectifying it.

3. 9 martie 2026 la 07:20 UTCmonitoring

   The issue has been fully rectified and all nodes are fully restored. We are closely monitoring the situation.

4. 9 martie 2026 la 09:00 UTCresolved

   After close monitoring, we consider the issue fully resolved. An RCA would be published here in due course.

5. 1 aprilie 2026 la 03:39 UTCpostmortem

   **Incident:** Exalate Cloud Service Disruption - March 9, 2026 **Duration:** 07:30 CET – 08:10 CET \(approximately 40 minutes\) **Impact:** Some Exalate Cloud nodes experienced temporary service disruption. Database write operations were briefly affected. Issue synchronisation resumed automatically once the issue was resolved. No data was lost. **Summary:** On March 9, 2026, the primary database instance serving part of the Exalate Cloud infrastructure reached full storage capacity. This prevented the database from processing write operations, temporarily impacting node availability. **Timeline:** * 07:30 CET - Issue detected, investigation initiated * 08:05 CET - Storage expanded, database operations resumed * 08:10 CET - Fix verified, nodes confirmed operational * 10:00 CET - Full stability confirmed after extended monitoring **Root Cause:** The primary database storage volume gradually reached full capacity under normal operational growth. Proactive storage monitoring did not fire in time. **Resolution:** Database storage was expanded and the service returned to full operation automatically. Additional alerting configured.

1. 23 ianuarie 2026 la 09:59 UTCinvestigating

   We have identify an incident with exalate.app that is currently not loading. We are currently investigating the issue and will be providing updates within the hour. This is not affecting the sync of issues but the UI for exalate is currently unavailable.

2. 23 ianuarie 2026 la 10:18 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 23 ianuarie 2026 la 12:18 UTCresolved

   This incident has been resolved.

4. 31 martie 2026 la 09:43 UTCpostmortem

   **Incident:** Exalate Application Unavailability — January 23, 2026 **Duration:** 10:59 CET – 11:18 CET \(approximately 19 minutes\) **Impact:** The Exalate UI was inaccessible during this window. Issue synchronisation was not affected — integrations continued to run normally throughout. No data was lost. **Summary:** On January 23, 2026, our monitoring detected a service outage affecting the Exalate application. The root cause was a deployment configuration change that unintentionally removed an active compute resource from the production environment. **Timeline:** * 10:59 CET — Issue detected, investigation initiated * 11:18 CET — Fix deployed, service restored * 13:18 CET — Full stability confirmed **Root Cause:** A deployment configuration change targeted the wrong resource section, resulting in an active production compute resource being removed and the application becoming inaccessible. **Resolution:** The affected resource was recreated and all services returned to full operation with no data loss. **Preventive Measures:** * Infrastructure-as-code changes must be validated in a non-production environment before production deployment * Peer review steps introduced to verify configuration targets prior to execution

1. 12 decembrie 2025 la 16:15 UTCinvestigating

   There is an outage on one of the clusters in Exalate cloud that might affect access to the nodes temporarily. We are currently investigating the issue to ensure that service is restored as soon as possible. A new update will be provided within 1 hour

2. 12 decembrie 2025 la 16:31 UTCidentified

   We have root caused the issue and the restoration process is underway already. The next update will be provided in 30mins.

3. 12 decembrie 2025 la 16:58 UTCidentified

   The recovery process is still ongoing. We will provide an update within an hour.

4. 12 decembrie 2025 la 19:11 UTCidentified

   We continue to work on the restoration of the affected nodes. We will be providing a new update in one hour.

5. 12 decembrie 2025 la 20:20 UTCidentified

   Nodes are being restored now, most nodes are now online, a full operational message will be posted once all nodes are back online.

6. 13 decembrie 2025 la 01:51 UTCidentified

   Most nodes are back on operational status, a full operational message will be posted once all nodes are back.

7. 13 decembrie 2025 la 02:56 UTCmonitoring

   All nodes are back to operational status now. We continue to monitor the stability closely.

8. 13 decembrie 2025 la 04:26 UTCresolved

   All Exalate nodes are stable and working normally. A post-mortem for the incident will be published in due course.

9. 22 decembrie 2025 la 04:43 UTCpostmortem

   **Incident: Service Outage - December 12, 2025** **Duration:** 16:35 CET - 03:01 CET \(approximately 10 hours\) **Impact:** A significant number of Exalate Cloud nodes experienced service unavailability, resulting in temporary disruption to data synchronization services. No data was lost during this incident. **Summary:** On December 12, 2025, our infrastructure monitoring detected a service outage affecting Exalate Cloud customers on our production clusters. The root cause was identified as a storage system failure triggered by network latency on a legacy infrastructure component, which caused storage connectivity issues for customer workloads. **Timeline:** * 16:35 CET - Issue detected by monitoring systems * 17:31 CET - Root cause identified, restoration initiated * 21:20 CET - Majority of nodes restored to service * 03:01 CET - Full service restoration confirmed **Root Cause:** A storage management component became unresponsive due to elevated network latency caused by a legacy networking layer. This resulted in storage disconnection for customer workloads. **Resolution:** The storage system was restored, all affected workloads were rescheduled, and the external dependency was updated to a supported version. All nodes were returned to full operation with no data loss. **Preventive Measures:** * Deploying patches to address the storage component stability issue * Accelerating migration away from the legacy networking layer to modern infrastructure * Implementing internal mirroring of critical external dependencies to eliminate reliance on third-party availability * Enhancing operational safeguards for infrastructure management procedures We sincerely apologize for the disruption this incident caused. Our team remains committed to improving the reliability and resilience of the Exalate Cloud platform.

1. 27 noiembrie 2025 la 11:47 UTCinvestigating

   We are investigating reports of some Exalate nodes being unavailable. We will be providing an update shortly on the investigation.

2. 27 noiembrie 2025 la 12:33 UTCidentified

   We have identified the problem and are working to restore full service as soon as possible.

3. 27 noiembrie 2025 la 13:47 UTCidentified

   Most nodes are currently running but we are still experiencing intermittent service failures. The full fix is being implemented now.

4. 27 noiembrie 2025 la 15:31 UTCmonitoring

   All nodes are back online and we are closely monitoring the cluster health.

5. 27 noiembrie 2025 la 16:51 UTCidentified

   We have detected some instability again and are investigating why some nodes are not reachable again.

6. 27 noiembrie 2025 la 20:48 UTCidentified

   All nodes are now back online and our team is working on stabilizing the services

7. 27 noiembrie 2025 la 22:04 UTCmonitoring

   All nodes are now fully operational. Any communication error reported in the console should now disappear after hitting "Resolve and retry". If you encounter any further problem please reach out to our support team. We continue to monitor the cluster closely and investigate to root cause the incident.

8. 28 noiembrie 2025 la 07:08 UTCresolved

   We have closely monitored the health of the affected Exalate nodes, and they are all performing as per expectation. A post-mortem of the incident will be published in due course.

9. 12 decembrie 2025 la 12:02 UTCpostmortem

   **Incident: Service Degradation - November 27, 2025** **Duration:** 11:26 CET - 21:37 CET \(~10 hours\) **Impact:** Approximately 700 Exalate Cloud nodes experienced intermittent connectivity issues, resulting in temporary disruption to data synchronization services. No data was lost during this incident. **Summary:** On November 27, 2025, our infrastructure monitoring detected service degradation affecting a subset of Exalate Cloud customers. The root cause was identified as storage I/O contention on the underlying database infrastructure, which caused the primary database to become unresponsive intermittently. **Timeline:** * 11:26 CET - Issue detected by monitoring systems * 11:30 CET - Engineering team began investigation * 15:30 CET - Initial mitigation applied \(infrastructure scaling\) * 18:30 CET - Root cause identified and permanent remediation initiated * 21:37 CET - Full service restoration confirmed **Root Cause:** Database storage was experiencing resource contention due to shared infrastructure components, causing elevated I/O latency. This triggered automated health checks to restart the database service repeatedly, compounding the connectivity issues. **Resolution:** The database was migrated to dedicated storage resources and allocated additional compute capacity. All affected nodes were restored to full operation with no data loss. **Preventive Measures:** * Implementing enhanced storage latency monitoring and alerting * Reviewing infrastructure health check configurations for database workloads * Auditing storage allocation across all database clusters to prevent similar contention We apologize for any inconvenience this incident may have caused. Our team remains committed to maintaining the reliability and performance of the Exalate Cloud platform.

1. 20 noiembrie 2025 la 09:43 UTCidentified

   We have identified an issue when trying to access the SyncRoom page, caused by a significant increase in DNS traffic originating from an external problem between Hostinger and Cloudflare. This external issue is currently impacting our service and is preventing the SyncRoom page and the community from loading Important Note: This issue does not affect the core Exalate functionality. Synchronization is continuing to work as expected. We are actively working to resolve this and will provide an update within the next two hours. Thank you for your patience.

2. 20 noiembrie 2025 la 10:29 UTCmonitoring

   A fix has been implemented by Hostinger and the services have been restored (Exalate community and SyncRoom) We will continue to monitor the results.

3. 20 noiembrie 2025 la 11:23 UTCresolved

   This incident has been resolved.

4. 1 aprilie 2026 la 04:08 UTCpostmortem

   timeout

1. 4 octombrie 2025 la 06:18 UTCinvestigating

   We are investigating reports of users unable to access the Exalate console on some systems. We will be providing an update soon.

2. 4 octombrie 2025 la 06:30 UTCmonitoring

   The problem has been identified and the fix has been put in place.

3. 4 octombrie 2025 la 06:54 UTCresolved

   The issue is fully resolved and all nodes are operational. A post-mortem will be provided here in due course.

4. 14 noiembrie 2025 la 12:23 UTCpostmortem

   ## **Summary** On October 4, 2025, Exalate Cloud experienced an issue that caused some Exalate nodes to become temporarily inaccessible at 04:00 CEST. This resulted in UI access issues and potential synchronization interruptions for part of our customer base. All services were fully restored by 09:00 CEST. ## **Impact** Customers using Exalate cloud nodes experienced: * Inability to access nodes * Sync failures or delays * Temporary disruption of workflow automations No data loss occurred. ## **Root Cause** There was an error in the certification renewal process. This prevented affected nodes from completing required secure connections, making them temporarily unreachable. ## **Resolution** After identifying the cause, the certificate was renewed and deployed. Services began recovering immediately and full functionality was validated shortly thereafter. ## **Preventive Measures** We are implementing several improvements to prevent recurrence, including: * Expanded automated monitoring for certificate validity * Additional service health checks, including customer-facing endpoints * Automated renewal processes for critical certificates * Strengthened operational procedures around certificate lifecycle management

1. 3 octombrie 2025 la 09:43 UTCmonitoring

   We've released a configuration update for Jira Cloud connections running version 5.28.5. Who is affected: Customers using external script repositories in their Jira Cloud connections may experience script-related errors after upgrading to 5.28.5. Resolution: If you're experiencing issues with your scripts, please contact our support team at [email protected] - we'll assist you with a quick configuration update. Status: We're actively monitoring and reaching out to affected customers.

2. 5 noiembrie 2025 la 14:17 UTCresolved

   This incident has been resolved.

3. 1 aprilie 2026 la 04:09 UTCpostmortem

   timeout

1. 24 septembrie 2025 la 10:56 UTCinvestigating

   There is an outage on one of the clusters in Exalate cloud that might affect access to the nodes temporarily. We are currently investigating the issue to ensure that service is restored as soon as possible.

2. 24 septembrie 2025 la 11:18 UTCidentified

   We have root caused the issue and the restoration process is underway already. The next update will be provided in 30mins.

3. 24 septembrie 2025 la 11:47 UTCidentified

   The recovery process is still ongoing. We will provide an update within an hour.

4. 24 septembrie 2025 la 13:00 UTCmonitoring

   All nodes are fully recovered. We continue to closely monitor the situation.

5. 24 septembrie 2025 la 14:50 UTCidentified

   Our monitoring uncovered a problem still lingering with the cluster. We are working to restore full functionality as soon as possible.

6. 24 septembrie 2025 la 16:56 UTCidentified

   Node recovery has presented some challenges and is taking longer than expected. We continue to strive to bring all nodes back online as soon as possible. Next update will be provided within 2 hours.

7. 24 septembrie 2025 la 18:47 UTCidentified

   Infrastructure component failures have been addressed by our Engineering team. Next step: We are restarting the individual Exalate nodes impacted by the failure. More information will be provided in an hour.

8. 24 septembrie 2025 la 19:54 UTCidentified

   We continue restarting the individual Exalate nodes impacted by the failure. 5% of the affected nodes have been brought back online. Further updates to be expected in an hour

9. 24 septembrie 2025 la 20:51 UTCidentified

   The team is actively working through the restart sequence for all individual Exalate nodes. This is a deliberate, multi-step process to ensure stability upon full restoration. Further updates to be expected in an hour.

10. 24 septembrie 2025 la 21:45 UTCidentified

    Following the deliberate, multi-step sequence, the engineering team has now moved into the main restoration phase. We are actively scaling up the restart of the affected Exalate nodes. We'll continue to monitor stability closely. We will provide the next update in one hour.

11. 24 septembrie 2025 la 22:49 UTCidentified

    The engineering team continue working on the main restoration phase. We'll continue to monitor stability closely. Further updates to be expected in an hour

12. 24 septembrie 2025 la 23:50 UTCidentified

    During the scale-up phase, the restoration process has presented some challenges that are taking longer than initially expected to resolve. The engineering team is actively working to address these stability issues. We will provide the next update within one hour.

13. 25 septembrie 2025 la 00:48 UTCidentified

    The previous technical challenges have been addressed. We have re-initiated the scale-up of the Exalate nodes and are closely monitoring the environment for stability. We will provide the next update within one hour.

14. 25 septembrie 2025 la 01:44 UTCidentified

    We are continuing the scale-up of the Exalate nodes. The team is maintaining a close monitoring posture to ensure stability throughout this process. We will provide the next update in one hour.

15. 25 septembrie 2025 la 03:23 UTCmonitoring

    All nodes are fully restored and functioning normally now. We continue to monitor the cluster carefully to ensure stability.

16. 25 septembrie 2025 la 14:21 UTCresolved

    We have extensively monitored the cluster health and there have been no outstanding issues found.

17. 10 octombrie 2025 la 10:41 UTCpostmortem

    ## Executive Summary On September 24, 2025, Exalate experienced a service interruption lasting 17 hours and 28 minutes that affected our cloud-hosted integration nodes. During this time, customers were unable to synchronize data between their integrated systems. **No customer data was lost.** We sincerely apologize for the inconvenience and want to share what happened and how we're preventing future issues. ## What Happened **Timeline:** * **10:02 UTC \(Sept 24\):** Infrastructure issue detected through customer reports * **13:00 UTC:** Partial service restoration achieved * **13:45 UTC:** Secondary technical issue caused complete service unavailability * **17:24 UTC:** Core infrastructure restored * **21:00 UTC:** Priority customer services online * **03:30 UTC \(Sept 25\):** Full service restoration completed **Root Cause:** A network connectivity issue on our hosting platform triggered a cascading infrastructure failure. The recovery process was complex due to database resilience challenges and infrastructure management system complications. ## Customer Impact **During the outage:** * Data synchronization between systems \(Jira, ServiceNow, etc.\) was unavailable * Automated workflow processes were temporarily halted **What was NOT affected:** * **No customer data was lost or corrupted** * All existing synchronized data remained intact * Customer configurations and sync histories were preserved ## Our Response We immediately activated our 24/7 incident response team, maintained continuous status page updates, directly contacted Enterprise customers, and coordinated with infrastructure providers throughout the recovery. ## Prevention Measures We're implementing comprehensive improvements on an accelerated timeline: **Immediate \(October 2025\):** * Enhanced infrastructure monitoring and alerting systems * Comprehensive disaster recovery documentation **Short-term \(November 2025\):** * Infrastructure resilience improvements * Automated recovery procedures * Regular disaster recovery testing **Medium-term \(Q1 2026\):** * Multi-cloud architecture implementation * Advanced predictive monitoring ## Customer Support If you need assistance related to this outage: * **Enterprise Customers:** Use your dedicated support channels * **Standard Support:** Submit tickets through our support portal * **Status Updates:** Monitor our status page for ongoing information We apologize for this service disruption and appreciate your patience. Your trust is essential to our business, and we're committed to earning it through reliable service delivery and continuous improvement.

1. 29 august 2025 la 16:18 UTCinvestigating

   We are investigating a problem where IssueLinks are being removed from Jira cloud tickets. Progress and actions will be notified accordingly, if you encountered this problem please reach us on support portal.

2. 29 august 2025 la 16:57 UTCidentified

   The issue has been identified and we are performing remediation actions.

3. 29 august 2025 la 21:04 UTCidentified

   All nodes have been moved from the affected version and a workaround to remediate the possible effects on issue links is being investigated.

4. 31 august 2025 la 19:00 UTCmonitoring

   We identified the affected instances and provided remediation steps to all affected clients to restore the removed links.

5. 5 septembrie 2025 la 11:56 UTCresolved

   The issue affecting Jira Cloud issue links has been fully resolved. A detailed postmortem will be published soon outlining the root cause and preventive measures being implemented.

6. 18 septembrie 2025 la 06:57 UTCpostmortem

   # Exalate v5.28 Issue Links Synchronization - Technical Incident Report **Incident Date:** 29/Aug/2025 **Duration:** ~4 hours from detection to rollback completion **Impact:** Issue link synchronization behavior change affecting multiple customer instances **Status:** Resolved with data restoration completed ## Timeline The incident was first detected  on 29/Aug at 17:56 when a customer reported issue links being removed after upgrading to v5.28. Within eight minutes, at 18:04, the support team received multiple similar reports and immediately requested a rollback. The formal incident response was initiated at 18:17, and the rollback process to v5.27.0 began at 18:48. The rollback was completed across all affected instances by 22:12 the same day, approximately four hours after initial detection. Recovery efforts continued over the weekend. On 30/Aug at 09:43, the data restoration team was assembled and began developing recovery procedures. The comprehensive customer communication deployment occurred on 01/Sep at 17:05, providing affected customers with restoration instructions and individualized support. _\(All times CET\)_ ‌ ‌ ## Root Cause Analysis The technical issue stemmed from a synchronization enhancement in v5.28 that compared issue links between source and destination systems. The implementation operated under the assumption that links present on the destination but not on the source represented synchronization inconsistencies requiring removal. This approach failed to distinguish between links managed by Exalate and links created independently outside the synchronization scope. Several contributing factors enabled this issue to reach production. The scope definition did not account for mixed environments where synchronized and non-synchronized links coexist on the same system. Test coverage focused primarily on standard synchronization flows rather than these mixed data environments. Additionally, the modification affected a broader scope than initially anticipated during the development and review process. The impact characteristics were significant but recoverable. Multiple customer instances experienced removal of issue links that existed outside the intended synchronization scope. However, service functionality continued throughout the incident, and comprehensive audit logs preserved all affected link data, which enabled complete restoration of the removed links.Regarding data security and privacy, the audit logs contain only metadata elements such as issue identifiers, link types, and relationship mappings. No sensitive customer content, comments, or detailed issue information was captured in these logs. This metadata-only approach ensured that the restoration process could proceed while maintaining appropriate data protection standards. ## Learnings On the positive side, the incident response team made a rapid rollback decision, quickly identifying this as the appropriate technical solution rather than attempting a forward fix. The comprehensive logging infrastructure proved invaluable, enabling complete data restoration from audit trails. Cross-functional coordination worked well across engineering, customer success, and operations teams. The structured communication approach maintained clarity and transparency throughout the resolution process. The incident also revealed important areas for system enhancement. Synchronization logic in complex integration scenarios requires better handling of mixed data environments where multiple systems manage different subsets of the same data types. Testing scope needs expansion to cover mixed synchronized and non-synchronized environments comprehensively. Change evaluation processes require enhancement for modifications that affect customer data. Monitoring capabilities need improvement to enable proactive detection of synchronization behavior changes before customer impact. Several process improvements have been \(or are being\) implemented as a result. Enhanced code review procedures now include additional requirements specifically for data modification operations. Expanded testing protocols cover scenarios involving mixed data environments and include dedicated data preservation validation. Improved monitoring systems detect synchronization pattern changes and unusual data modification activities. Updated release procedures include enhanced evaluation criteria for data-affecting changes and improved rollback automation capabilities.