Webroot driftsforstyrrelser

1. 9. september 2026 kl. 07.49 UTCinvestigating

   Frankfurt EU8 is currently experiencing service degradation with UCMDB service on EU8 farm. Clients may experience degradation while loading request entities or using an actual service on the EU8 farm. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3995249

2. 9. september 2026 kl. 08.13 UTCresolved

   Frankfurt EU8 experienced service degradation with UCMDB service on EU8 farm. The issue is now resolved. We appreciate your patience. Tracking Number: IM3995249

1. 31. august 2026 kl. 16.33 UTCinvestigating

   Microsoft O365 Exchange - some users are experiencing an issue connecting to Exchange 365. Microsoft is aware of the issue and has provided Issue ID: EX1464935.

2. 31. august 2026 kl. 16.57 UTCinvestigating

   Update from Microsoft: Microsoft isolated a common failure pattern across affected Exchange Online requests that is associated with authentication and protocol connectivity. They are analyzing service telemetry to identify the underlying source of impact and validate potential remediation options. Additionally, they are continuing to assess the scope of impact and monitor for additional affected scenarios. More info - Users may experience a variety of symptoms related to this event, including but not limited to: Delays or failures when sending or receiving email messages. Authentication-related errors when accessing Exchange Online services. Difficulties accessing or performing actions within Exchange administration experiences. Intermittent failures affecting mailbox operations and message delivery workflows.

3. 31. august 2026 kl. 17.51 UTCinvestigating

   Update from Microsoft: Microsoft has identified a potential corrective action for the affected infrastructure and are evaluating deployment options. They are monitoring service telemetry and affected Exchange Online transactions to determine whether the action is reducing impact and to better understand the scope of affected scenarios.

4. 31. august 2026 kl. 20.14 UTCinvestigating

   Update from Microsoft: Microsoft is continuing to perform comprehensive tests to ensure their mitigation strategy effectively resolves the issue without introducing additional impact. In parallel, they are exploring alternative remediation avenues to minimize impact in the interim.

5. 1. september 2026 kl. 12.26 UTCidentified

   Update from Microsoft: A substantial portion of the remediation deployment has been completed, and organizations whose environments remain affected are expected to recover as the deployment reaches the relevant infrastructure. As remediation progresses, Microsoft is focused on validating sustained recovery and monitoring for any remaining pockets of impact before determining whether any additional corrective actions are required.

6. 1. september 2026 kl. 17.07 UTCmonitoring

   Update from Microsoft: Microsoft observed continued recovery across previously impacted Exchange Online scenarios, with core mail flow functionality remaining healthy. Their focus remains on validating recovery across dependent Microsoft 365 experiences and confirming that remaining impact scenarios are fully addressed. They are maintaining enhanced monitoring while engineering teams complete end-to-end validation before determining whether any further corrective actions are required.

7. 1. september 2026 kl. 21.57 UTCmonitoring

   Update from Microsoft: Microsoft continues to advance multiple workstreams to restore service and prevent additional impact. Microsoft is prioritizing infrastructure that requires the most immediate attention while carefully expanding corrective actions across additional regions, with continued monitoring throughout this process. In parallel, Microsoft is investigating remaining reports of impact and evaluating additional actions to support full service recovery.

8. 2. september 2026 kl. 12.18 UTCmonitoring

   Update from Microsoft: Their telemetry indicates service availability remains stable above 99 percent and expect the majority of users should no longer be seeing impact from this issue. The continued focus is on balancing the implementation of their fixes across remaining portions of affected infrastructure to ensure persistent recovery, with added attention on ensuring withstanding recovery of scenarios dependent on REST and Graph API connection methods.

9. 3. september 2026 kl. 16.45 UTCmonitoring

   Update from Microsoft: Microsoft discovered an issue in less than one percent of their infrastructure, where additional mitigation efforts to resolve impact for Exchange Online did not successfully deploy. The vast majority of impact remains remediated; however, those serviced from the impacted portion of infrastructure may be unable to access previously recovered Outlook connection methods. Microsoft remains committed to restoring all services to all users and will continue to carefully monitor their telemetry to ensure recovery.

10. 3. september 2026 kl. 18.33 UTCmonitoring

    Update from Microsoft: All user impact scenarios are now resolved as they rectified the additional mitigation efforts for the Outlook impact which occurred in less than one percent of their infrastructure. They will continue to monitor their telemetry to ensure all services remain healthy and plan to close this communication by next update.

11. 4. september 2026 kl. 12.22 UTCresolved

    This incident has been resolved.

1. 28. august 2026 kl. 17.16 UTCinvestigating

   Desktop Messaging BMS is currently experiencing delays in processing outbound fax delivery. Document backlogs exist and are currently being processed. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3987893

2. 28. august 2026 kl. 17.58 UTCresolved

   Desktop Messaging BMS experienced delays in processing outbound fax delivery. Backlogs have been cleared, and the issue is now resolved. We appreciate your patience. Tracking Number: IM3987893

1. 28. august 2026 kl. 02.42 UTCinvestigating

   Core Communications Europe is currently unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3987509

2. 28. august 2026 kl. 03.13 UTCmonitoring

   Core Communications Europe was unavailable. Teams are currently assembled and working to resolve the issue. Service has been restored and is being validated. We appreciate your patience. Tracking Number: IM3987509

3. 28. august 2026 kl. 03.24 UTCresolved

   Core Communications Europe was unavailable. The issue is now resolved. We appreciate your patience. Tracking Number: IM3987509

1. 26. august 2026 kl. 14.12 UTCinvestigating

   MailStore Cloud is currently unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience.

2. 26. august 2026 kl. 15.05 UTCmonitoring

   MailStore Cloud was unavailable. Service has been restored and is being validated. We appreciate your patience.

3. 26. august 2026 kl. 15.57 UTCresolved

   MailStore Cloud was unavailable. The issue is now resolved. We appreciate your patience.

1. 22. august 2026 kl. 03.41 UTCinvestigating

   Core EDR/MDR in the US region is currently experiencing service degradation. Teams are currently assembled and working to resolve the issue. We appreciate your patience.

2. 22. august 2026 kl. 04.41 UTCinvestigating

   Core EDR/MDR in the US region is currently experiencing service degradation. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first.

3. 22. august 2026 kl. 06.41 UTCinvestigating

   Core EDR/MDR in the US region is currently experiencing service degradation. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Updates for this issue will be posted as soon as there are significant updates.

4. 24. august 2026 kl. 13.18 UTCresolved

   Core EDR/MDR in the US region experienced service degradation. The issue has been resolved. We appreciate your patience.

1. 20. august 2026 kl. 15.54 UTCidentified

   Core EDR/MDR is currently experiencing service degradation. Agents that were upgraded to version 3.3.0 from an earlier version may experience issues preventing remote uninstallations from completing successfully. New installations of version 3.3.0 are not impacted. Teams have identified that the issue only affects the Windows OS and are working to resolve it. We appreciate your patience. If agent removal is required, please follow the steps outlined in our Knowledge Base article for manual agent uninstallation, which remains effective for affected endpoints: https://help.pillrplatform.com/faq/uninstall.html

2. 20. august 2026 kl. 17.55 UTCidentified

   Core EDR/MDR is currently experiencing service degradation. Agents that were upgraded to version 3.3.0 from an earlier version may experience issues preventing remote uninstallations from completing successfully. New installations of version 3.3.0 are not impacted. Teams have identified that the issue affects only the Windows OS and are working to resolve it. We appreciate your patience. If agent removal is required, please follow the steps outlined in our Knowledge Base article for manual agent uninstallation, which remains effective for affected endpoints: https://help.pillrplatform.com/faq/uninstall.html

3. 20. august 2026 kl. 22.58 UTCidentified

   Core EDR/MDR is currently experiencing service degradation. Agents that were upgraded to version 3.3.0 from an earlier version may experience issues preventing remote uninstallations from completing successfully. New installations of version 3.3.0 are not impacted. Teams have identified that the issue affects only the Windows OS and are working to resolve it. If agent removal is required, please follow the steps outlined in our Knowledge Base article for manual agent uninstallation, which remains effective for affected endpoints: https://help.pillrplatform.com/faq/uninstall.html Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first. We appreciate your patience.

4. 20. august 2026 kl. 23.42 UTCmonitoring

   Core EDR/MDR experienced service degradation. Service has been restored in agent version 3.3.2, which is now GA. For customers still on version 3.3.0, a manual upgrade can be triggered through the Action System before proceeding with the uninstall.

5. 21. august 2026 kl. 01.45 UTCresolved

   Core EDR/MDR experienced service degradation. The issue is now resolved. We appreciate your patience.

1. 13. august 2026 kl. 18.36 UTCinvestigating

   Secure Cloud Portal is currently experiencing an issue with Microsoft 365 license assignments. Our teams are actively investigating and working to restore normal functionality as quickly as possible. We appreciate your patience and understanding while we work toward a resolution. Workaround: After updating license counts in the Secure Cloud Portal, please sign in to the customer's Microsoft 365 Admin Center and assign licenses to users directly within the Microsoft 365 tenant. Tracking Number: IM3979306

2. 14. august 2026 kl. 16.24 UTCresolved

   This incident has been resolved.

1. 13. august 2026 kl. 15.09 UTCinvestigating

   Cloud Fax services is currently experiencing delays in processing of fax files. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Desktop Messaging BMS Tracking Number: IM3978817

2. 13. august 2026 kl. 16.15 UTCinvestigating

   Desktop Messaging BMS is experiencing delays in processing fax files. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3978817

3. 13. august 2026 kl. 17.02 UTCresolved

   Desktop Messaging BMS experienced delays in processing fax files. The issue is now resolved. We appreciate your patience. Tracking Number: IM3978817

1. 9. august 2026 kl. 09.06 UTCinvestigating

   Enterprise Service Management hosted under the saas.microfocus.com domain may currently experience issues accessing their applications. Teams are assembled and working to resolve the issue. We appreciate your patience Tracking Number: IM3976323

2. 9. august 2026 kl. 09.06 UTCinvestigating

   We are continuing to investigate this issue.

3. 9. august 2026 kl. 10.13 UTCinvestigating

   Enterprise Service Management hosted under the saas.microfocus.com domain may currently experience issues accessing their applications. Teams are assembled and working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first Tracking Number: IM3976323

4. 9. august 2026 kl. 12.17 UTCmonitoring

   Enterprise Service Management hosted under the saas.microfocus.com domain may currently experience issues accessing their applications. A fix has been implemented and we are monitoring the results. We appreciate your patience. Tracking Number: IM3976323

5. 9. august 2026 kl. 14.34 UTCmonitoring

   Enterprise Service Management hosted under the saas.microfocus.com domain may currently experience issues accessing their applications. A fix has been implemented, and we are monitoring the results. We appreciate your patience. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first. Tracking Number: IM3976323

6. 10. august 2026 kl. 00.33 UTCmonitoring

   Enterprise Service Management hosted under the saas.microfocus.com domain might have experienced issues accessing their applications. A fix has been implemented, and we are monitoring the results. We appreciate your patience. Updates for this issue will be sent every 8 hours or if there are significant updates, whichever comes first. Tracking Number: IM3976323

7. 10. august 2026 kl. 01.17 UTCresolved

   Enterprise Service Management hosted under the saas.microfocus.com domain might have experienced issues accessing their applications. The issue is now resolved. We appreciate your patience. Tracking Number: IM3976323

8. 13. august 2026 kl. 19.01 UTCpostmortem

   **Root Cause Analysis** **Tracking number:** IM3976323 PM1011709 **Incident window:** August 9, 2026, from 01:00 GMT to 11:35 GMT **Services affected:** OpenText™ Shared Network Services **Overview** On August 9, 2026, at 06:24 GMT, Incident Management was engaged to investigate client-reported access issues affecting multiple OpenText SaaS services. **Impact** Clients were unable to access the OpenText SaaS services. **Root Cause** The investigation determined that a Domain Name System Security Extensions \(DNSSEC\) Key Signing Key \(KSK\) expired for the [microfocus.com](http://microfocus.com) DNS zone, resulting in DNS resolution failures across multiple services. This condition disrupted DNS resolution across multiple DNSSEC-enabled subzones, including [saas.microfocus.com](http://saas.microfocus.com), resulting in service inaccessibility. Furthermore, downstream propagation timelines and varying client-side caching behaviors extended recovery durations for a subset of endpoints. **Resolution** To mitigate the issue, the team implemented a configuration change to generate and apply new DNSSEC signing keys. The existing DNS signatures were removed, and the [microfocus.com](http://microfocus.com) DNS zone was re-signed using the newly generated keys. Following the configuration change, validation activities were completed successfully, and service was restored at 11:35 GMT, ending the impact. Note: Some clients may have continued to experience name-resolution issues due to stale DNS records cached within their internal DNS infrastructure, proxy servers, or firewall appliances. These issues should resolve once the cached DNS records expired or refreshed. **Action Plan** PM1011709-003: Review and optimize DNSSEC KSK alert triggers. - In progress - Target complete: August 14, 2026 PM1011709-004: Implement proactive internal monitoring and automated alert generation for DNSSEC key rollovers. - In progress - Target complete: September 4, 2026 PM1011709-006: Review incident escalation procedures to optimize the process. - In progress - Target complete: September 4, 2026 PM1011709-007: Evaluate external accessibility monitoring capabilities for critical application endpoints. - In progress - Target complete: September 4, 2026

1. 8. august 2026 kl. 15.05 UTCinvestigating

   Investigating: We are currently experiencing an issue in the CP Portal where users may encounter an "Unknown Error" message. Our Engineering team is actively investigating the issue and working toward a resolution. We will provide further updates as more information becomes available. Tracking Number - IM3976014

2. 8. august 2026 kl. 20.03 UTCmonitoring

   The issue affecting the CP Portal, where users may have encountered an "Unknown Error" message, has been identified and resolved by our Backend Engineering team. The fix has been successfully implemented, and services are operating as expected. We are currently monitoring the environment to ensure stability and confirm that the issue does not recur. We will continue to provide updates as needed. Tracking Number - IM3976014

3. 10. august 2026 kl. 12.58 UTCresolved

   The issue affecting the CP Portal, where users may have encountered an "Unknown Error" message, has been identified and resolved by our Backend Engineering team. The fix has been successfully implemented, and services are now operating as expected. Tracking Number - IM3976014

1. 7. august 2026 kl. 17.59 UTCinvestigating

   Secure Cloud Portal (cp.appriver.com) is currently experiencing an issue with Microsoft 365 license changes. Teams are currently assembled and working to resolve the issue. We appreciate your patience. If you need any 365 license changes, please email [email protected] to create a ticket for processing. Tracking Number: IM397569

2. 7. august 2026 kl. 20.14 UTCmonitoring

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

3. 13. august 2026 kl. 18.25 UTCresolved

   This incident has been resolved.

1. 6. august 2026 kl. 17.18 UTCinvestigating

   Zix Encryption Services - Secure Cloud Email Encryption AEE DLP is currently experiencing an issue requiring the sender of an email to log in to an interface to release messages from DLP. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3975128

2. 6. august 2026 kl. 21.14 UTCmonitoring

   Zix Encryption Services - Secure Cloud Email Encryption AEE DLP experienced an issue requiring the sender of an email to log in to an interface to release messages from DLP. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3975128

3. 7. august 2026 kl. 12.56 UTCresolved

   Zix Encryption Services - Secure Cloud Email Encryption AEE DLP experienced an issue requiring the sender of an email to log in to an interface to release messages from DLP. The issue is now resolved. We appreciate your patience. Tracking Number: IM3975128

1. 3. august 2026 kl. 22.28 UTCidentified

   Core EDR / MDR oplever i øjeblikket forringelse af tjenesten. Agent installer downloads kan ikke fungere som forventet. Holdene har identificeret årsagen og arbejder på en resolution. Vi sætter pris på din tålmodighed. Hvis du har spørgsmål eller bekymringer, bedes du kontakte supportholdet.

2. 3. august 2026 kl. 23.28 UTCidentified

   Core EDR / MDR oplever i øjeblikket forringelse af tjenesten. Agent installer downloads kan ikke fungere som forventet. Holdene har identificeret årsagen og arbejder på en resolution. Vi sætter pris på din tålmodighed. Opdateringer til dette nummer vil blive sendt hver 2. time, eller hvis der er væsentlige opdateringer, alt efter hvad der kommer først. Hvis du har spørgsmål eller bekymringer, bedes du kontakte supportholdet.

3. 4. august 2026 kl. 00.54 UTCmonitoring

   Kernen EDR / MDR oplevede forringelse af tjenesten. Tjenesten er blevet genoprettet og valideres nu. Vi sætter pris på din tålmodighed. Opdateringer til dette nummer vil blive sendt hver 2. time, eller hvis der er væsentlige opdateringer, alt efter hvad der kommer først. Hvis du har spørgsmål eller bekymringer, bedes du kontakte supportholdet.

4. 4. august 2026 kl. 02.51 UTCresolved

   Kernen EDR / MDR oplevede forringelse af tjenesten. Spørgsmålet er nu løst. Vi sætter pris på din tålmodighed.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 31. juli 2026 kl. 14.29 UTCinvestigating

   Følgende tjenester oplever et problem med TLS-forbindelser til Googleejede servere. Holdene samles i øjeblikket og arbejder på at løse problemet. Vi sætter pris på din tålmodighed. - Zix Encryption Services - Hosted SMB - Zix Encryption Services - Secure Cloud Email Encryption (AEE / ZEE) - Zix Encryption Services - ZixGateway (Hosted) Sporingsnummer: IM3971825

2. 31. juli 2026 kl. 14.37 UTCinvestigating

   Følgende tjenester oplever et problem med TLS-forbindelser til flere eksterne mailtjenester. Holdene samles i øjeblikket og arbejder på at løse problemet. Vi sætter pris på din tålmodighed. - Zix Encryption Services - Hosted SMB - Zix Encryption Services - Secure Cloud Email Encryption (AEE / ZEE) - Zix Encryption Services - ZixGateway (Hosted) Sporingsnummer: IM3971825

3. 31. juli 2026 kl. 14.45 UTCinvestigating

   Følgende tjenester oplever et problem med TLS-forbindelser til flere eksterne mailtjenester. Holdene samles i øjeblikket og arbejder på at løse problemet. Vi sætter pris på din tålmodighed. - Zix Encryption Services - Hosted SMB - Zix Encryption Services - Secure Cloud Email Encryption (AEE / ZEE) - Zix Encryption Services - ZixGateway (Hosted) - Zix Treat Protection Services - ZixProtect Sporingsnummer: IM3971825

4. 31. juli 2026 kl. 14.57 UTCmonitoring

   Følgende tjenester oplever et problem med TLS-forbindelser til flere eksterne mailtjenester. Tjenesten er blevet genoprettet og valideres nu. Vi sætter pris på din tålmodighed. - Zix Encryption Services - Hosted SMB - Zix Encryption Services - Secure Cloud Email Encryption (AEE / ZEE) - Zix Encryption Services - ZixGateway (Hosted) - Zix Treat Protection Services - ZixProtect Sporingsnummer: IM3971825

5. 31. juli 2026 kl. 17.35 UTCresolved

   Følgende tjenester oplever et problem med TLS-forbindelser til flere eksterne mailtjenester. - Zix Encryption Services - Hosted SMB - Zix Encryption Services - Secure Cloud Email Encryption (AEE / ZEE) - Zix Encryption Services - ZixGateway (Hosted) - Zix Treat Protection Services - ZixProtect Spørgsmålet er nu løst. Vi sætter pris på din tålmodighed. Sporingsnummer: IM3971825

Automatisk oversat fra den officielle hændelsesopdatering.

1. 31. juli 2026 kl. 04.43 UTCresolved

   São Paulo BR14 oplevede funktionsnedsættelse og funktionsforringelse i drift. Spørgsmålet er nu løst. Vi sætter pris på din tålmodighed. Sporingsnummer: IM3971517

2. 31. juli 2026 kl. 13.47 UTCpostmortem

   * * Foreløbig rodårsag * * * * Sporingsnummer: * * IM3971517 PM 1011702 * * Tilfælde vindue: * * 31 juli 2026, fra 03: 32 GMT til 04: 42 GMT den 30 juli 226 * * Berørte tjenester: * * OpenText ™ Enterprise Service Management\ (ESM BR14\) * * Oversigt * * Den 31. juli 2026, kl. 04: 10 GMT, Incident Management blev engageret til at undersøge forringet systemets ydeevne på OpenText ™ Enterprise Service Management\ (ESM BR14\) miljøet. * * Indvirkning * * Brugerne oplevede problemer med forringet systemydeevne og funktionalitet. * * Rodårsag * * Undersøgelsen afslørede intermitterende forbindelsesfejl mellem RabbitMQ-klyngen og afhængige anvendelseskomponenter. RabbitMQ, som fungerer som en multinode grupperet tjeneste, der letter kommunikationen mellem kernemotoren og andre komponenter, undlod automatisk at genetablere forbindelse i visse tilfælde, hvilket nødvendiggjorde en klyngegenopbygning. Den grundlæggende årsag analyse identificeret to primære medvirkende faktorer: • RabbitMQ Metadata Store Instabilitet: En ustabilitet i RabbitMQ Metadata butik forårsaget uoverensstemmelser i kø metadata, hvilket resulterer i messaging forstyrrelser på tværs af platformen. • Tilslutning Inddrivelse Fejl: Visse applikationstjenester var ude af stand til automatisk at genetablere stabile RabbitMQ-forbindelser efter svigt, hvilket førte til forringet platform ydeevne og funktionalitet. * * Opløsning * * RabbitMQ service blev genopbygget, genoprette service på 04: 24 GMT. Valideringsaktiviteterne efter restaurering blev afsluttet med succes kl. 04: 42 GMT, hvorved virkningen blev bragt til ophør. * * Handlingsplan * * Engineering teams fortsætter med at undersøge den underliggende årsag til denne hændelse og identificere yderligere korrigerende og forebyggende foranstaltninger for at reducere risikoen for gentagelse. Som en del af oprydningsindsatsen er der iværksat et langsigtet stabilitetsprogram for at styrke RabbitMQ 's modstandsdygtighed, styrke applikationstilslutning genoprettelsesmekanismer og udvide proaktiv overvågning og varsling kapaciteter. Disse forbedringer, sammen med forbedringer planlagt for Release 26.3.1, forventes yderligere at forbedre systemets stabilitet og væsentligt reducere sandsynligheden for lignende hændelser i fremtiden.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 28. juli 2026 kl. 17.31 UTCidentified

   Vi er i øjeblikket ved at undersøge rapporter af partnere forkert autentificering gennem Kundeportalen med forkerte log ins. Vores team er aktivt i gang med dette spørgsmål nu. Hændelse: IM3969646

2. 28. juli 2026 kl. 17.38 UTCmonitoring

   Vi har med succes startet en rollback, der forårsagede denne godkendelse problem og har bekræftet, at problemet ikke længere er ouccring. Vi fortsætter med aktivt at overvåge vores logfiler for at sikre, at alt er fuldt operationelt. Hændelse: IM3969646

3. 29. juli 2026 kl. 17.38 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 27. juli 2026 kl. 15.22 UTCinvestigating

   Oregon US6 oplever i øjeblikket intermitterende service manglende tilgængelighed. Holdene samles i øjeblikket og arbejder på at løse problemet. Vi sætter pris på din tålmodighed. Sporingsnummer: IM3968671

2. 27. juli 2026 kl. 15.54 UTCresolved

   Oregon US6 oplevede intermitterende service manglende tilgængelighed. Spørgsmålet er nu løst. Vi sætter pris på din tålmodighed. Sporingsnummer: IM3968671

3. 29. juli 2026 kl. 17.30 UTCpostmortem

   * * Foreløbig rodårsag * * * * Sporingsnummer: * * IM3968671 PM 1011655 * * Tilfælde vinduer: * * 27 juli 2026, fra 13: 28 GMT til 14: 15 GMT * * Berørte tjenester: * * OpenText ™ Enterprise Service Management\ (ESM US6\) * * Oversigt * * Den 27. juli 2026, kl 14: 11 GMT, Incident Management blev engageret til at undersøge intermitterende tilgængelighed og performance nedbrydning i US6 miljøet. * * Indvirkning * * Klienter oplevede forringet service ydeevne, hvilket resulterer i langsom brugergrænseflade\ (UI\) svartider. * * Rodårsag * * Den grundlæggende årsag analyse identificeret to primære medvirkende faktorer: • RabbitMQ Metadata Store Instabilitet: En ustabilitet i RabbitMQ Metadata butik forårsaget uoverensstemmelser i kø metadata, hvilket resulterer i messaging forstyrrelser på tværs af platformen. • Tilslutning Inddrivelse Fejl: Visse applikationstjenester var ude af stand til automatisk at genetablere stabile RabbitMQ-forbindelser efter svigt, hvilket førte til forringet platform ydeevne og funktionalitet. * * Opløsning * * Undersøgelsen viste, at utilstrækkelig replikakapacitet i Gateway og Platform-tjenester påvirkede tjenesternes ydeevne. Antallet af kopier for begge tjenester blev øget, og tjenesten blev genoprettet. Hele valideringen blev afsluttet med 14: 15 GMT, som afslutter virkningen. * * Handlingsplan * * Engineering teams fortsætter med at undersøge den underliggende årsag til denne hændelse og identificere yderligere korrigerende og forebyggende foranstaltninger for at reducere risikoen for gentagelse. Som en del af oprydningsindsatsen er der iværksat et langsigtet stabilitetsprogram for at styrke RabbitMQ 's modstandsdygtighed, styrke applikationstilslutning genoprettelsesmekanismer og udvide proaktiv overvågning og varsling kapaciteter. Disse forbedringer, sammen med forbedringer planlagt for Release 26.3.1, forventes yderligere at forbedre systemets stabilitet og væsentligt reducere sandsynligheden for lignende hændelser i fremtiden. OpenText tog følgende handlinger og vil afgøre yderligere forebyggende handlinger efter behov. • Gennemført statisk pod tildeling til RabbitMQ, erstatter dynamisk tildeling for at reducere risikoen for pod contention. - * * COMPLETE * * • Forhøjede CPU-ressourcer tildelt RabbitMQ-kapsler for at mindske flaskehalse og forbedre den overordnede systemstabilitet. - * * COMPLETE * *

Automatisk oversat fra den officielle hændelsesopdatering.

1. 27. juli 2026 kl. 09.03 UTCinvestigating

   Frankfurt EU8 oplever i øjeblikket intermitterende servicefravær. Holdene samles i øjeblikket og arbejder på at løse problemet. Vi sætter pris på din tålmodighed. Sporingsnummer: IM3968415

2. 27. juli 2026 kl. 10.54 UTCmonitoring

   Frankfurt EU8 oplevede intermitterende service manglende tilgængelighed. Tjenesten er blevet genoprettet og valideres nu. Vi sætter pris på din tålmodighed. Sporingsnummer: IM3968415

3. 27. juli 2026 kl. 11.42 UTCresolved

   Frankfurt EU8 oplevede intermitterende service manglende tilgængelighed. Spørgsmålet er nu løst. Vi sætter pris på din tålmodighed. Sporingsnummer: IM3968415

4. 29. juli 2026 kl. 14.26 UTCpostmortem

   * * Foreløbig rodårsag * * * * Sporingsnummer: * * IM3968415 PM 1011655 * * Tilfælde vinduer: * * 27 juli 2026, fra 06: 31 GMT til 09: 41 GMT * * Berørte tjenester: * * OpenText ™ Enterprise Service Management\ (ESM EU8\) * * Oversigt * * Den 27. juli 2026, på 07: 10 GMT, Incident Management blev engageret til at undersøge intermitterende adgang spørgsmål og service manglende tilgængelighed. * * Indvirkning * * Flere kunder oplevede intermitterende adgangsproblemer og service manglende tilgængelighed på tværs af ESM EU8 miljøet. * * Rodårsag * * Den grundlæggende årsag analyse identificeret to primære medvirkende faktorer: • RabbitMQ Metadata Store Instabilitet: En ustabilitet i RabbitMQ Metadata butik forårsaget uoverensstemmelser i kø metadata, hvilket resulterer i messaging forstyrrelser på tværs af platformen. • Tilslutning Inddrivelse Fejl: Visse applikationstjenester var ude af stand til automatisk at genetablere stabile RabbitMQ-forbindelser efter svigt, hvilket førte til forringet platform ydeevne og funktionalitet. * * Opløsning * * CPU-tildelingen blev øget, og RabbitMQ-køerne blev genbalanceret for at forbedre systemets stabilitet og ydeevne. Systematisk genstart af platformskapslerne blev afsluttet kl. 07: 56 GMT, som genoprettede kernetjenesterne. Men SLT-tjenesten fortsatte med at opleve problemer. Klyngen blev genopbygget, og tjenesterne normaliseret kl. 09: 41 GMT. Yderligere manuel kontrol blev gennemført på tværs af miljøet for at rydde falske nedbrydningsindberetninger, og der blev ikke observeret yderligere problemer. Valideringer blev afsluttet kl 11: 38 GMT, slutter virkningen. * * Handlingsplan * * Engineering teams fortsætter med at undersøge den underliggende årsag til denne hændelse og identificere yderligere korrigerende og forebyggende foranstaltninger for at reducere risikoen for gentagelse. Som en del af oprydningsindsatsen er der iværksat et langsigtet stabilitetsprogram for at styrke RabbitMQ 's modstandsdygtighed, styrke applikationstilslutning genoprettelsesmekanismer og udvide proaktiv overvågning og varsling kapaciteter. Disse forbedringer, sammen med forbedringer planlagt for Release 26.3.1, forventes yderligere at forbedre systemets stabilitet og væsentligt reducere sandsynligheden for lignende hændelser i fremtiden. OpenText tog følgende handlinger og vil afgøre yderligere forebyggende handlinger efter behov. • Gennemført statisk pod tildeling til RabbitMQ, erstatter dynamisk tildeling for at reducere risikoen for pod contention. - * * COMPLETE * * • Forhøjede CPU-ressourcer tildelt RabbitMQ-kapsler for at mindske flaskehalse og forbedre den overordnede systemstabilitet. - * * COMPLETE * *

Automatisk oversat fra den officielle hændelsesopdatering.

1. 27. juli 2026 kl. 07.17 UTCinvestigating

   Frankfurt EU8 oplever i øjeblikket intermitterende servicefravær. Holdene samles i øjeblikket og arbejder på at løse problemet. Vi sætter pris på din tålmodighed. Sporingsnummer: IM3968415

2. 27. juli 2026 kl. 08.19 UTCresolved

   Frankfurt EU8 oplever i øjeblikket intermitterende servicefravær. Holdene samles i øjeblikket og arbejder på at løse problemet. Vi sætter pris på din tålmodighed. Sporingsnummer: IM3968415

Automatisk oversat fra den officielle hændelsesopdatering.