Istoricul incidentelor Samanage

1. 31 august 2026 la 15:15 UTCidentified

   În prezent, ne confruntăm cu întârzieri în ceea ce privește informațiile actualizate care figurează pe platformă. Bilete noi și actualizate, comentarii, schimbări de incident și actualizări de câmp, cum ar fi statul și titlul, precum și alte funcții, sunt uneori lente pentru a actualiza și a arăta informații depășite. Vedem, de asemenea, timpul de încărcare a paginii fiind afectat. Echipa a identificat problema și lucrează la o rezoluție. Puteți experimenta unele întârzieri în timp ce vom rula fix pe platforma.

2. 31 august 2026 la 15:58 UTCmonitoring

   Fixarea a fost implementată, şi procesăm activ restul actualizărilor biletelor. În timp ce prelucrarea este în curs de desfășurare, unele actualizări ale biletelor pot continua să experimenteze întârzieri. Ne așteptăm ca aceste întârzieri să se rezolve pe măsură ce registrul este eliminat. Vom continua să monitorizăm sistemul și să oferim actualizări suplimentare pe măsură ce prelucrarea progresează.

3. 31 august 2026 la 16:50 UTCmonitoring

   Vedem îmbunătățiri în urma implementării fixului; monitorizăm în mod activ sistemul pentru a garanta că performanța rămâne stabilă și că toate actualizările întârziate sunt pe deplin prelucrate.

4. 31 august 2026 la 17:42 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 14 iulie 2026 la 14:30 UTCinvestigating

   Investigăm în prezent o problemă care afectează Biroul SolarWinds Service. Unii utilizatori nu pot accesa cererea în acest moment. Echipa noastră lucrează activ pentru a identifica cauza și a restabili serviciul cât mai repede posibil. Vom împărtăși o altă actualizare de îndată ce mai multe informații sunt disponibile.

2. 14 iulie 2026 la 14:44 UTCinvestigating

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

3. 14 iulie 2026 la 14:57 UTCinvestigating

   Aplicația este accesibilă din nou, iar serviciul a fost restabilit. Echipa noastră continuă să monitorizeze îndeaproape aplicaţia pentru a asigura stabilitatea. Vom furniza o altă actualizare dacă vor fi identificate alte probleme.

4. 14 iulie 2026 la 15:05 UTCmonitoring

   Echipa noastră continuă să monitorizeze îndeaproape aplicaţia pentru a asigura stabilitatea. Alte actualizări vor fi comunicate de îndată ce acestea sunt disponibile.

5. 14 iulie 2026 la 16:01 UTCresolved

   După o perioadă lungă de monitorizare, SolarWinds Service Desk operează în mod normal. În acest moment, considerăm incidentul rezolvat. Analiza cauzelor profunde (RCA) va fi împărtășită în zilele următoare după finalizarea anchetei. Dacă aveți nevoie de asistență sau experiență suplimentară, vă rugăm să ne contactați la suport [email protected].

Traducere automată din actualizarea oficială a incidentului.

1. 7 iulie 2026 la 15:59 UTCidentified

   Investigăm în prezent o problemă care afectează Biroul de service SolarWinds, unde incidentele create prin e-mail sunt transmise cu succes, iar mesajele de confirmare sunt trimise, dar incidentele nou create nu pot apărea pe pagina Index Incident. Echipa noastră este activ de lucru pentru a identifica cauza rădăcină și de a restabili vizibilitatea normală cât mai repede posibil. Vom oferi o altă actualizare de îndată ce mai multe informații devin disponibile.

2. 7 iulie 2026 la 16:23 UTCinvestigating

   Continuăm să investigăm o problemă în SolarWinds Service Desk unde noi incidente nu pot apărea pe pagina Indexului Incidentelor, în ciuda faptului că au fost transmise cu succes și generează mesaje de confirmare. Echipa noastră încearcă să identifice cauza şi să restabilească vizibilitatea normală. Vom împărtăși o altă actualizare de îndată ce mai multe informații sunt disponibile.

3. 7 iulie 2026 la 16:57 UTCidentified

   Am identificat cauza principală a problemei care afectează Biroul de service SolarWinds, unde noi incidente nu pot apărea pe pagina Indexului de incidente, în ciuda faptului că au fost depuse cu succes. Vom împărtăși o altă actualizare de îndată ce mai multe informații devin disponibile.

4. 7 iulie 2026 la 18:00 UTCmonitoring

   A fost implementat un fix pentru a remedia problema care afectează Biroul de service SolarWinds, în cazul în care noi incidente nu pot apărea pe pagina Index Incident, în ciuda faptului că au fost create cu succes. Continuăm să monitorizăm îndeaproape serviciul pentru a ne asigura că vizibilitatea normală este restabilită complet.

5. 7 iulie 2026 la 19:00 UTCresolved

   După o perioadă lungă de monitorizare, SolarWinds Service Desk operează în mod normal. În acest moment, considerăm incidentul rezolvat. Dacă aveți nevoie de asistență sau experiență suplimentară, vă rugăm să ne contactați la suport [email protected].

Traducere automată din actualizarea oficială a incidentului.

1. 30 iunie 2026 la 17:22 UTCinvestigating

   Investigăm în prezent o problemă care afectează Biroul de service SolarWinds în care incidentele create prin e-mail sunt transmise cu succes și mesajele de confirmare sunt trimise, dar incidentele nou create nu pot apărea în pagina Index Incident. Echipa noastră lucrează activ pentru a identifica cauza şi pentru a restabili vizibilitatea normală cât mai repede posibil. Vom împărtăși o altă actualizare de îndată ce mai multe informații devin disponibile.

2. 30 iunie 2026 la 17:58 UTCidentified

   Am identificat cauza problemei raportate și lucrează la o fix cât mai repede posibil. Mulţumesc pentru răbdare.

3. 30 iunie 2026 la 18:09 UTCmonitoring

   Am finalizat fixarea pentru această problemă și serviciile revin la normal. Incidentele transmise prin e-mail ar trebui să apară acum în mod corespunzător în pagina Index Incident așa cum se aștepta. Echipa noastră va continua să monitorizeze îndeaproape mediul pentru a asigura stabilitatea și a confirma că problema a fost rezolvată pe deplin. Apreciem răbdarea dumneavoastră în timp ce am lucrat pentru a aborda această problemă.

4. 30 iunie 2026 la 19:47 UTCmonitoring

   Continuăm să monitorizăm comportamentul îndeaproape în timp ce echipa noastră lucrează pentru a confirma vizibilitatea consecventă în lista de incidente. Vom împărtăși o altă actualizare de îndată ce mai multe informații devin disponibile.

5. 30 iunie 2026 la 21:04 UTCmonitoring

   Vedem îmbunătățiri în performanța generală a aplicației. Echipa noastră continuă să monitorizeze îndeaproape mediul pentru a asigura stabilitatea și a confirma că nu apar alte probleme. Vom împărtăși actualizări suplimentare, după cum este necesar.

6. 30 iunie 2026 la 22:02 UTCresolved

   După o perioadă lungă de monitorizare, problema nu a reapărut și nu am primit niciun raport suplimentar de impact. Serviciul funcţionează normal şi considerăm acest incident rezolvat. Dacă continuați să experimentați orice probleme sau aveți nevoie de asistență suplimentară, vă rugăm să ne contactați prin e-mail la suport [email protected], iar echipa noastră va fi bucuroasă să vă ajute.

Traducere automată din actualizarea oficială a incidentului.

1. 23 iunie 2026 la 16:14 UTCinvestigating

   În prezent investigăm o problemă în care incidentele create prin e-mail nu pot apărea imediat în lista de incidente din Biroul de servicii SolarWinds. În timpul revizuirii noastre, am confirmat că notificările de creare de incidente sunt trimise cu succes, iar incidentele afectate pot fi accesate prin intermediul legăturilor lor directe. Cu toate acestea, poate exista o întârziere înainte ca aceste incidente să devină vizibile în lista de incidente din cadrul UI. Echipa noastră investighează în mod activ acest comportament și lucrează pentru a determina cauza. Vom împărtăși o altă actualizare de îndată ce mai multe informații devin disponibile.

2. 23 iunie 2026 la 16:37 UTCmonitoring

   În prezent, monitorizăm această problemă. Investigația noastră a confirmat că crearea de incidente are loc cu succes și e-mailurile de notificare sunt trimise conform așteptărilor. Cu toate acestea, unele incidente create prin e-mail nu pot apărea imediat în lista de incidente din cadrul UI, chiar dacă rămân accesibile prin intermediul legăturii directe incluse în emailul de notificare. Continuăm să monitorizăm comportamentul îndeaproape în timp ce echipa noastră lucrează pentru a confirma vizibilitatea consecventă în lista de incidente. Vom împărtăși o altă actualizare de îndată ce mai multe informații devin disponibile.

3. 23 iunie 2026 la 18:31 UTCresolved

   Monitorizarea noastră arată că problema care afectează vizibilitatea incidentului a fost rezolvată. Am continuat să monitorizăm îndeaproape serviciul și nu am observat alte evenimente ale problemei. În acest moment, considerăm incidentul rezolvat. Dacă aveți nevoie de asistență sau experiență suplimentară, vă rugăm să ne contactați la suport [email protected].

Traducere automată din actualizarea oficială a incidentului.

1. 3 iunie 2026 la 12:18 UTCinvestigating

   We are currently investigating reports of slow performance issues in SolarWinds Service Desk. Our team is working to resolve this as quickly as possible.

2. 3 iunie 2026 la 13:03 UTCidentified

   We have identified the cause of the reported issue and are actively working to implement a fix as quickly as possible. Thank you for your patience and understanding while we work toward a resolution.

3. 3 iunie 2026 la 13:32 UTCmonitoring

   We are seeing improved performance on our end and are continuing to monitor the situation closely. We are also working to confirm whether customers are experiencing similar improvements as we continue our efforts to ensure full service stability. We appreciate your patience and understanding during this time. We will provide another update as soon as additional information becomes available.

4. 3 iunie 2026 la 14:26 UTCresolved

   We have continued to monitor the service and have not observed any further issues. In addition, we have not received any new reports of slow performance. Based on our monitoring and the current system status, this incident is considered resolved. Should you require any further assistance or experience any additional issues, please do not hesitate to contact us at [email protected]. Thank you for your patience and cooperation throughout this process.

1. 6 mai 2026 la 13:23 UTCinvestigating

   We are aware of an issue that caused the application to be unavailable for a few minutes. Our team is currently investigating the cause and monitoring the service to ensure it remains stable. Further updates will be posted here as more information becomes available.

2. 6 mai 2026 la 13:53 UTCmonitoring

   The services are currently operating normally, and our engineering team is closely monitoring system performance to ensure continued stability. We will provide additional updates here if we observe any further impact or if additional action is required.

3. 6 mai 2026 la 15:25 UTCresolved

   Following an extended monitoring period, the issue has not reappeared, and no further impact has been reported. Services are operating normally, and we consider this incident resolved. If you experience any additional issues or need assistance, please contact us at [email protected], and our team will be glad to help.

1. 29 aprilie 2026 la 19:01 UTCinvestigating

   We are aware of an issue that caused the application to be unavailable for approximately two minutes. Our team is currently investigating the cause and monitoring the service to ensure it remains stable. Further updates will be posted here as more information becomes available.

2. 29 aprilie 2026 la 19:08 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 aprilie 2026 la 19:56 UTCmonitoring

   The services are currently operating normally, and our engineering team is closely monitoring system performance to ensure continued stability. We will provide additional updates here if we observe any further impact or if additional action is required.

4. 29 aprilie 2026 la 23:28 UTCresolved

   After an extended period of monitoring, the issue has not resurfaced and we have not received any additional reports of impact. Service is operating normally and we are considering this incident resolved. If you continue to experience any issues or need further assistance, please contact us via email at [email protected], and our team will be happy to help.

1. 3 aprilie 2026 la 12:33 UTCinvestigating

   We are currently investigating reports of slow performance and intermittent Error 500 issues in SolarWinds Service Desk. Our team is working to resolve this as quickly as possible.

2. 3 aprilie 2026 la 13:00 UTCidentified

   We've identified the cause of the reported issue and are working on a fix as quickly as possible. Thank you for your patience.

3. 3 aprilie 2026 la 13:42 UTCmonitoring

   We have completed the fix for this issue and will continue to monitor the situation to ensure stability.

4. 3 aprilie 2026 la 15:08 UTCinvestigating

   We have observed unexpected behavior following the recent fix and are currently reviewing the issue. Our team is continuing to investigate while working to ensure full stability. We appreciate your patience and will provide further updates as soon as more information becomes available.

5. 3 aprilie 2026 la 16:29 UTCinvestigating

   We are actively investigating continued unexpected behavior following a recent fix. Our team is working to ensure full stability. We appreciate your patience and will share another update as soon as more information is available.

6. 3 aprilie 2026 la 17:56 UTCmonitoring

   We are seeing improved results on our end and are continuing to monitor performance closely. We are also working to confirm whether customers are seeing similar improvement while we continue to ensure full stability. We appreciate your patience and will provide another update as soon as more information becomes available.

7. 3 aprilie 2026 la 21:57 UTCresolved

   We have continued to monitor the service and have not observed any further issues. Additionally, we have not received any new reports of slow performance or Error 500 errors. At this time, the incident is considered resolved. If further assistance is needed, please contact [email protected]. Thank you for your patience throughout this process.

1. 18 martie 2026 la 09:14 UTCinvestigating

   We have received reports of overlapping text fields in Incident/Service Request tickets and are currently investigating the issue.

2. 18 martie 2026 la 09:46 UTCidentified

   We have identified the cause of the overlapping text fields and are currently working on a fix. We will provide updates as soon as progress is made. Thank you for your patience and understanding.

3. 18 martie 2026 la 11:52 UTCidentified

   We are still working on fixing the issue. We will continue to monitor the situation and provide updates as they become available.

4. 18 martie 2026 la 11:57 UTCidentified

   We will deploy a fix shortly. We will provide an update once it has been deployed.

5. 18 martie 2026 la 12:26 UTCidentified

   We are in the process of deploying the fix. We will keep you updated as progress continues.

6. 18 martie 2026 la 12:47 UTCmonitoring

   We have completed the deployment of the fix for this issue and will continue to monitor the situation to ensure stability.

7. 18 martie 2026 la 13:30 UTCresolved

   This issue has been resolved.

1. 2 februarie 2026 la 15:49 UTCinvestigating

   We are currently experiencing performance issues in the Service Desk Application, and our team is investigating. This impacts actions such as navigating through the Incidents page and other areas of the app.

2. 2 februarie 2026 la 16:21 UTCinvestigating

   We have identified elevated load on the database layer in our US Service Desk environment. This is leading to slow page loads, delayed data population, and intermittent 504 Gateway Timeout errors for some customers. Our team is actively working on remediation to reduce database load and restore normal performance. During this time, the application may run more slowly than normal. We will provide the next update within 30 minutes or sooner as we make progress.

3. 2 februarie 2026 la 16:50 UTCidentified

   We are still actively working on reducing the elevated database load in our US Service Desk environment. The underlying issue has been identified, and our team is continuing remediation efforts to stabilize performance.

4. 2 februarie 2026 la 17:26 UTCidentified

   We are continuing to work on a fix for this issue and further reducing the elevated database load in our US Service Desk environment. Some users may still experience intermittent slowness or timeouts while we complete these changes. We will provide another update within 30 minutes or as soon as we have more information.

5. 2 februarie 2026 la 18:19 UTCmonitoring

   We have implemented a fix for the database load issue affecting our US Service Desk environment; we are restarting a set of frontend services to complete remediation. Users should now begin to see improved performance and fewer timeouts as these changes take effect. Our team will continue to closely monitor the environment and will provide another update once performance is fully stabilized.

6. 2 februarie 2026 la 18:55 UTCresolved

   We have resolved the database load issue affecting our US Service Desk environment and restarted the impacted frontend services. Since then, performance has remained stable under monitoring, and we are no longer observing elevated errors or timeouts. This incident is now closed. If you continue to experience slowness or errors, please contact SolarWinds Support or open a ticket so we can investigate further.

1. 28 ianuarie 2026 la 19:54 UTCinvestigating

   We are investigating an issue where some users are unable to fully load service (catalog) requests. Affected pages may briefly appear and then show blank or incomplete content. Our engineering team is actively investigating the cause and working to restore full functionality. We will provide updates on this page as more information becomes available. If you are impacted and need assistance, please contact SolarWinds Support through your usual channels.

2. 28 ianuarie 2026 la 20:08 UTCinvestigating

   We are continuing to investigate this issue.

3. 28 ianuarie 2026 la 20:43 UTCinvestigating

   Our investigation has determined that this issue is limited to a subset of Service Desk service requests and service catalog items and does not affect all users or all catalogs. We are continuing to investigate the underlying cause and will provide additional updates on this page as our work progresses.

4. 28 ianuarie 2026 la 21:29 UTCidentified

   We have identified the root cause of the issue. It occurs when a process workflow includes a Send Notification action that sends an email to a user or email address that does not have a valid user account within the affected Service Desk instance. Our engineering team is actively working on a fix. Additional updates will be provided on this page as progress continues.

5. 28 ianuarie 2026 la 23:17 UTCidentified

   We are actively working on a fix for this issue. As a reminder, the cause occurs when a process workflow includes a Send Notification action that sends an email to a user or email address that does not have a valid user account in the affected Service Desk instance. As a temporary workaround, service desk administrators can update the affected workflows so that Send Notification actions are configured to send emails to a named user with a valid Service Desk account instead of an email address that is not associated with a user. We will provide further updates on this page as our work progresses.

6. 29 ianuarie 2026 la 01:41 UTCidentified

   Our engineering team has prepared a fix for this issue, and the deployment process has started. During the deployment window, some users may experience brief slowdowns or intermittent delays; we expect any impact to be minimal and temporary. We will provide a further update on this page once the deployment has finished.

7. 29 ianuarie 2026 la 03:30 UTCmonitoring

   Our Engineering team has successfully applied a fix and is applying it retroactively to resolve the issue for all affected users. Any interruptions during this process should be minimal. We will provide another update in the next hour.

8. 29 ianuarie 2026 la 05:38 UTCmonitoring

   Our Engineering team is continuously working on applying a fix to the data for all affected users. Further updates will be provided in the next hour.

9. 29 ianuarie 2026 la 08:19 UTCmonitoring

   Our Engineering team is actively deploying a remediation to address issues resulting in page load failures, blank pages, or incomplete content. Further updates will be provided as progress continues.

10. 29 ianuarie 2026 la 11:05 UTCmonitoring

    Our team is in the final stages of deploying the fix. We expect completion shortly and will share an update immediately.

11. 29 ianuarie 2026 la 11:28 UTCmonitoring

    The fix deployment is now complete, and our team is closely monitoring the results to ensure stability.

12. 29 ianuarie 2026 la 14:12 UTCresolved

    We are marking this issue as resolved, as we have confirmed that all new service requests work correctly and previously submitted requests work as intended. If the issue resurfaces or if you require any further assistance, please don’t hesitate to contact us at [email protected].

1. 27 ianuarie 2026 la 18:51 UTCinvestigating

   We are currently investigating an issue affecting Service Requests for customers in the US and AU regions. Initial findings indicate that when the approval process is configured to use the Incident Assignee as the approver, the workflow may terminate unexpectedly with the following error: “The task [Task Name] has been automatically declined per predefined approval conditions because the approval step contains unknown approvers.” Our engineering teams are actively working to identify the root cause and determine a resolution. If you have questions, are experiencing related issues, or would like to provide additional details, please contact us via chat or email at [email protected]. We will continue to provide updates as more information becomes available.

2. 27 ianuarie 2026 la 19:48 UTCinvestigating

   Our team is actively investigating the issue, which may be related to a recent deployment. We are working to identify the root cause and resolve it, and we will provide updates as more information becomes available. Thank you for your patience.

3. 27 ianuarie 2026 la 21:49 UTCinvestigating

   Our team is continuing to investigate the issue and is focused on identifying the root cause and resolving it as quickly as possible. We will provide updates as new details become available. Thank you for your patience.

4. 27 ianuarie 2026 la 23:13 UTCidentified

   We have identified the root cause of the issue affecting Service Request approval workflows for customers in the US and AU regions. We are currently testing a fix. Once testing is complete, we will proceed with deployment and share further updates.

5. 28 ianuarie 2026 la 03:44 UTCidentified

   The fix we had in place did not resolve the issue as expected. Our Engineering team has identified and is currently working on a resolution. Our team is preparing for the deployment, which is expected to be completed within the next hour. If this changes, we will provide an update immediately.

6. 28 ianuarie 2026 la 04:49 UTCresolved

   This issue has been resolved.

1. 27 ianuarie 2026 la 00:03 UTCinvestigating

   We are currently investigating an issue affecting the Service Desk in the AU Data Center, where newly created objects, such as tickets and assets, are not appearing in the user interface as expected. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

2. 27 ianuarie 2026 la 01:23 UTCmonitoring

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

3. 27 ianuarie 2026 la 02:09 UTCresolved

   This incident has been resolved.

1. 12 ianuarie 2026 la 19:49 UTCinvestigating

   We are currently seeing performance slowness within the Service Desk Application, and our team is investigating this matter. This impacts actions such as navigating through the Incidents page and other areas of the app.

2. 12 ianuarie 2026 la 22:55 UTCinvestigating

   The platform performance has greatly improved, and while that is the case, we are still seeing delays, at times, when navigating between pages. The engineering team found a high load on the database, which has been cleared for a couple of hours, and are now focusing efforts on the remaining delay issues. You can expect the next update in one hour.

3. 13 ianuarie 2026 la 02:23 UTCresolved

   This issue has been resolved.

1. 12 ianuarie 2026 la 07:43 UTCinvestigating

   We are currently investigating an issue affecting the Service Desk in the AU Data Center. New tickets are not appearing in the UI. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

2. 12 ianuarie 2026 la 12:28 UTCresolved

   This issue has been resolved.

1. 9 ianuarie 2026 la 09:27 UTCinvestigating

   We are aware of an issue affecting a scheduled Service Desk service catalog item in our EU data center. Our team is actively working to identify the root cause and restore normal functionality. Additional updates will be shared as they become available.

2. 9 ianuarie 2026 la 09:36 UTCidentified

   Additional resources have been allocated to help manage the queue. As a result, the backlog is now being processed efficiently, and pending items are getting cleared. Additional updates will be shared as they become available.

3. 9 ianuarie 2026 la 10:09 UTCmonitoring

   Scheduled service catalog item are now being processed. We are monitoring the situation closely to ensure continued stability.

4. 9 ianuarie 2026 la 11:00 UTCresolved

   This incident has been resolved.

1. 6 ianuarie 2026 la 10:47 UTCinvestigating

   We are currently investigating an issue affecting Service Desk in EU Data Center. Round-robin assignment and Automation Rules process are delayed, this affects automation assigning and or updating incidents. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

2. 6 ianuarie 2026 la 11:14 UTCinvestigating

   We have identified performance degradation in the Service Desk application within EUDC. This issue is impacting multiple functionalities of the application. Our team is actively investigating the issue and working to identify the root cause. Further updates will be shared as more information becomes available.

3. 6 ianuarie 2026 la 14:32 UTCmonitoring

   Service Desk EU data-center degradation issue affecting the application has now been restored. System performance is now normal and the application is operating as expected. We continue to monitor performance closely to ensure ongoing stability and reliability.

4. 6 ianuarie 2026 la 17:59 UTCresolved

   This incident has been resolved.

1. 5 ianuarie 2026 la 13:35 UTCinvestigating

   We are currently investigating an issue affecting the Service Desk in our EU Data Center. The round-robin automatic assignment is not working as expected, and newly created tickets are not being assigned to a user or group automatically. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

2. 5 ianuarie 2026 la 16:13 UTCmonitoring

   A fix has been implemented. We will continue to monitor until we can confirm that no additional impact is expected.

3. 5 ianuarie 2026 la 19:13 UTCresolved

   This incident has been resolved.

1. 18 noiembrie 2025 la 13:32 UTCmonitoring

   We're currently experiencing an upstream vendor outage. This is affecting services, and you may see failures in items such as VA (Virtual Agent) functionality and custom domain routing. Our teams are monitoring the situation closely for updates.

2. 18 noiembrie 2025 la 14:16 UTCmonitoring

   Our upstream vendor are continue working on restoring service for application services.

3. 18 noiembrie 2025 la 15:33 UTCmonitoring

   Based on the recent update from our upstream vendor they have implemented a fix to resolve the issue. Our team is continuously monitoring for updates.

4. 18 noiembrie 2025 la 19:23 UTCmonitoring

   Our upstream vendor’s issue has been resolved, and we are no longer seeing any impact on our platform. We will continue to closely monitor the fix.

5. 18 noiembrie 2025 la 23:17 UTCresolved

   This issue has been resolved. Please contact us at [email protected] if you need further assistance.