Anaplan driftsforstyrrelser

1. 7. september 2026 kl. 13.26 UTCinvestigating

   Vi undersøger i øjeblikket et problem, der påvirker kundernes evne til at få adgang til Anaplan Platform. Vi arbejder på at løse dette problem så hurtigt som muligt og vil levere opdateringer hvert 30. minut eller efter resolution.

2. 7. september 2026 kl. 13.33 UTCinvestigating

   Vi har identificeret den sandsynlige årsag til problemet, og vi fokuserer lige nu på at genoprette tjenesten så hurtigt som muligt. I øjeblikket har vi endnu ikke tid til at tage stilling. Vi vil levere yderligere opdateringer om 30 minutter eller efter opløsning.

3. 7. september 2026 kl. 13.35 UTCmonitoring

   Service er nu blevet genoprettet; du bør nu være i stand til at genoptage normale aktiviteter. Vi vil fortsat overvåge platformen for at sikre, at der ikke opstår yderligere problemer. Hvis du har spørgsmål, bekymringer eller fortsætter med at opleve problemer, skal du ikke tøve med at kontakte Anaplan Support. Vi vil give dig en endelig opdatering, når vi overvejer denne situation helt løst.

4. 7. september 2026 kl. 13.46 UTCresolved

   Vi har bekræftet, at spørgsmålet nu er løst. Vi undskylder dybt for eventuelle konsekvenser af dette spørgsmål. Vi sætter pris på Deres tålmodighed og partnerskab, da vi arbejdede os igennem dette spørgsmål. Vi vil følge op inden for 7 hverdage med en detaljeret rod årsag analyse (RCA), der vil blive delt på vores status side. Hvis du har spørgsmål eller bekymringer, så tøv ikke med at kontakte os på Anaplan Support.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 3. september 2026 kl. 14.56 UTCinvestigating

   Vi undersøger i øjeblikket et problem, der påvirker kundernes evne til at få adgang til Anaplan Platform. Vi arbejder på at løse dette problem så hurtigt som muligt og vil levere opdateringer hvert 30. minut eller efter resolution.

2. 3. september 2026 kl. 15.12 UTCidentified

   Vi har identificeret den sandsynlige årsag til problemet, og vi fokuserer lige nu på at genoprette tjenesten så hurtigt som muligt. I øjeblikket har vi endnu ikke tid til at tage stilling. Vi vil levere yderligere opdateringer om 30 minutter eller efter opløsning.

3. 3. september 2026 kl. 15.16 UTCmonitoring

   Service er nu blevet genoprettet; du bør nu være i stand til at genoptage normale aktiviteter. Vi vil fortsat overvåge platformen for at sikre, at der ikke opstår yderligere problemer. Hvis du har spørgsmål, bekymringer eller fortsætter med at opleve problemer, skal du ikke tøve med at kontakte Anaplan Support. Vi vil give dig en endelig opdatering, når vi overvejer denne situation helt løst.

4. 3. september 2026 kl. 18.04 UTCresolved

   Vi har bekræftet, at spørgsmålet nu er løst. Vi undskylder dybt for eventuelle konsekvenser af dette spørgsmål. Vi sætter pris på Deres tålmodighed og partnerskab, da vi arbejdede os igennem dette spørgsmål. Vi vil følge op inden for 7 hverdage med en detaljeret rod årsag analyse (RCA), der vil blive delt på vores status side. Hvis du har spørgsmål eller bekymringer, så tøv ikke med at kontakte os på Anaplan Support.

5. 9. september 2026 kl. 08.38 UTCpostmortem

   * * Indledning * * Den 3. september 2026, fra 14: 51 UTC til 16: 17 UTC, in1: Cloud - Indien regionen var ikke tilgængelig. I denne periode var kunderne ude af stand til at få adgang til eller navigere rundt på platformen. * * Rodårsag * * Den 3. september 2026, under en planlagt fornyelse af sikkerhedscertifikater for vores tjenester i Indien region, blev der anvendt en ufuldstændig certifikat bundt. Dette forårsagede autentificering og validering tjenester til at være ude af stand til at kontrollere den sikre forbindelse, hvilket resulterede i platformen er utilgængelige. * * Inddrivelse * * Vores ingeniørhold identificerede problemet og greb straks ind. Vi vendte den brugerdefinerede konfiguration tilbage til platformens forvaltede sikre certificeringstjeneste, som med succes genoprettede forbindelsen validering. Ved 16: 17 UTC blev problemet løst fuldt ud. * * Korrigerende og forebyggende foranstaltninger * * Vi gennemfører følgende foranstaltninger for at forhindre gentagelse: * Vi udfører en grundig revision af alle sikkerhedscertifikater i vores miljøer for at optimere og standardisere vores konfigurationsadministration. * Vi skifter til forvaltede certificeringstjenester for at minimere manuelle konfigurationskrav. * Vi er ved at implementere automatiserede full-chain validering kontroller for alle fremtidige sikkerhedscertifikater opdateringer for at sikre fuldstændig integritet før implementering. Vi undskylder for enhver indvirkning på din forretning. Vi styrker løbende vores systemer og procedurer for at sikre, at vi undgår fremtidige forstyrrelser af din virksomhed og brugere. Hvis du har yderligere spørgsmål eller bekymringer, kan du besøge vores [Support website] (https: / / www.google.com / url? q = https% 3A% 2F% 2Fsupport.anaplan.com% 2F). Vi værdsætter din tålmodighed under denne hændelse og værdsætter den tillid, du placerer i Anaplan.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 1. september 2026 kl. 09.49 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem, der påvirker kundernes evne til at køre Cloudworks integration. Vi arbejder på at løse dette problem så hurtigt som muligt og vil levere opdateringer hvert 30. minut eller efter resolution.

2. 1. september 2026 kl. 10.25 UTCinvestigating

   Tak for Deres tålmodighed, når vi fortsætter med at undersøge dette spørgsmål. I øjeblikket har vi endnu ikke tid til at tage stilling. Vi vil fortsætte med at levere opdateringer hvert halve minut, når vi arbejder på at løse dette problem så hurtigt som muligt.

3. 1. september 2026 kl. 11.06 UTCinvestigating

   Tak for Deres fortsatte tålmodighed, mens vi undersøger dette spørgsmål. Vi har bekræftet et problem, der påvirker CloudWorks integration på tværs af flere regioner. Det er fortsat en topprioritet, og vi har endnu ikke et anslået tidspunkt til løsning. Vi vil fortsætte med at dele opdateringer hvert halve minut, når vi arbejder på at løse dette så hurtigt som muligt.

4. 1. september 2026 kl. 11.45 UTCidentified

   Tak for Deres fortsatte tålmodighed, mens vi undersøger dette spørgsmål. Vi har observeret CloudWorks-integration, der starter og fuldfører med succes på tværs af alle regioner, men vi fortsætter med at overvåge situationen nøje. Vi vil dele yderligere opdateringer hvert halve minut, når vi arbejder på at løse dette så hurtigt som muligt.

5. 1. september 2026 kl. 12.19 UTCmonitoring

   Service er nu blevet genoprettet; du bør nu være i stand til at genoptage normale aktiviteter. Vi vil fortsat overvåge platformen for at sikre, at der ikke opstår yderligere problemer. Hvis du har spørgsmål, bekymringer eller fortsætter med at opleve problemer, skal du ikke tøve med at kontakte Anaplan Support. Vi vil give dig en endelig opdatering, når vi overvejer denne situation helt løst.

6. 1. september 2026 kl. 12.42 UTCresolved

   Vi har bekræftet, at spørgsmålet nu er løst. Vi undskylder dybt for eventuelle konsekvenser af dette spørgsmål. Vi sætter pris på Deres tålmodighed og partnerskab, da vi arbejdede os igennem dette spørgsmål. Vi vil følge op inden for 7 hverdage med en detaljeret rod årsag analyse (RCA), der vil blive delt på vores status side. Hvis du har spørgsmål eller bekymringer, så tøv ikke med at kontakte os på Anaplan Support.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 1. september 2026 kl. 09.10 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem, der påvirker kundernes evne til at køre Cloudworks integration. Vi arbejder på at løse dette problem så hurtigt som muligt og vil levere opdateringer hvert 30. minut eller efter resolution.

2. 1. september 2026 kl. 09.28 UTCmonitoring

   Service er nu blevet genoprettet; du bør nu være i stand til at genoptage normale aktiviteter. Vi vil fortsat overvåge platformen for at sikre, at der ikke opstår yderligere problemer. Hvis du har spørgsmål, bekymringer eller fortsætter med at opleve problemer, skal du ikke tøve med at kontakte Anaplan Support. Vi vil give dig en endelig opdatering, når vi overvejer denne situation helt løst.

3. 1. september 2026 kl. 09.47 UTCresolved

   Vi har bekræftet, at spørgsmålet nu er løst. Vi undskylder dybt for eventuelle konsekvenser af dette spørgsmål. Vi sætter pris på Deres tålmodighed og partnerskab, da vi arbejdede os igennem dette spørgsmål. Vi vil følge op inden for 7 hverdage med en detaljeret rod årsag analyse (RCA), der vil blive delt på vores status side. Hvis du har spørgsmål eller bekymringer, så tøv ikke med at kontakte os på Anaplan Support.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 27. august 2026 kl. 10.22 UTCinvestigating

   Vi undersøger i øjeblikket et problem, der påvirker kundernes evne til at få adgang til Anaplan Platform i Canada. Vi arbejder på at løse dette problem så hurtigt som muligt og vil levere opdateringer hvert 30. minut eller efter resolution.

2. 27. august 2026 kl. 10.52 UTCinvestigating

   Tak for Deres tålmodighed, når vi fortsætter med at undersøge dette spørgsmål. I øjeblikket har vi endnu ikke tid til at tage stilling. Vi vil fortsætte med at levere opdateringer hvert halve minut, når vi arbejder på at løse dette problem så hurtigt som muligt.

3. 27. august 2026 kl. 10.57 UTCidentified

   Vi har identificeret den sandsynlige årsag til problemet, og vi fokuserer lige nu på at genoprette tjenesten så hurtigt som muligt. I øjeblikket vil vi levere yderligere opdateringer om 30 minutter eller efter opløsning.

4. 27. august 2026 kl. 10.58 UTCmonitoring

   Service er nu blevet genoprettet; du bør nu være i stand til at genoptage normale aktiviteter. Vi vil fortsat overvåge platformen for at sikre, at der ikke opstår yderligere problemer. Hvis du har spørgsmål, bekymringer eller fortsætter med at opleve problemer, skal du ikke tøve med at kontakte Anaplan Support. Vi vil give dig en endelig opdatering, når vi overvejer denne situation helt løst.

5. 27. august 2026 kl. 11.08 UTCresolved

   Vi har bekræftet, at spørgsmålet nu er løst. Vi undskylder dybt for eventuelle konsekvenser af dette spørgsmål. Vi sætter pris på Deres tålmodighed og partnerskab, da vi arbejdede os igennem dette spørgsmål. Vi vil følge op inden for 7 hverdage med en detaljeret rod årsag analyse (RCA), der vil blive delt på vores status side. Hvis du har spørgsmål eller bekymringer, så tøv ikke med at kontakte os på Anaplan Support.

6. 3. september 2026 kl. 15.52 UTCpostmortem

   Den 27. august 2026, kl 10: 22 UTC, nogle kunder i vores ca1: Cloud - Canada region oplevede intermitterende problemer adgang til platformen. I løbet af denne periode, kan brugerne have stødt på fejl, når de forsøger at logge ind. Virkningen varierede afhængigt af, hvilken komponent der behandlede hver anmodning - nogle anmodninger lykkedes, mens andre ikke lykkedes. * * Rodårsag * * Efter en standard systemopdatering, en enkelt handel-routing komponent i Canada-regionen trådte en inkonsistent tilstand efter en konfiguration genindlæses og undladt at genopbygge sin routing instruktioner korrekt. Komponenten begyndte periodisk at afvise eller vildlede kundeanmodninger. Komponentens sundhedstjek bekræftede dens tilgængelighed, men fangede ikke rigtigheden af dets routing konfiguration. Som følge heraf forblev den aktiv og fortsatte med at betjene trafikken. Dette resulterede i nogle anmodninger lykkes, mens andre var forgæves, afhængigt af hvilken komponent håndterede forbindelsen. * * Inddrivelse * * Vores ingeniørhold identificerede problemet og greb straks ind. Holdet isolerede spørgsmålet til en enkelt handel-routing komponent og genstartet det. Dette omfordelte al indgående trafik på tværs af de resterende sunde komponenter. Ved 11: 08 UTC blev problemet løst fuldt ud. * * Korrigerende og forebyggende foranstaltninger * * Vi gennemfører følgende handlinger for at forhindre gentagelse: * Vi hærder sundhedstjekket på vores traffic- routing komponenter til straks at isolere og automatisk genstarte enhver komponent, der undlader at validere korrekt efter en konfiguration opdatering. Dette forhindrer en forringet komponent i fortsat at betjene trafikken og forårsager intermitterende adgangssvigt for kunderne. * Vi raffinerer vores overvågning for at give mere kornet synlighed i de enkelte servicekomponenter. Dette gør det muligt hurtigere at opdage lokaliserede problemer, før de påvirker flere kunder. Vi undskylder for den indvirkning, dette spørgsmål har haft på dine operationer. Vi er forpligtet til de forbedringer, der er skitseret ovenfor for at forhindre lignende forstyrrelser. Hvis du har spørgsmål eller bekymringer, bedes du kontakte vores [Support] (https: / / support.anaplan.com /) team.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 15. august 2026 kl. 03.27 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem, der påvirker kundernes evne til at køre Cloudworks integration. Vi arbejder på at løse dette problem så hurtigt som muligt og vil levere opdateringer hvert 30. minut eller efter resolution.

2. 15. august 2026 kl. 04.02 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem, der påvirker kundernes evne til at få adgang til Anaplan Platform, som også påvirker CloudWorks integration Vi arbejder på at løse dette problem så hurtigt som muligt og vil levere opdateringer hvert 30. minut eller efter resolution.

3. 15. august 2026 kl. 04.31 UTCinvestigating

   Tak for Deres tålmodighed, når vi fortsætter med at undersøge dette spørgsmål. I øjeblikket har vi endnu ikke tid til at tage stilling. Vi vil fortsætte med at levere opdateringer hvert halve minut, når vi arbejder på at løse dette problem så hurtigt som muligt.

4. 15. august 2026 kl. 05.03 UTCidentified

   Vi har identificeret den sandsynlige årsag til problemet, og vi fokuserer lige nu på at genoprette tjenesten så hurtigt som muligt. I øjeblikket har vi endnu ikke tid til at tage stilling. Vi vil levere yderligere opdateringer om 30 minutter eller efter opløsning.

5. 15. august 2026 kl. 05.33 UTCidentified

   Vi har optrappet dette spørgsmål med tredjepartsudbyderen for at mindske problemet. I øjeblikket har vi endnu ikke tid til at tage stilling. Vi vil levere yderligere opdateringer om 30 minutter eller efter opløsning.

6. 15. august 2026 kl. 06.13 UTCidentified

   Vi arbejder fortsat tæt sammen med vores leverandør for at løse problemet med adgang til EU2-regionen, som fortsat er vores højeste prioritet. Gennem vores undersøgelse har vi identificeret forbindelsesspørgsmål til EU- CENTAL-1-regionen som den underliggende årsag. Begyndelsen kl. 7: 33 PDT den 14. august begyndte vores leverandør at opleve øget pakketab, der påvirker konnektiviteten for kunder i EU- CENTAL-1-regionen. Det berørte sted er blevet identificeret som Equinix, Frankfurt. Mens der er gjort fremskridt, er forbindelserne til dette sted stadig svækket. Vi fortsætter med at prioritere opløsning trin med vores leverandør. Men fuld bedring forventes at være flere timer væk. Vi vil give en opdatering hver 60 minutter, som vi arbejder på at gendanne service så hurtigt som muligt, eller hurtigere, hvis yderligere oplysninger bliver tilgængelige.

7. 15. august 2026 kl. 07.12 UTCidentified

   Vi fortsætter med at arbejde med vores leverandør for at løse adgangsproblemet, der påvirker eu2-regionen som vores højeste prioritet. Vi er også ved at udforske flere stier til at genoprette service så hurtigt som muligt. Samarbejdet med vores leverandør er i gang, men fuld inddrivelse forventes at være flere timer væk. Vi vil give en opdatering hver 60 minutter, som vi arbejder på at genoprette service så hurtigt som muligt, eller hurtigere, hvis yderligere oplysninger bliver tilgængelige

8. 15. august 2026 kl. 08.11 UTCidentified

   Vi har afsluttet trafikruten ud af det ramte område og er nu i en overvågningsfase. En yderligere opdatering vil blive givet om 30 minutter, eller før, hvis yderligere oplysninger bliver tilgængelige.

9. 15. august 2026 kl. 08.37 UTCresolved

   Vi har bekræftet, at spørgsmålet nu er løst. Vi undskylder dybt for eventuelle konsekvenser af dette spørgsmål. Vi sætter pris på Deres tålmodighed og partnerskab, da vi arbejdede os igennem dette spørgsmål. Vi vil følge op inden for 7 hverdage med en detaljeret rod årsag analyse (RCA), der vil blive delt på vores status side. Hvis du har spørgsmål eller bekymringer, så tøv ikke med at kontakte os på Anaplan Support.

10. 25. august 2026 kl. 16.00 UTCpostmortem

    Den 15. august 2026, fra 03: 16 UTC til 08: 23 UTC, kunder i vores eu2: Data Center - Tyskland region oplevede en service afbrydelse, der forhindrede adgang til Anaplan platformen. I løbet af denne periode, en lokal infrastruktur fiasko påvirkede regionens evne til at forbinde til eksterne tjenester, hvilket resulterer i et tab af platform tilgængelighed. * * Rodårsag * * Afbrydelsen skyldtes en miljøfejl på vores sælgers tredjeparts anlæg i Frankfurt, Tyskland. En lækage i anlæggets kølesystem førte til lokal overophedning, hvilket udløste automatiske sikkerhedsstop af kritisk netværksudstyr. Flyttet vand også beskadiget lokaliserede strømfordelings systemer i anlægget, deaktivere netværk enheder. Denne kombinerede effekt og køling svigt forhindrede systemet i at løse eksterne adresser og udfylde udgående anmodninger i denne region. * * Inddrivelse * * Da anlæggets miljøforhold gjorde området usikkert at komme ind i, blev vores leverandør forsinket med at vurdere og reparere det berørte udstyr. Som et resultat, vores engineering team indsat en nødsituation ændring til at omdirigere trafik gennem en alternativ regional netvej, uden om den svækkede facilitet og regionen. Dette lykkedes restaureret fuld ekstern forbindelse og navn opløsning, og platform adgang blev fuldt restaureret af 08: 23 UTC. Facilitetens operatør og vores leverandør fortsatte inddrivelse arbejde i løbet af de følgende dage, med fuld restaurering bekræftet af August 18. Vi vedligeholdt vores nødrute i hele denne periode for at holde service stabil, mens sælgeren gennemført reparationer. * * Korrigerende og forebyggende foranstaltninger * * Vi gennemfører følgende foranstaltninger for at styrke modstandsdygtigheden og mindske risikoen for en lignende forstyrrelse: * Vi tilføjer et lag, der automatisk omdirigerer trafik til alternative geografiske steder under en lokaliseret udfald, uden manuel intervention kræves. * Vi gør det muligt cached optegnelser til at fortsætte med at betjene trafik, når stien til eksterne resolvers er utilgængelig, så en forbindelse tab til eksterne tjenester ikke længere forhindrer platform adgang, når en regional begivenhed opstår. * Vi arbejder med vores tredjeparts faciliteter og netværksudbydere for at gennemgå deres standarder for kritiske power og kølesystemer og sikre, at der er stærkere forebyggende sikkerhedsforanstaltninger på plads. Vi undskylder for den indvirkning, dette spørgsmål har haft på dine operationer. Vi går ind for de ovenfor skitserede forbedringer for at forhindre lignende forstyrrelser. Hvis du har spørgsmål eller bekymringer, bedes du kontakte vores Support team.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 29. juli 2026 kl. 11.06 UTCinvestigating

   Vi undersøger i øjeblikket et problem, der påvirker kundernes evne til at få adgang til Anaplan Platform. Vi arbejder på at løse dette problem så hurtigt som muligt og vil levere opdateringer hvert 30. minut eller efter resolution.

2. 29. juli 2026 kl. 11.36 UTCinvestigating

   Vi undersøger i øjeblikket et problem, der påvirker kundernes evne til at få adgang til Anaplan Platform. Tak for Deres tålmodighed, når vi fortsætter med at undersøge dette spørgsmål. I øjeblikket har vi endnu ikke tid til at tage stilling. Vi vil fortsætte med at levere opdateringer hvert halve minut, når vi arbejder på at løse dette problem så hurtigt som muligt.

3. 29. juli 2026 kl. 11.41 UTCmonitoring

   Service er nu blevet genoprettet; du bør nu være i stand til at genoptage normale aktiviteter. Vi vil fortsat overvåge platformen for at sikre, at der ikke opstår yderligere problemer. Hvis du har spørgsmål, bekymringer eller fortsætter med at opleve problemer, skal du ikke tøve med at kontakte Anaplan Support. Vi vil give dig en endelig opdatering, når vi overvejer denne situation helt løst.

4. 29. juli 2026 kl. 12.51 UTCresolved

   Vi har bekræftet, at spørgsmålet nu er løst. Vi undskylder dybt for eventuelle konsekvenser af dette spørgsmål. Vi sætter pris på Deres tålmodighed og partnerskab, da vi arbejdede os igennem dette spørgsmål. Vi vil følge op inden for 7 hverdage med en detaljeret rod årsag analyse (RCA), der vil blive delt på vores status side. Hvis du har spørgsmål eller bekymringer, så tøv ikke med at kontakte os på Anaplan Support.

5. 7. august 2026 kl. 18.56 UTCpostmortem

   On July 29, 2026, between 10:57 UTC and 11:53 UTC, customers in our us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan regions experienced degraded performance. This resulted in delayed model and workspace access, slow page load times, and slower logins across the platform, as well as delayed execution of CloudWorks™ integrations. All other regions were unaffected during this time.  **Root Cause**  The incident was triggered by an automated security software update deployed across our platform servers. This simultaneous update caused an unexpected, short-lived spike in storage activity that temporarily exceeded the storage systems' processing capacity. The resulting latency disrupted communication between internal metadata services and core system servers, causing the service connection pools to become unresponsive and preventing them from automatically recovering.  **Recovery**  Our engineering team identified the issue and took immediate action. We performed rolling restarts of the affected metadata services to clear the unresponsive connection pools and stabilize the systems. By 11:30 UTC, affected systems had recovered. Following this, the CloudWorks™ scheduler was restarted to process and clear the backlog of integration tasks. The issue was fully resolved by 11:53 UTC.  **Corrective & Preventative Actions**  We are implementing the following actions to prevent recurrence:  * We are implementing enhanced storage performance tiers and traffic-prioritization controls to isolate key platform workloads from other background system activities.  * We are updating our internal service connection frameworks to automatically detect and gracefully recover from unexpected system connection interruptions.  * We are refining our security software deployment processes to stagger rollouts and limit simultaneous resource utilization.  * We are enhancing our synthetic monitoring dashboards to improve visibility of regional service performance deviations.  * We are conducting rigorous connection-recovery and system testing in our lower environments to validate application resilience under loaded states.  We apologize for any impact this issue may have had on your business operations. We are continuously strengthening our systems and procedures to ensure we avoid future disruptions to your business and users.  If you have further questions or concerns, please visit our [Support website](https://www.google.com/url?q=https%3A%2F%2Fsupport.anaplan.com%2F). We appreciate your patience during this incident and value the trust you place in Anaplan.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 24. juli 2026 kl. 20.35 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem resulterer i nogle kunder ikke være i stand til at indlæse modeller. Vi arbejder på at løse dette problem så hurtigt som muligt og vil levere opdateringer hvert 30. minut eller efter resolution.

2. 24. juli 2026 kl. 23.01 UTCinvestigating

   Tak for Deres tålmodighed, når vi fortsætter med at undersøge dette spørgsmål. I øjeblikket har vi endnu ikke tid til at tage stilling. Vi vil fortsætte med at levere opdateringer hvert halve minut, når vi arbejder på at løse dette problem så hurtigt som muligt.

3. 24. juli 2026 kl. 23.33 UTCinvestigating

   Tak for Deres tålmodighed, når vi fortsætter med at undersøge dette spørgsmål. Vores støttehold fortsætter med at undersøge dette spørgsmål, men vi har endnu ikke tid til at løse det. Vi vil fortsætte med at levere opdateringer hvert halve minut, når vi arbejder på at løse dette problem så hurtigt som muligt.

4. 25. juli 2026 kl. 00.07 UTCinvestigating

   Tak for Deres tålmodighed, når vi fortsætter med at undersøge dette spørgsmål. Dette spørgsmål er blevet optrappet til vores ledende ingeniør- og lederhold, som aktivt undersøger situationen og evaluerer alle nødvendige næste skridt for at genoprette fuld drift. Selv om vi ikke har specifikke tekniske detaljer at dele på nuværende tidspunkt, bedes du være sikker på, at løsningen af denne hændelse er vores højeste prioritet. Vi undskylder for forstyrrelsen og værdsætter din tålmodighed. Vi vil fortsætte med at levere opdateringer hvert halve minut eller før, hvis der dukker nye detaljer op, da vi arbejder på at løse dette problem så hurtigt som muligt.

5. 25. juli 2026 kl. 00.39 UTCinvestigating

   Vi har identificeret mulige oprensningsveje og er i øjeblikket i gang med aktiv afbødning for at genoprette servicestabiliteten. Selv om vi ikke har en fast estimeret tid til inddrivelse (ETA) at dele på dette tidspunkt, skal du være sikker på, at vores primære fokus forbliver på sikker og hurtig løsning af dette spørgsmål. Vi overvåger nøje virkningen af vores nuværende afbødende foranstaltninger. Vi undskylder for ulejligheden. Vores næste opdatering vil blive offentliggjort om 30 minutter, eller før der opnås vigtige milepæle.

6. 25. juli 2026 kl. 01.08 UTCinvestigating

   Vi forstår den forstyrrelse, det har forårsaget, og vi vil gerne forsikre Dem om, at vi fortsat prioriterer at løse dette så hurtigt som muligt. Vores team er aktivt engageret i oprydning, og de iværksatte foranstaltninger viser meningsfulde fremskridt i retning af fuld service restaurering. Vi anerkender Deres tålmodighed gennem hele denne proces og tager det ikke for givet. Vi overvåger vores systemer nøje og vil levere en yderligere opdatering inden for 30 minutter, eller før skulle der være en betydelig udvikling at dele.

7. 25. juli 2026 kl. 01.42 UTCinvestigating

   Vi fortsætter med at udføre og validere vores afværgeplaner. Vi ser vedvarende fremskridt, efterhånden som genopretningsbestræbelserne skrider frem systematisk. For at sikre en sikker og fuldstændig genopretning skrider vi forsigtigt frem og er endnu ikke i stand til at dele specifikke tekniske milepæle. Vær forvisset om, at hele vores team stadig er fuldt dedikeret til at løse denne hændelse. Tak for Deres tålmodighed. Vores næste opdatering vil blive offentliggjort om 30 minutter, eller før vi har yderligere fremskridt at rapportere.

8. 25. juli 2026 kl. 02.18 UTCinvestigating

   Vi udfører i øjeblikket nødvedligeholdelse i Canada-regionen. Adgangen til platformen er blevet midlertidigt begrænset, mens vores team arbejder for at fuldføre oprydning og validere fuld service restaurering. Vi overvåger aktivt miljøet og gør fremskridt. Vi sætter pris på din tålmodighed og forstår den indvirkning dette har på dit arbejde. Yderligere opdateringer vil blive leveret hver 30 minutter, eller før, hvis der er en betydelig udvikling at dele. Vi undskylder ulejligheden og er fortsat forpligtet til at genoprette tjenesten så hurtigt som muligt.

9. 25. juli 2026 kl. 03.09 UTCinvestigating

   Vores team er fortsat aktivt engageret i oprydningsbestræbelser. Arbejdet skrider frem på tværs af flere arbejdsstrømme, og vi fortsætter med at gøre fremskridt mod fuld service restaurering. Vi vil levere en yderligere opdatering inden for 30 minutter, eller før, hvis der er en meningsfuld udvikling at dele. Vi sætter pris på din tålmodighed.

10. 25. juli 2026 kl. 03.47 UTCinvestigating

    Vi udfører i øjeblikket nødvedligeholdelse i Canada-regionen. Vores team er aktivt involveret i oprensning indsats i koordinering med vores leverandør, og problemet er blevet holdt. Kunden adgang til Canada miljø er fortsat midlertidigt begrænset, mens vi fuldføre validering og restaurering indsats. Vi sætter pris på din tålmodighed og vil give en yderligere opdatering inden for 1 time, eller før, hvis der er en betydelig udvikling at dele.

11. 25. juli 2026 kl. 04.47 UTCinvestigating

    Vores team fortsætter med at arbejde gennem nødvedligeholdelse på Canada regionen i tæt koordinering med vores leverandør. Spørgsmålet er blevet begrænset, og genopbygningsindsatsen er aktivt i gang. Adgangen til Canadas miljø er fortsat midlertidigt begrænset, efterhånden som vi gennemfører de nødvendige valideringstrin før servicegenoprettelsen. Vi anerkender den indvirkning dette har på dit arbejde og værdsætter din fortsatte tålmodighed. Vores næste opdatering vil blive leveret inden for 1 time, eller før skulle en betydelig udvikling forekomme.

12. 25. juli 2026 kl. 06.05 UTCidentified

    Vores team fortsætter med at arbejde gennem nødvedligeholdelse på Canada regionen i tæt koordinering med vores leverandør. Men på grund af genrejsningsprocessens kompleksitet og omfang forventer vi, at genopretningen bliver en udvidet indsats, som vil tage flere timer at fuldføre. Adgangen til Canadas miljø vil fortsat være begrænset, så længe genopretningen finder sted. Vi anerkender den betydelige indvirkning dette har på dit arbejde og oprigtigt værdsætter din tålmodighed. Vores næste opdatering vil blive leveret inden for en time, eller før skulle en betydelig udvikling forekomme.

13. 25. juli 2026 kl. 07.06 UTCidentified

    Vores team og leverandør partnere fortsætter med at gøre fremskridt gennem den komplekse recovery proces for Canada-regionen under denne nødvedligeholdelse. Vi udfører systematisk vores inddrivelsesprotokoller og validerer systemets integritet på hvert trin. Som tidligere nævnt, på grund af omfanget af denne indsats, er dette fortsat en udvidet gendannelsesproces, og adgangen til Canada miljø vil fortsat være begrænset, når vi arbejder hen imod en sikker og komplet service restaurering. Vi er stadig fuldt ud klar over den indvirkning, denne service afbrydelse har på dine operationer og gør alt muligt for at fremskynde disse skridt. Vores næste opdatering vil blive leveret inden for en time, eller før skulle en betydelig udvikling forekomme.

14. 25. juli 2026 kl. 08.07 UTCidentified

    Vores engineering og leverandør teams fortsætter med aktivt at udføre inddrivelse trin for Canada region under nødvedligeholdelse. Der er ingen nye tekniske detaljer eller ændringer at dele på nuværende tidspunkt, da vi udelukkende fokuserer på systematisk og sikker restaurering af tjenester. Adgangen til Canadas miljø er fortsat begrænset, mens disse genopretningsaktiviteter er i gang. Vi værdsætter Deres fortsatte tålmodighed og partnerskab, når vi arbejder gennem denne udvidede indsats. Vores næste opdatering vil blive leveret inden for en time, eller før skulle en betydelig udvikling forekomme.

15. 25. juli 2026 kl. 09.06 UTCidentified

    Vores ingeniørhold og leverandør partnere fortsætter med at gøre fremskridt gennem inddrivelse trin for Canada-regionen under nødvedligeholdelse. Vi er ved at gøre positive fremskridt og er ved at komme tættere på at sætte regionen i stand til de fleste arbejdspladser. Adgangen til Canadas miljø er fortsat midlertidigt begrænset, mens vi udfører og afslutter disse afgørende afsluttende valideringsskridt for at sikre servicestabiliteten. Vi sætter stor pris på Deres tålmodighed og partnerskab, når vi går ind i disse sidste stadier af genopretningsprocessen. Vores næste opdatering vil blive leveret inden for en time, eller før skulle en betydelig udvikling forekomme.

16. 25. juli 2026 kl. 10.07 UTCinvestigating

    Vi fortsætter med systematisk at udføre vores inddrivelsestrin for Canada-regionen under nødvedligeholdelse. Vores ingeniørhold og leverandørpartnere er fortsat fokuseret på de endelige valideringsfaser, og vi fortsætter med at komme tættere på at sætte regionen i stand for de fleste kunder. Adgangen til Canadas miljø er fortsat begrænset indtil videre for at sikre, at vi opretholder systemets stabilitet under disse kritiske afsluttende trin. Vi er utrolig taknemmelige for jeres tålmodighed og partnerskab. Vores næste opdatering vil blive leveret inden for en time, eller før skulle en betydelig udvikling forekomme.

17. 25. juli 2026 kl. 11.14 UTCidentified

    Vores ingeniørhold og leverandørpartnere fortsætter systematisk med at gøre fremskridt gennem de sidste faser af valideringen for Canada-regionen under nødvedligeholdelse. Vi er fortsat fokuseret på at kontrollere systemets stabilitet, hvilket holder os på en stabil vej mod at sætte regionen for de fleste kunder. Adgangen til Canadas miljø er fortsat begrænset indtil videre for at sikre, at disse kritiske sikkerheds- og stabilitetskontroller er gennemført fuldt ud. Vi er utrolig taknemmelige for Deres fortsatte tålmodighed og partnerskab, når vi afslutter denne udvidede indsats. Vores næste opdatering vil blive leveret inden for en time, eller før skulle en betydelig udvikling forekomme.

18. 25. juli 2026 kl. 12.37 UTCidentified

    Vores ingeniør- og sælgerhold går ind i de sidste forberedelsesfaser af vores genopretningsplan for Canada-regionen under nødvedligeholdelse. Som vi forbereder at genoprette adgangen, vores plan er at aktivere alle tjenester i regionen med undtagelse af Medbring din egen nøgle (BYOK) konfigurationer. Derudover vil et lille antal arbejdspladser forblive deaktiveret i første omgang ved generel service restaurering. For disse specifikke resterende arbejdsområder vil vi gennemføre en stærkt kontrolleret, systematisk genoprettelsesplan for at inddrive hvert enkelt miljø for at garantere fuldstændig stabilitet og dataintegritet. Adgangen til det canadiske miljø er fortsat begrænset på nuværende tidspunkt, mens vi afslutter disse afsluttende valideringstrin forud for muligheden. Vi anerkender den vedvarende indvirkning dette har på dine operationer og oprigtigt værdsætter din fortsatte tålmodighed. Vores næste opdatering vil blive leveret inden for en time, eller før skulle en betydelig udvikling forekomme.

19. 25. juli 2026 kl. 13.51 UTCidentified

    Vi genopretter platformen. Vores ingeniør- og sælgerhold arbejder aktivt på at gendanne tjenester så hurtigt som muligt. Som en del af vores genopretningsplan, vil vi genoprette alle tjenester i regionen med undtagelse af Medbring din egen nøgle (BYOK) konfigurationer. Derudover vil et lille antal arbejdsrum forblive midlertidigt deaktiveret ved den første service restaurering. For disse specifikke arbejdsområder vil vi gennemføre en meget kontrolleret, systematisk restaureringsproces for at genvinde hvert miljø individuelt og garantere fuldstændig stabilitet og dataintegritet. Adgangen til det canadiske miljø er fortsat begrænset på nuværende tidspunkt Vi anerkender den betydelige indvirkning dette har på dine operationer og oprigtigt værdsætter din fortsatte tålmodighed. Vores næste opdatering vil blive leveret inden for en time, eller før skulle en betydelig udvikling forekomme.

20. 25. juli 2026 kl. 16.22 UTCidentified

    Vores ingeniørhold arbejder aktivt på at genoprette platformstabiliteten i hele Canada (CA1) gennem en omhyggelig trinvis genopretning. Vi vil i første omgang gendanne generelle tjenester, med undtagelse af Medbring din egen nøgle (BYOK) konfigurationer. For at sikre et stabilt og sikkert miljø, kan et lille antal arbejdspladser forblive midlertidigt deaktiveret, mens vi udfører kontrollerede genoprettelser. Den samlede adgang til Canadas miljø er fortsat begrænset på nuværende tidspunkt, når vi gennemfører disse kritiske genoprettelsesforanstaltninger. Vi erkender dybt den betydelige indvirkning denne situation har på dine operationer og oprigtigt værdsætter din fortsatte tålmodighed, mens vi arbejder gennem disse sikkerhedsforanstaltninger. Vores næste opdatering vil blive leveret inden for en time, eller før skulle en betydelig udvikling forekomme.

21. 25. juli 2026 kl. 17.24 UTCidentified

    Vi har givet generel kundeadgang til Canada-regionen. Alle tjenester i regionen bliver nu bragt online, med undtagelse af Medbring din egen nøgle (BYOK) konfigurationer. Derudover vil et lille, specifikt antal kundearbejdspladser forblive midlertidigt deaktiveret. For disse resterende arbejdspladser, er vores ingeniørhold udfører en meget kontrolleret, systematisk restaurering plan til sikkert inddrive hvert miljø individuelt for at sikre fuldstændig dataintegritet. Vi sætter stor pris på din vedvarende tålmodighed og partnerskab, når vi udfører disse endelige, præcise opsving trin. Vores næste opdatering vil blive leveret inden for en time, eller før skulle en betydelig udvikling forekomme.

22. 25. juli 2026 kl. 23.28 UTCidentified

    Vi beklager dybt den forstyrrelse, det har forårsaget, og sætter stor pris på Deres tålmodighed. Generel kundeadgang til Canada regionen er blevet genoprettet, og tjenester kommer tilbage online. Medbring dine egne nøglekonfigurationer og et lille antal arbejdsområder forbliver midlertidigt offline, mens vi fuldføre omhyggelig, individualiseret restaurering for at sikre fuld dataintegritet. Vi vil levere en yderligere opdatering inden for en time, eller før, hvis der er en betydelig udvikling at dele.

23. 25. juli 2026 kl. 23.52 UTCidentified

    Den generelle kundeadgang til Canada er blevet genoprettet. Workspaces ved hjælp bringe din egen nøgle (BYOK) kryptering vil forblive midlertidigt offline, mens vi fuldføre individualiseret restaurering for hver berørt arbejdsplads. Vi vil give en yderligere opdatering om BYOK restaurering status på 09: 00 UTC den 26 juli 2026. Vi undskylder forstyrrelsen og takker dig for din tålmodighed.

24. 26. juli 2026 kl. 08.59 UTCinvestigating

    Vi skriver for at give en opdatering på højt niveau om service afbrydelse påvirker Canada (CA1) region adgang, der begyndte fredag den 24. juli kl 20: 35 UTC. Gennem den dedikerede koordinering af vores ingeniørhold og sælgerpartnere blev den generelle adgang til Canada-regionen genaktiveret lørdag den 25. juli kl. 17: 24 UTC. Langt de fleste af vores kunder kan nu få adgang til deres arbejdsrum og modeller normalt. Nuværende status og næste trin Mens generel region adgang er blevet fuldt restaureret, arbejdsrum udnytte bringe din egen nøgle (BYOK) kryptering forbliver midlertidigt offline. Vores primære fokus er i øjeblikket på en vellykket gengivelse af den tekniske forstyrrelse i et kontrolleret miljø. Indsigterne fra denne reproduktionsfase er afgørende, da de direkte vil påvirke og bestemme den sikreste, mest effektive gendannelsesti for de resterende BYOK arbejdsrum. Fortsættelse af denne systematiske undersøgelse sikrer, at vi opretholder de højeste standarder for systemstabilitet og dataintegritet. Vi forventer at give vores næste målrettede opdatering om BYOK workspace restaurering ved 11: 00 UTC. Vi undskylder for forstyrrelsen og virkningen på jeres operationer. Vores support hold forbliver fuldt tilgængelige til at hjælpe dig med eventuelle spørgsmål eller umiddelbare behov.

25. 26. juli 2026 kl. 11.16 UTCinvestigating

    Vi skriver for at give en opdatering på højt niveau om service afbrydelse påvirker Canada (CA1) region adgang, der begyndte fredag den 24. juli kl 20: 35 UTC. Gennem den dedikerede koordinering af vores ingeniørhold og sælgerpartnere blev den generelle adgang til Canada-regionen genaktiveret lørdag den 25. juli kl. 17: 24 UTC. Langt de fleste af vores kunder kan nu få adgang til deres arbejdsrum og modeller normalt. Nuværende status og næste trin Mens generel region adgang er blevet fuldt restaureret, arbejdsrum udnytte bringe din egen nøgle (BYOK) kryptering forbliver midlertidigt offline. Vores primære fokus er i øjeblikket på en vellykket gengivelse af den tekniske forstyrrelse i et kontrolleret miljø. Indsigterne fra denne reproduktionsfase er afgørende, da de direkte vil påvirke og bestemme den sikreste, mest effektive gendannelsesti for de resterende BYOK arbejdsrum. Fortsættelse af denne systematiske undersøgelse sikrer, at vi opretholder de højeste standarder for systemstabilitet og dataintegritet. Vi forventer at give vores næste målrettede opdatering om BYOK workspace restaurering ved 13: 00 UTC. Vi undskylder for forstyrrelsen og virkningen på jeres operationer. Vores support hold forbliver fuldt tilgængelige til at hjælpe dig med eventuelle spørgsmål eller umiddelbare behov.

26. 26. juli 2026 kl. 13.06 UTCinvestigating

    Mens generel adgang til Canada (CA1) regionen er blevet fuldt restaureret fra lørdag, 25 Juli kl 17: 24 UTC, arbejdsrum udnytte bringe din egen nøgle (BYOK) kryptering forbliver midlertidigt offline. Vores primære fokus på at reproducere forstyrrelsen i et kontrolleret miljø er stadig i gang med vores leverandør. Dette er en kritisk fase, da den direkte vil påvirke og bestemme den sikreste og mest effektive genvindingsvej for de resterende BYOK arbejdsrum og samtidig sikre systemets stabilitet og dataintegritet. Vi forventer at give vores næste målrettede opdatering om BYOK workspace restaurering inden 15: 00 UTC. Vi undskylder for forstyrrelsen og virkningen på jeres operationer. Vores support hold forbliver fuldt tilgængelige til at hjælpe dig med eventuelle spørgsmål eller umiddelbare behov.

27. 26. juli 2026 kl. 15.20 UTCinvestigating

    De fleste kunder har fortsat fuld adgang til CA1-regionen. Workspaces udnytte Medbring din egen nøgle (BYOK) kryptering forbliver midlertidigt offline, mens vi afslutter sikker inddrivelse, validering, og root- årsag analyse. Vi samarbejder aktivt med vores tredjeparts krypteringspartner for at forstå årsagen og potentielle fix.

28. 26. juli 2026 kl. 17.53 UTCidentified

    EU-erhvervsgrenens økonomiske situation Workspaces udnytte bringe din egen nøgle (BYOK) kryptering forbliver midlertidigt offline, mens vi færdiggøre sikker inddrivelse, validering, og root- årsag analyse. Vi samarbejder aktivt med vores tredjeparts krypteringspartner for at forstå årsagen og potentielle fix.

29. 26. juli 2026 kl. 18.49 UTCidentified

    Den generelle adgang til Canada (CA1) er fortsat fuldt genoprettet. Men arbejdsområder, der udnytter bringe din egen nøgle (BYOK) kryptering vil forblive midlertidigt offline. Vi vil give en yderligere opdatering om BYOK restaurering status på 10: 00 UTC den 27 juli 2026. Vi undskylder forstyrrelsen og takker for Deres tålmodighed.

30. 27. juli 2026 kl. 10.03 UTCinvestigating

    Vi skriver for at give en statusopdatering om den igangværende inddrivelse indsats for bringe din egen nøgle (BYOK) arbejdsområder i Canada (CA1) regionen. De generelle tjenesteydelser i regionen er fortsat fuldt restaureret og fungerer normalt. Nuværende undersøgelsesstatus Vores ingeniør- og sælgerhold fortsætter deres dybdegående undersøgelse af årsagen til den seneste afbrydelse. Vi fokuserer i øjeblikket på at kopiere spørgsmålet inden for et dedikeret, ikke-produktionsmæssigt miljø. Denne kontrollerede replikation er et kritisk skridt, da de tekniske resultater direkte vil give os mulighed for at identificere og validere den mest effektive recovery sti for de resterende BYOK arbejdsrum. Ved at sikre os, at vi forstår systemets opførsel under disse specifikke forhold i non-produktion først, kan vi garantere den absolutte sikkerhed, stabilitet og integritet af dine data i den endelige restaureringsfase. Vi sætter stor pris på din tålmodighed og partnerskab, når vi udfører disse omhyggelige valideringsskridt. Vores næste opdatering vil blive leveret inden for to timer, eller før skulle en væsentlig milepæl nås.

31. 27. juli 2026 kl. 12.30 UTCinvestigating

    Vi fortsætter vores aktive efterforsknings- og genopretningsplanlægning for Medbring din egen nøgle (BYOK) arbejdsområder i Canada (CA1) regionen. De generelle tjenesteydelser til regionen er fortsat fuldt genoprettet og fungerer fortsat normalt. Vores ingeniørhold og sælgerpartnere fortsætter med at fokusere deres indsats på at kopiere afbrydelsen inden for et kontrolleret, ikke-produktionsmiljø. Replikere scenariet under disse sikre forhold forbliver vores højeste prioritet, da det er det kritiske skridt, der vil gøre det muligt for os at identificere og bekræfte den mest effektive helbredelsesvej for de resterende BYOK arbejdsrum. Vi arbejder metodisk for at sikre, at genopbygningsprocessen, når den er påbegyndt, bevarer systemets stabilitet og dataintegritet. Vi sætter pris på din fortsatte tålmodighed og partnerskab, mens denne dybe tekniske validering fortsætter. Vores næste opdatering vil blive leveret inden for to timer, eller før skulle vi have nye fremskridt at dele.

32. 27. juli 2026 kl. 14.04 UTCinvestigating

    Vi fortsætter vores aktive indsats for at genoprette Medbring din egen nøgle (BYOK) arbejdsområder i Canada (CA1) regionen. Generelle tjenester i hele regionen er fortsat fuldt restaurerede og fungerer normalt. For at fremskynde beslutningen, vores ingeniørhold og leverandør partnere forfølger flere linjer af undersøgelse samtidigt. Denne mangefacetterede tilgang er afgørende for at sikre, at vores restaureringsplan er fuldt valideret og bevarer integriteten af dit miljø. Vi sætter stor pris på din tålmodighed og partnerskab, når vi udfører disse samtidige bestræbelser. Vores næste opdatering vil blive leveret inden for to timer, eller før skulle vi opnå et betydeligt gennembrud.

33. 27. juli 2026 kl. 15.54 UTCidentified

    Vi fortsætter vores aktive indsats for at genoprette Medbring din egen nøgle (BYOK) arbejdsområder i Canada (CA1) regionen. Generelle tjenester i hele regionen er fortsat fuldt restaurerede og fungerer normalt. Vores ingeniørhold og sælgerpartnere følger samtidig flere linjer i efterforskningen. Denne parallelle tilgang udføres bevidst for at validere og færdiggøre den mest effektive recovery sti for de resterende BYOK arbejdsrum, der sikrer, at vi gendanne tjenester sikkert og med det højeste niveau af stabilitet. Vi sætter pris på din tålmodighed, når vores hold arbejder gennem disse nødvendige skridt. Vores næste opdatering vil blive leveret inden for to timer, eller før skulle vi opnå et betydeligt gennembrud.

34. 27. juli 2026 kl. 17.37 UTCinvestigating

    Mens generelle tjenester i hele Canada (CA1) regionen forbliver fuldt restaureret og fungerer normalt, fortsætter vi vores dedikerede fokus på genopretning af bring din egen nøgle (BYOK) arbejdsområder. Vores hold bevæger sig systematisk fremad med flere parallelle arbejdsstrømme. At udføre disse bestræbelser samtidigt giver os mulighed for grundigt at analysere alle resultater, sikre, at vi validerer og implementere den mest effektive recovery sti for de resterende BYOK arbejdsrum, sikre, at vi genoprette tjenester sikkert og med det højeste niveau af stabilitet. Vi sætter pris på dit løbende partnerskab og tålmodighed, når vi udfører disse kritiske opsving trin. Vi vil give en yderligere opdatering om BYOK restaurering status på 09: 00 UTC (10: 00 BST) den 28 juli 2026.

35. 28. juli 2026 kl. 09.02 UTCidentified

    De generelle tjenester i Canada (CA1) er fortsat fuldt genoprettet og fungerer normalt. For de resterende bringe din egen nøgle (BYOK) arbejdsrum, vores hold fortsætter med at udføre flere parallelle arbejdsstrømme. Denne samtidige tilgang udføres bevidst for at validere den mest effektive recovery sti for de resterende BYOK arbejdsrum og samtidig sikre absolut systemstabilitet. Vi sætter pris på din tålmodighed. Vores næste opdatering vil blive leveret inden for to timer, eller før skulle vi nå en betydelig milepæl.

36. 28. juli 2026 kl. 11.01 UTCidentified

    Generelle tjenesteydelser i Canada (CA1 )-regionen fungerer fortsat normalt og forbliver fuldt ud stabile. Vores ingeniør- og sælgerhold fortsætter med at gøre fremskridt gennem flere samtidige arbejdsgange for at løse de resterende Medbring din egen nøgle (BYOK) arbejdsområder. Denne parallelle tilgang er fortsat vores aktive fokus, som giver os mulighed for systematisk at validere og implementere den mest effektive helbredelsesvej for de resterende BYOK arbejdsrum med det højeste sikkerhedsniveau. Vi sætter pris på jeres tålmodighed og støtte. Vores næste opdatering vil blive leveret inden for to timer, eller før skulle vi nå en betydelig milepæl.

37. 28. juli 2026 kl. 13.11 UTCidentified

    De generelle tjenester i Canada (CA1) regionen forbliver fuldt restaureret, stabil og fortsætter med at fungere normalt. Vores ingeniørhold og leverandør partnere fortsætter med at bevæge sig fremad med flere samtidige workstreams til at løse de resterende bringe din egen nøgle (BYOK) arbejdsrum. Denne parallelle strategi forbliver vores aktive fokus, så vi systematisk kan validere og implementere den mest effektive recovery sti for de resterende BYOK arbejdsrum. Vi sætter stor pris på din tålmodighed, når vi arbejder gennem disse bevidste skridt. Vores næste opdatering vil blive leveret inden for to timer, eller før skulle vi nå en betydelig milepæl.

38. 28. juli 2026 kl. 16.02 UTCidentified

    De generelle tjenester i Canada (CA1) regionen forbliver fuldt restaureret, stabil og fortsætter med at fungere normalt. Vores engineering teams og leverandør partnere er aktivt at opretholde deres fokus på de resterende bringe din egen nøgle (BYOK) arbejdsområder gennem flere parallelle arbejdsstrømme. Vi sætter pris på jeres tålmodighed og partnerskab, når vi afslutter disse kritiske valideringsfaser. Vores næste opdatering vil blive leveret inden for to timer, eller før skulle vi nå en betydelig milepæl.

39. 28. juli 2026 kl. 19.51 UTCidentified

    Mens generelle tjenester i hele Canada (CA1) regionen forbliver fuldt restaureret og fungerer normalt, fortsætter vi vores dedikerede fokus på genopretning af bring din egen nøgle (BYOK) arbejdsområder. Vores hold bevæger sig systematisk fremad med flere parallelle arbejdsstrømme. At udføre disse bestræbelser samtidigt giver os mulighed for grundigt at analysere alle resultater, sikre, at vi validerer og implementere den mest effektive recovery sti for de resterende BYOK arbejdsrum, sikre, at vi genoprette tjenester sikkert og med det højeste niveau af stabilitet. Vi sætter pris på dit løbende partnerskab og tålmodighed, når vi udfører disse kritiske opsving trin. Vi vil give en yderligere opdatering om BYOK restaurering status på 09: 00 UTC (10: 00 BST) den 29 juli 2026.

40. 29. juli 2026 kl. 09.04 UTCidentified

    Mens generelle tjenester i hele Canada (CA1) regionen forbliver fuldt restaureret og fungerer normalt, fortsætter vi vores dedikerede fokus på genopretning af bring din egen nøgle (BYOK) arbejdsområder. Vores hold fortsætter med at udvikle sig systematisk gennem flere parallelle arbejdsstrømme. Udførelse af disse bestræbelser samtidig giver os mulighed for grundigt at analysere alle tekniske resultater, sikre, at vi validerer og implementere den sikreste og mest stabile opsving sti for de resterende BYOK arbejdsrum. Vi sætter pris på dit løbende partnerskab og tålmodighed, når vi udfører disse kritiske opsving trin. Vores næste opdatering vil blive leveret inden for to timer, eller før skulle vi nå en betydelig milepæl.

41. 29. juli 2026 kl. 13.23 UTCinvestigating

    Mens generelle tjenester i hele Canada (CA1) regionen forbliver fuldt restaureret og fungerer normalt, fortsætter vi vores dedikerede fokus på genopretning af bring din egen nøgle (BYOK) arbejdsområder. Vores hold fortsætter stadig med at udvikle sig systematisk gennem flere parallelle arbejdsgange. Udførelse af disse bestræbelser samtidig giver os mulighed for grundigt at analysere alle tekniske resultater, sikre, at vi validerer og implementere den sikreste og mest stabile opsving sti for de resterende BYOK arbejdsrum. Vi sætter pris på dit løbende partnerskab og tålmodighed, når vi udfører disse kritiske opsving trin. Vores næste opdatering vil blive leveret inden for to timer, eller før skulle vi nå en betydelig milepæl.

42. 29. juli 2026 kl. 15.21 UTCinvestigating

    Generelle tjenesteydelser i hele Canada (CA1) regionen forbliver fuldt restaureret og fortsætter med at fungere normalt. Vores ingeniør- og driftsteam vedligeholder deres dedikerede, koncentrerede fokus på at inddrive de resterende Medbring din egen nøgle (BYOK) arbejdsrum. For at sikre den sikreste mulige restaurering, er vi aktivt fremme flere parallelle recovery workstreams. At køre disse bestræbelser samtidig giver os mulighed for konsekvent at analysere tekniske resultater i realtid, sikre, at vi validerer og implementere den mest stabile og sikre vej frem for de resterende BYOK arbejdsrum. Vi sætter stor pris på jeres tålmodighed og partnerskab, når vi systematisk gennemfører disse kritiske genopretningsskridt. Vores næste opdatering vil blive leveret inden for to timer, eller før skulle vi nå en betydelig milepæl.

43. 29. juli 2026 kl. 17.17 UTCinvestigating

    Mens generelle tjenester i hele Canada (CA1) regionen forbliver fuldt restaureret og fungerer normalt, fortsætter vi vores dedikerede fokus på genopretning af bring din egen nøgle (BYOK) arbejdsområder. Vores hold bevæger sig systematisk fremad med flere parallelle arbejdsstrømme. At udføre disse bestræbelser samtidigt giver os mulighed for grundigt at analysere alle resultater, sikre, at vi validerer og implementere den mest effektive recovery sti for de resterende BYOK arbejdsrum, sikre, at vi genoprette tjenester sikkert og med det højeste niveau af stabilitet. Vi sætter pris på dit løbende partnerskab og tålmodighed, når vi udfører disse kritiske opsving trin. Vi vil give en yderligere opdatering om BYOK restaurering status på 09: 00 UTC (10: 00 BST) den 30. juli 2026.

44. 30. juli 2026 kl. 08.59 UTCinvestigating

    Mens generelle tjenester i hele Canada (CA1) regionen fortsætter med at fungere normalt med fuld stabilitet, vores tekniske hold opretholde deres dedikerede fokus på inddrivelse af de resterende bringe din egen nøgle (BYOK) arbejdsrum. Vi fortsætter med at fremme flere parallelle arbejdsstrømme for at validere og udføre den sikreste mulige restaureringssti. At køre disse bestræbelser samtidigt giver os mulighed for grundigt at analysere alle tekniske resultater, sikre, at vi gendanne tjenester med det højeste niveau af sikkerhed og stabilitet for alle udestående BYOK arbejdsrum. Vi værdsætter Deres fortsatte tålmodighed og partnerskab, da vi systematisk arbejder gennem disse kritiske genopretningsskridt. Vi vil give en yderligere opdatering om BYOK restaurering fremskridt i to timer.

45. 30. juli 2026 kl. 11.07 UTCinvestigating

    Mens generelle tjenester i hele Canada (CA1) regionen fortsætter med at fungere normalt med fuld stabilitet, vores tekniske hold opretholde deres dedikerede fokus på inddrivelse af de resterende bringe din egen nøgle (BYOK) arbejdsrum. Vi fortsætter med at fremme flere parallelle arbejdsstrømme for at validere og udføre den sikreste mulige restaureringssti. At køre disse bestræbelser samtidigt giver os mulighed for grundigt at analysere alle tekniske resultater, sikre, at vi gendanne tjenester med det højeste niveau af sikkerhed og stabilitet for alle udestående BYOK arbejdsrum. Vi værdsætter Deres fortsatte tålmodighed og partnerskab, da vi systematisk arbejder gennem disse kritiske genopretningsskridt. Vi vil give en yderligere opdatering om BYOK restaurering status på 09: 00 UTC (10: 00 BST) den 31 juli 2026, eller før skulle vi nå en betydelig milepæl.

46. 31. juli 2026 kl. 09.04 UTCinvestigating

    Mens generelle tjenester i hele Canada (CA1) regionen fortsætter med at fungere normalt med fuld stabilitet, vores tekniske hold opretholde deres dedikerede fokus på inddrivelse af de resterende bringe din egen nøgle (BYOK) arbejdsrum. Vi fortsætter med at fremme flere parallelle arbejdsstrømme for at validere og udføre den sikreste mulige restaureringssti. At køre disse bestræbelser samtidigt giver os mulighed for grundigt at analysere alle tekniske resultater, sikre, at vi gendanne tjenester med det højeste niveau af sikkerhed og stabilitet for alle udestående BYOK arbejdsrum. Vi værdsætter Deres fortsatte tålmodighed og partnerskab, da vi systematisk arbejder gennem disse kritiske genopretningsskridt. Vi vil give en yderligere opdatering om BYOK restaurering status på 09: 00 UTC (10: 00 BST) den 3. august 2026, eller før skulle vi nå en betydelig milepæl.

47. 31. juli 2026 kl. 13.47 UTCresolved

    Vi har bekræftet, at spørgsmålet nu er løst. Vi undskylder dybt for eventuelle konsekvenser af dette spørgsmål. Vi sætter pris på Deres tålmodighed og partnerskab, da vi arbejdede os igennem dette spørgsmål. Vi vil følge op inden for 7 hverdage med en detaljeret rod årsag analyse (RCA), der vil blive delt på vores status side. Hvis du har spørgsmål eller bekymringer, så tøv ikke med at kontakte os på Anaplan Support.

48. 11. august 2026 kl. 16.03 UTCpostmortem

    **Summary**  On July 24, 2026, at 20:22 UTC, our engineering team began investigating an issue affecting customers in our ca1: Cloud — Canada region. Customers with affected workspaces were unable to open their models. As a precaution, while we validated the scope of the issue, we restricted access to the region behind a maintenance page at 02:18 UTC on July 25. General access to CA1 was restored at 17:24 UTC on July 25. Bring Your Own Key \(BYOK\) workspaces remained offline for additional safeguards, and were re-enabled progressively as those safeguards were validated. The incident was fully resolved on July 31, 2026, at 13:47 UTC.  **Root cause**  The disruption was caused by a defect in a third-party component used within our BYOK service. The defect only surfaced under a very specific combination of events occurring in a particular order on the same host. When a BYOK workspace was unloaded, the component failed tofully clear one of its local resources, leaving behind a stale reference. When a BYOK workspace was subsequently loaded onto the same host, the component attempted to clean up that stale reference before proceeding. During this step, it incorrectly executed a removal that extended beyond the stale reference and deleted files that were still in active use.   The affected files were captured in our regular backups. Once our engineering team identified the source of the activity, isolated it, and applied protective controls to stop any further impact, restoration became a controlled process of returning each affected file to its most recent backup.  **Recovery**  Our engineering team identified the issue and isolated it at its source, then worked systematically to restore the affected files. This allowed us to bring non-BYOK workspaces back online in a controlled sequence, and general access to CA1 was restored at 17:24 UTC on July 25.  We deliberately kept BYOK workspaces offline while our team worked with the third-party vendor to reproduce the trigger in a controlled, non-production environment. This reproduction gave us the diagnostic evidence the vendor needed to build a fix and to confirm the exact cause. It also allowed us to develop and validate our own temporary safeguards — targeted changes to how BYOK workspaces are scheduled — that eliminated the specific combination of conditions required to trigger the defect. These safeguards act as compensating controls to bring BYOK workspaces back online while the third party completes the permanent fix to the underlying component. We re-enabled BYOK workspaces once those safeguards were validated, ensuring the trigger conditions couldn't recur. The incident was fully resolved on July 31, 2026, at 13:47 UTC.  **Corrective and preventative actions**  Our corrective actions follow two complementary tracks. The first removes the specific combination of conditions required to trigger the defect, using controls we have developed and deployed ourselves as compensating safeguards. The second is the permanent fix to the underlying component itself, which the third party is delivering. Together, these tracks address both the trigger and the defect, so that neither can produce another incident of this kind. We are implementing the following actions to prevent recurrence:  * We have deployed changes that prevent the specific combination of conditions required to trigger the defect. This is a temporary but effective control that removes the trigger today, ahead of the permanent fix.  * We are working with the third party to deploy their validated fix. This removes the defect at its source and closes the underlying cause of this incident.  * We are strengthening how we validate BYOK third-party components in non-production before they reach production, including reproducing a wider range of workspace lifecycle scenarios and event sequences. This gives us stronger assurance to surface these types of issues in non-production and are addressed before they can affect customers.  * We have deployed dedicated alerting on the specific event pattern that triggered this incident and are actively reviewing additional file-level alerting. These alerts provide an additional safety net and earlier warning, enabling faster preventative action before customers are affected.  **Closing**  We apologize for any impact this issue may have had on your business operations. We are continuously strengthening our systems and procedures to ensure we avoid future disruptions to your business and users.   If you have further questions or concerns, please visit our [Support](https://www.google.com/url?q=https%3A%2F%2Fsupport.anaplan.com%2F) website. We appreciate your patience during this incident and value the trust you place in Anaplan.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 21. juli 2026 kl. 14.30 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem, der påvirker kundernes evne til at køre Cloudworks integration. Vi arbejder på at løse dette problem så hurtigt som muligt og vil levere opdateringer hvert 30. minut eller efter resolution.

2. 21. juli 2026 kl. 14.44 UTCmonitoring

   Service er nu blevet genoprettet; du bør nu være i stand til at genoptage normale aktiviteter. Vi vil fortsat overvåge platformen for at sikre, at der ikke opstår yderligere problemer. Hvis du har spørgsmål, bekymringer eller fortsætter med at opleve problemer, skal du ikke tøve med at kontakte Anaplan Support. Vi vil give dig en endelig opdatering, når vi overvejer denne situation helt løst.

3. 21. juli 2026 kl. 14.54 UTCresolved

   Vi har bekræftet, at spørgsmålet nu er løst. Vi undskylder dybt for eventuelle konsekvenser af dette spørgsmål. Vi sætter pris på Deres tålmodighed og partnerskab, da vi arbejdede os igennem dette spørgsmål. Vi vil følge op inden for 7 hverdage med en detaljeret rod årsag analyse (RCA), der vil blive delt på vores status side. Hvis du har spørgsmål eller bekymringer, så tøv ikke med at kontakte os på Anaplan Support.

4. 30. juli 2026 kl. 22.22 UTCpostmortem

   Den 21. juli 2026, mellem 14: 15 UTC og 14: 50 UTC, os5: Cloud - US East region oplevede en afbrydelse af planlagt CloudWorks ™ integration. I dette vindue kunne automatiserede arbejdsgange ikke udløses, og brugerne kan have haft problemer med at få adgang til integrationstjenester. * * Rodårsag * * Spørgsmålet blev udløst af en kort afbrydelse i de underliggende lagringssystemer efter en systemfrigivelse rollback. Dette førte til et tab af forbindelse inden for integration scheduler system, som forhindrede planmæssige opgaver i at blive sat i kø eller udløst. * * Inddrivelse * * Vores ingeniørhold identificerede problemet og greb straks ind. Vi verificerede systemforbindelse, da de underliggende tjenester blev genvundet automatisk, og vi udførte testintegreringer for at validere planlagte arbejdsgange. Disse valideringskontroller bekræftede, at alle planlægningsmekanismer sikkert havde genoptaget normale operationer uden at kræve en systemgenstart. Ved 14: 50 UTC blev problemet løst fuldt ud. * * Korrigerende og forebyggende foranstaltninger * * * Vi foretager en dybdegående undersøgelse af systemets ydeevne under rollback-operationer for at sikre stabilitet under høje belastningsforhold. * Vi er ved at gennemføre forbedrede sundhedskontroller for integration scheduler for at sikre, at det når en "klar" tilstand, før trafikken er dirigeret under rollbacks. * Vi opdaterer vores implementering processer til at omfatte automatiseret validering af opgave kø dybde umiddelbart efter enhver regional opdatering eller rollback. * Vi opdaterer vores ressource størrelse dokumentation for denne service med anbefalede anmodning / grænseværdier for at sikre tilstrækkelig kapacitet til implementering og rollback operationer. Vi undskylder for enhver indvirkning på din forretning. Vi styrker vores systemer og procedurer for at undgå forstyrrelser i din virksomhed og brugere. Hvis du har yderligere spørgsmål eller bekymringer, kan du besøge vores [Support] (https: / / www.google.com / url? q = https% 3A% 2F% 2Fsupport.anaplan.com% 2F) hjemmeside. Vi værdsætter din tålmodighed under denne hændelse og værdsætter den tillid, du placerer i Anaplan.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. juli 2026 kl. 20.04 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem, der påvirker kundernes evne til at køre Cloudworks integration. Vi arbejder på at løse dette problem så hurtigt som muligt og vil levere opdateringer hvert 30. minut eller efter resolution.

2. 14. juli 2026 kl. 21.00 UTCmonitoring

   Vi har set, at noget er gået galt. Vi undersøger sagen og vil snart opdatere den.

3. 14. juli 2026 kl. 21.04 UTCmonitoring

   Service er nu blevet genoprettet; du bør nu være i stand til at genoptage normale aktiviteter. Vi vil fortsat overvåge platformen for at sikre, at der ikke opstår yderligere problemer. Hvis du har spørgsmål, bekymringer eller fortsætter med at opleve problemer, skal du ikke tøve med at kontakte Anaplan Support. Vi vil give dig en endelig opdatering, når vi overvejer denne situation helt løst.

4. 14. juli 2026 kl. 21.12 UTCresolved

   Vi har bekræftet, at spørgsmålet nu er løst. Vi undskylder dybt for eventuelle konsekvenser af dette spørgsmål. Vi sætter pris på Deres tålmodighed og partnerskab, da vi arbejdede os igennem dette spørgsmål. Vi vil følge op inden for 7 hverdage med en detaljeret rod årsag analyse (RCA), der vil blive delt på vores status side. Hvis du har spørgsmål eller bekymringer, så tøv ikke med at kontakte os på Anaplan Support.

5. 22. juli 2026 kl. 18.15 UTCpostmortem

   Den 14. juli 2026, kl. 19: 55 UTC, oplevede kunder i vores us7: Cloud - US West region forsinkelser og svigt i CloudWorks ™ integration job behandling. Integration job, der var planlagt til at køre i denne region ikke afsluttet som forventet, hvilket resulterer i en behandling tilbage, der blev ryddet, når tjenesten blev fuldt restaureret. Rodsag En back- end komponent, der understøtter CloudWorks ™ -tjenesten, har midlertidigt opbrugt sin tilgængelige hukommelse, hvilket har ført til en kort forbindelsesforstyrrelse. Selv om databasen blev genvundet med det samme, bevarede CloudWorks ™ proceskomponenter inaktive forbindelser og kunne ikke automatisk genoprette forbindelsen. Dette forhindrede integration job i at fuldføre og forårsagede en kø af planlagte opgaver at akkumulere. Inddrivelse Vores ingeniørhold identificerede problemet og greb straks ind. Holdet genstartede CloudWorks ™ proceskomponenter for at rydde alle dårlige og inaktive forbindelser. For hurtigt at få bugt med de udestående integrationsjob øgede vi midlertidigt forarbejdningskapaciteten for komponenterne. Efter at have kontrolleret, at integrationsjob blev gennemført normalt, og at efterslæbet var blevet fuldt behandlet, vendte vi systemet tilbage til sin oprindelige kapacitet. Ved 21: 14 UTC blev problemet løst fuldt ud. Korrigerende og forebyggende foranstaltninger Vi gennemfører følgende foranstaltninger for at forhindre gentagelse: * * * Forhøjelse af hukommelsesallokering: * * Vi øger hukommelsen allokering for back-end komponent i us7. Dette reducerer sandsynligheden for, at en lignende hukommelsestrykhændelse opstår i fremtiden. * * * Optimering af baggrundsprocessen: * * Vi har deaktiveret visse baggrundsmetriske indsamlingsprocesser, der bidrog med unødvendig belastning til backend komponenten. Dette yderligere sænker risikoen for memory pressure building over tid. * * * Restkoncentrationstest: * * Vores ingeniørhold kører kontrollerede tests i ikke-produktionsmiljøer for bedre at forstå, hvordan CloudWorks ™ -tjenesten opfører sig under korte forbindelsesforstyrrelser. Dette arbejde vil hjælpe os med at forbedre tjenestens evne til at komme sig automatisk - uden at kræve manuel indgriben - hvis en lignende begivenhed skulle opstå i fremtiden. Vi undskylder for den indvirkning, dette spørgsmål har haft på dine operationer. Vi går ind for de ovenfor skitserede forbedringer for at forhindre lignende forstyrrelser. Hvis du har spørgsmål eller bekymringer, bedes du kontakte [Support] (https: / / support.anaplan.com /).

Automatisk oversat fra den officielle hændelsesopdatering.

1. 2. juli 2026 kl. 00.00 UTCinvestigating

   Vi undersøger i øjeblikket et problem, der påvirker kundernes evne til at få adgang til Anaplan Platform. Vi arbejder på at løse dette problem så hurtigt som muligt og vil levere opdateringer hvert 30. minut eller efter resolution.

2. 2. juli 2026 kl. 00.30 UTCinvestigating

   Tak for Deres tålmodighed, når vi fortsætter med at undersøge dette spørgsmål. Vi oplever i øjeblikket en kritisk afbrydelse af tjenesten, som forårsager, at der ikke er adgang til alle i de berørte regioner. Brugere, der forsøger at få adgang til tjenester i disse regioner vil støde på tilslutning timeouts og manglende at indlæse ressourcer. I øjeblikket har vi endnu ikke tid til at tage stilling. Vi vil fortsætte med at levere opdateringer hvert halve minut, når vi arbejder på at løse dette problem så hurtigt som muligt.

3. 2. juli 2026 kl. 00.59 UTCinvestigating

   Vi undersøger et problem, der påvirker login og platformadgang for kunder i vores ME1- og EU5-regioner. Den første undersøgelse peger på en afbrydelse af godkendelsesvejen for disse regioner. At løse dette er vores højeste prioritet, og vores ingeniørhold arbejder aktivt på at genoprette normale operationer. Vi har ikke en ETA endnu. Vi vil give en anden opdatering inden for 30 minutter, eller før, hvis vi har væsentlige nye oplysninger.

4. 2. juli 2026 kl. 01.29 UTCinvestigating

   Vores undersøgelse af login og platform adgang problem påvirker ME1 og EU5 regioner er i gang. Vi har engageret vores leverandør for yderligere støtte, som vi arbejder på at identificere og løse den grundlæggende årsag. At løse dette er fortsat vores højeste prioritet. Ingen ETA endnu. Vi vil give vores næste opdatering inden for 30 minutter, eller før, hvis vi har væsentlige nye oplysninger.

5. 2. juli 2026 kl. 01.58 UTCinvestigating

   Vores undersøgelse af login og platform adgang problem påvirker ME1 og EU5 regioner er i gang. Vores ingeniørhold har indsnævret efterforskningen og er aktivt i gang med at efterforske flere linjer i samarbejde med vores infrastrukturpartner. Genopretning service forbliver vores højeste prioritet. Ingen ETA endnu. Vi vil give vores næste opdatering inden for 30 minutter, eller før, hvis vi har væsentlige nye oplysninger.

6. 2. juli 2026 kl. 02.27 UTCinvestigating

   Vi undersøger et problem, der påvirker login og platformadgang for kunder i vores ME1- og EU5-regioner. Emnet begyndte omkring 23: 52 UTC den 1 juli 2026. I samarbejde med vores infrastrukturpartner har vi med succes indsnævret de potentielle årsager og fokuserer i øjeblikket vores tekniske indsats på at isolere spørgsmålet for at iværksætte målrettet afbødning. Vores team er fortsat fuldt engageret i at løse dette problem så hurtigt som muligt. Vi vil give vores næste opdatering inden for 30 minutter, eller før, hvis vi har væsentlige nye oplysninger.

7. 2. juli 2026 kl. 02.55 UTCinvestigating

   Vi fortsætter med at undersøge spørgsmålet om login og platformadgang for kunder i vores ME1- og EU5-regioner. Vi har identificeret den potentielle årsag og er aktivt fremme afbødning af problemet og genoprette fuld service. Vi vil fortsætte med at levere opdateringer som oprensning fremskridt. Vi vil give vores næste opdatering inden for 30 minutter, eller før, hvis vi har væsentlige nye oplysninger.

8. 2. juli 2026 kl. 03.21 UTCmonitoring

   Service er nu blevet genoprettet; du bør nu være i stand til at genoptage normale aktiviteter. Vi vil fortsat overvåge platformen for at sikre, at der ikke opstår yderligere problemer. Hvis du har spørgsmål, bekymringer eller fortsætter med at opleve problemer, skal du ikke tøve med at kontakte Anaplan Support. Vi vil give dig en endelig opdatering, når vi overvejer denne situation helt løst.

9. 2. juli 2026 kl. 04.00 UTCresolved

   Vi har bekræftet, at spørgsmålet nu er løst. Vi undskylder dybt for eventuelle konsekvenser af dette spørgsmål. Vi sætter pris på Deres tålmodighed og partnerskab, da vi arbejdede os igennem dette spørgsmål. Vi vil følge op inden for 7 hverdage med en detaljeret rod årsag analyse (RCA), der vil blive delt på vores status side. Hvis du har spørgsmål eller bekymringer, så tøv ikke med at kontakte os på Anaplan Support.

10. 10. juli 2026 kl. 18.35 UTCpostmortem

    Den 1. juli 2026, ca. 23: 52 UTC, vores overvågningssystemer opdaget en service forstyrrelser påvirker kunder i me1: Cloud - Mellemøsten og eu5: Cloud - Europa regioner. I denne periode, berørte kunder var ude af stand til at logge ind på platformen. Tjenesten blev genoprettet kl 03: 21 UTC * * Rodårsag * * Afbrydelsen opstod fra en planlagt netværkskonfiguration ændring til vores interne navn opløsning infrastruktur. En forkert konfiguration blev indført som en del af den ændring, der efterlod en underliggende routing konflikt på plads. Dette forårsagede returtrafik for interne navneopslag til at tage en forkert sti under rutinemæssig netværksaktivitet. Som følge heraf begyndte den interne navneløsning at svigte for de to berørte regioner. Dette forhindrede autentificeringsstrømmen i at udfylde og stoppe kunderne fra at logge ind. * * Inddrivelse * * På opdagelse klokken 23.52 UTC begyndte vores ingeniørhold og vores infrastrukturpartner at undersøge parallelt. Fordi interne navnesolution spørgsmål kan præsentere sig på flere forskellige måder, teamet arbejdede gennem flere linjer af undersøgelser, før isolere den specifikke routing konflikt ansvarlig. Når identificeret, vi rullede tilbage den seneste ændring for at genoprette den tidligere known-god routing konfiguration. Forbindelse genvundet gradvist som rollback formeret, og ved 03: 21 UTC, autentificering blev fuldt restaureret for begge berørte regioner. * * Korrigerende og forebyggende foranstaltninger * * Vi gennemfører følgende foranstaltninger for at forhindre en gentagelse: * Vi tilføjer præ-ændring validering, der specifikt registrerer klassen af routing konflikt ansvarlig for denne hændelse. Dette lukker den underliggende konfiguration problem, før nogen lignende ændring kan nå miljøet. * Vi re- architecting de berørte routing setup for at forhindre denne klasse af forkert konfiguration fra at blive indført igen. Dette fjerner det underliggende problem ved kilden. * Vi er ved at forbedre vores overvågning af de interne navnesolution stier mellem vores cloud miljøer. Dette forkorter tiden til at opdage og løse denne klasse af spørgsmål. * * Lukning * * Vi undskylder for den indvirkning denne afbrydelse har haft på dine operationer. Ovenstående korrigerende foranstaltninger fokuserer på at forhindre en gentagelse af lignende spørgsmål i fremtiden. Hvis du har spørgsmål eller bekymringer, bedes du kontakte [Support] (https: / / support.anaplan.com /).

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. juni 2026 kl. 07.29 UTCinvestigating

   We are currently investigating an issue resulting in some customers not being able to load models. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

2. 22. juni 2026 kl. 07.48 UTCinvestigating

   Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

3. 22. juni 2026 kl. 08.23 UTCinvestigating

   We are actively investigating a service disruption currently affecting customers' ability to open Models. This issue is also affecting CloudWorks Integrations. Our engineering teams are prioritizing this issue and evaluating immediate mitigation steps to restore full service as quickly and safely as possible. We do not yet have an estimated time to resolution, but will provide progress updates every 30 minutes or sooner.

4. 22. juni 2026 kl. 08.52 UTCidentified

   We are progressing with active mitigation steps to resolve the disruption affecting Model opening and CloudWorks integrations. Initial reports indicate positive outcomes from these activities. Our engineering teams are closely monitoring system stability while we complete the remaining mitigation steps to ensure a full and durable recovery. We will continue to provide updates every 30 minutes as we work to bring all systems back to standard operations.

5. 22. juni 2026 kl. 09.25 UTCidentified

   We are currently proceeding with the final remediation steps while continuing our investigation into the root cause. Customers should now be able to open models, though some may still encounter temporary delays; however, CloudWorks integrations are not yet completing. We are monitoring these recovery steps closely to ensure full system stability and will continue to provide updates every 30 minutes.

6. 22. juni 2026 kl. 09.36 UTCidentified

   We are pleased to report that all issues affecting model loading have been fully resolved, and normal access has been restored. Additionally, CloudWorks integrations are running again, and our teams are currently processing the accumulated backlog of queued jobs. We are monitoring the queue progression closely to ensure all delayed integrations complete successfully. We will provide our next update in 30 minutes or once the backlog is fully cleared.

7. 22. juni 2026 kl. 10.05 UTCidentified

   Our teams confirm that the CloudWorks integration backlog is actively processing and recovering. Access to opening models remains fully restored and stable. We are continuing to monitor the integration queues closely as jobs complete, and we will provide our next status update in 30 minutes.

8. 22. juni 2026 kl. 10.22 UTCmonitoring

   Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

9. 22. juni 2026 kl. 10.52 UTCresolved

   We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

10. 1. juli 2026 kl. 19.34 UTCpostmortem

    On June 22, 2026, at 07:20 UTC, we became aware of an issue affecting our us7: Cloud – US region. Customers experienced difficulties loading models, with impact beginning at approximately 05:12 UTC. CloudWorks™ integrations in the region were also unable to run during this period. Customers with active workspace sessions weren't affected. However, any workspace that was unloaded during this time couldn't be loaded until service was restored. Full service was restored at 10:21 UTC.  **Root cause**  A component that manages active workspace resources in the us7 region encountered an unexpected fault and restarted. On restart, the component entered a state where it appeared to be operating normally but couldn't process new workspace requests. Our systems normally recover automatically from this kind of state, but in this case the fault wasn't detected by our recovery processes. We intervened manually and performed a corrective restart of the component, which restored normal operation.  **Recovery**  We conducted a thorough investigation of the platform and identified the source of the issue. We performed a targeted reset of the resource scheduling services to clear the pending connections and restore normal communication. Once communication was re-established at 08:48 UTC, the platform began successfully assigning resources and loading models.  To handle the accumulated backlog of scheduled integrations, we scaled up the processing capacity for CloudWorks™. By 10:21 UTC, the backlog had finished processing, and the issue was fully resolved.  **Corrective and preventative actions**  We're implementing the following actions to prevent recurrence:  * We're deploying enhanced automated monitoring specifically designed to detect the condition seen in this incident, where a component appears operational but isn't processing requests. This closes the detection gap that extended the impact of this issue.  * We're developing automated self-healing for the resource scheduling component, so that a corrective restart can be performed automatically without engineering intervention. This directly addresses the failure mode that caused this incident.  * We're streamlining our scaling procedures for CloudWorks™, so that integration processing capacity can be expanded more rapidly during recovery. This shortens the time to clear integration backlogs following incidents like this one.  We apologize for any impact this issue may have had on your business operations. We are continuously strengthening our systems and procedures to ensure we avoid future disruptions to your business and users.  If you have further questions or concerns, please visit our [Support](https://support.anaplan.com/) website. We appreciate your patience during this incident and value the trust you place in Anaplan.

1. 17. juni 2026 kl. 07.02 UTCinvestigating

   We are currently investigating an issue resulting in some customers not being able to load models. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

2. 17. juni 2026 kl. 08.00 UTCinvestigating

   Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

3. 17. juni 2026 kl. 08.31 UTCinvestigating

   Thank you for your patience as we continue to investigate this issue. Our technical teams are fully engaged, and restoring normal service operations as quickly and safely as possible is our absolute priority. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

4. 17. juni 2026 kl. 08.59 UTCinvestigating

   Thank you for your patience as we continue to investigate this issue. Our coordinated technical response has made progress in narrowing down the scope of our investigation. We have isolated the primary area of concern to our storage configuration layer and are evaluating mitigation steps to alleviate the issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

5. 17. juni 2026 kl. 09.22 UTCidentified

   We have identified the likely cause of the issue, and we are focused right now on restoring service as quickly as possible. We have identified mitigation steps to alleviate the issue and initial reports indicate positive outcomes of these activities. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

6. 17. juni 2026 kl. 09.50 UTCidentified

   We are pleased to report a significant milestone in our resolution efforts. Our cross-functional engineering teams have successfully validated a targeted configuration adjustment to restore access to the affected workspaces. We have initiated a phased deployment of this mitigation across the region to safely and systematically restore full access to all affected workspaces. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

7. 17. juni 2026 kl. 10.06 UTCmonitoring

   Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

8. 17. juni 2026 kl. 10.23 UTCresolved

   We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

9. 26. juni 2026 kl. 17.41 UTCpostmortem

   On June 17, 2026, at 06:50 UTC, we became aware of an issue affecting a subset of workspaces in our eu4: Cloud - Europe region. Customers with affected workspaces were unable to load models, seeing persistent loading screens or errors when opening their work. CloudWorks™ integrations in the region also experienced a period of degradation, from approximately 05:20 UTC to 06:26 UTC, because of the same underlying issue. The impact was limited to a specific subset of workspaces — all other regions, and many workspaces in eu4: Cloud - Europe, continued to operate normally. Full service for the affected workspaces was restored at 10:00 UTC.   Root cause  The affected workspaces ran on a previous storage configuration in the eu4 region. Over time, a storage directory used by these workspaces accumulated a large number of small temporary files. The directory reached its operational limit and could no longer accept new file operations. This prevented models from loading for customers whose workspaces were running on this configuration.  Recovery  Our engineering team cleared the accumulated temporary files, which provided immediate relief. We then moved all affected workspaces from the old configuration to the new configuration through an automated process. We checked that model loading was restored through testing. By 10:00 UTC, the issue was fully resolved. On the same day, we implemented a change across the eu4 region to make sure no workspace can be directed to the old configuration.  Corrective and preventative actions  We've taken the following actions to address this incident and prevent it from happening again:  1. We've deployed an update across all regions that prevents any workspace from being directed to the older storage configuration. This eliminates the specific configuration condition that caused this incident.  2. We're decommissioning the older storage configuration. This permanently removes the configuration that caused this incident.  3. We’re strengthening our automated validation checks to confirm that workspaces are running on the correct configuration. This catches any configuration mismatch before it can cause customer impact.  4. We're implementing automated cleanup rules for the temporary files involved in this incident. This prevents storage directories from reaching operational limits and supports faster automatic recovery.  Closing  We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

1. 11. juni 2026 kl. 17.20 UTCinvestigating

   We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

2. 11. juni 2026 kl. 17.45 UTCidentified

   We want to sincerely apologize to our customers for the continued disruption to the Anaplan Platform today. We understand how critical access to Anaplan is for your business, and we deeply regret the impact this is having on your teams. Our engineers have identified the root cause of this issue and are actively working to restore service. We are currently executing remediation steps and will continue to provide updates here every 30 minutes until full service is restored.

3. 11. juni 2026 kl. 18.15 UTCidentified

   We want to start by offering our sincere apologies to every customer affected by today's disruption to the Anaplan Platform. We know your teams rely on Anaplan to do critical work. Our engineering team has identified the root cause and is fully focused on resolution. Active remediation steps are underway, and we are committed to keeping you informed with updates every 30 minutes — or sooner if there is meaningful progress to share.

4. 11. juni 2026 kl. 18.27 UTCmonitoring

   We are pleased to share that the core Anaplan Platform has successfully recovered and all primary services are fully operational. Our engineering teams are actively monitoring platform stability while corrective actions to address the underlying root cause continue to advance. We sincerely apologize for the disruption today and recognize that this has been a difficult week for many of our customers. Restoring your trust and ensuring platform stability remains our highest priority. Next update: In 30 minutes or sooner

5. 11. juni 2026 kl. 18.47 UTCmonitoring

   Our engineering team has successfully implemented a targeted infrastructure patch and completed a controlled failover to the updated version. All primary services are fully restored and accessible to customers. Our teams remain in active monitoring as we continue to validate the patch and advance corrective work across the remaining infrastructure. We do not anticipate further disruption at this time, and we will continue to monitor platform performance closely over the next several hours. We sincerely apologize for the impact today's incidents have had on your teams. A full incident summary will be published once our corrective actions are complete.

6. 12. juni 2026 kl. 00.30 UTCmonitoring

   The issue impacting access to the Anaplan Platform across all affected regions has been mitigated. The platform is stable and all services have returned to normal operation. Corrective measures to prevent recurrence are actively advancing and will continue to be applied to ensure this issue does not reoccur. We are continuing to monitor the platform to confirm stability. We do not anticipate any further customer impact from these activities. We appreciate your patience and partnership. If you have any questions or concerns, please do not hesitate to contact us at Anaplan Support.

7. 12. juni 2026 kl. 15.09 UTCresolved

   We would like to provide you with the latest update regarding the recent service disruption affecting our platform. Working in close collaboration with our vendor, our engineering team were able to identify a software bug in our network infrastructure that was causing temporary connection instability. To resolve the instability, we applied the fix recommended by the Vendor for the software bug, then successfully moved platform traffic to updated infrastructure at 18:17 UTC on 11 June. All connections stabilised with no disruption observed post the transition. Since then, the platform has remained stable and our engineering teams have continued to monitor this closely. This is our final update on this incident. We will provide a thorough Root Cause Analysis (RCA) within 7 business days. Thank you for your patience and understanding throughout this incident.

8. 19. juni 2026 kl. 14.38 UTCpostmortem

   **June 8–12, 2026 Platform Disruptions** On June 8, 2026, at 11:05 UTC, our monitoring detected a brief drop in incoming traffic across the Anaplan platform, with automated monitoring checks failing across all affected regions \(us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan\). Over the four days, a series of related disruptions affected the same regions. Customers experienced intermittent difficulties logging in, opening models, and running integrations. The platform was fully stabilized on June 11, 2026, at 18:12 UTC. These disruptions are linked to our previously communicated infrastructure modernization program. On the weekend of June 6, we migrated our control plane, the part of the platform that directs how traffic is routed between services. This was the most complex of the planned migration weekends, and it was completed successfully, as had the two previous migration weekends. The issues described in this report emerged in the days following that migration. This report covers the seven linked incidents that occurred between June 8 and June 11, 2026. **Root cause** As part of our infrastructure modernization program, on the weekend of June 6, we completed a successful migration of our control plane. In the days that followed, we observed two discrete network-hardware issues that interacted to drive these disruptions. _Issue 1: Media Access Control \(MAC\) flapping \(June 8–9\)_ Every device on a network has a MAC address, a unique hardware identifier that network switches use to route traffic to the correct destination. In our environment, the MAC addresses involved are virtual — assigned to logical network gateways rather than to fixed physical hardware — which allows them to legitimately move between hosts as part of normal operation. MAC flapping occurs when a switch sees the same MAC address appearing on two different physical ports in rapid succession, forcing it repeatedly to update its routing tables. This briefly slows or interrupts traffic. For customers, this surfaced as a brief, self-recovering instability. Short bursts of load and intermittent errors appeared and cleared on their own within minutes. The trigger for this behavior was the specific way live production traffic interacted with the new post-migration network. To resolve the issue, we scaled capacity, engaged our vendor, and deployed configuration changes to contain the impact. _Issue 2: network card driver defect \(June 10–11\)_ Once the first set of mitigations were in place, we identified a second issue: A defect in the network card driver, which is the software that controls how a network card sends and receives data. The defect affected fewer than 0.005% of the cards in our estate. Those cards failed randomly and unpredictably, dropping traffic while still appearing healthy to our monitoring systems. This is known as a "gray failure" condition, because the affected components don’t flag themselves as broken. The cards sat in the part of the network that routes traffic between the regions impacted. This resulted in failures that cascaded across the platform and drove disruptions on June 10 and June 11. The defect hadn't been observed in previous migrations or in any other environment, and there were no indicators in pre-deployment testing. The gray failure pattern was also what initially masked the defect as a load issue, until further investigation pointed us to the driver itself. We engaged our vendor, who confirmed the defect. Working closely with them, we rapidly prepared, tested, and deployed the patch to the affected hosts on the evening of June 11, UTC. After that, the platform stabilized. **Recovery** From the first occurrence on June 8 through to permanent resolution on June 11, our engineering team led a continuous, round-the-clock response, working closely with our vendor to identify, diagnose, and resolve the underlying defect. We deployed configuration mitigations, repeatedly rerouted traffic between hosts and across alternative network paths, and scaled out capacity to restore service to customers as quickly as possible while the underlying defect was being addressed. The seven linked incidents and their impact windows were: * **June 8, 2026, 11:00–11:20 UTC** — A short network disruption from the initial MAC flapping event caused intermittent login failures and slow page loads. For most customers, this appeared as a brief 6-minute blip and recovered automatically. Some basic authentication users experienced a longer impact and needed to start a new browser session, with full recovery by 11:20 UTC. * **June 9, 2026, 11:05–11:29 UTC** — A recurrence of the same MAC flapping condition caused a similar brief disruption. Again, most customers experienced only a short blip of around 6 minutes, with basic authentication users seeing a longer impact. We applied scaling changes to address the issue. * **June 10, 2026, 11:02–12:40 UTC** — Customers across all affected regions experienced a loss of access to the platform for approximately 98 minutes. We worked with the vendor and applied configuration changes to address the issue. * **June 10–11, 2026, 23:06–00:04 UTC** — A disruption of approximately 58 minutes, caused when the network card defect affected the backup host that traffic had been moved to. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 03:43–05:20 UTC** — A disruption of approximately 97 minutes, as the next backup host was affected by the same defect. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 11:10–13:02 UTC** — A further recurrence of the network traffic surge caused customers to experience slow or failed access to the platform. We restored service by applying an underlying configuration change. * **June 11, 2026, 17:04–17:48 UTC** — A final disruption of approximately 44 minutes during which we moved traffic to a host running the updated network card driver. The platform was fully stabilized at 18:12 UTC on June 11, 2026, once traffic was successfully moved to a host running the updated network card driver. We then applied the same update to a second host for resilience. Monitoring continued through to midday Friday before the incident was closed. CloudWorks™ experienced a backlog of queued jobs during and immediately after each disruption. Our engineering team scaled out CloudWorks capacity to accelerate processing, and the backlog was fully cleared shortly after each recovery. **Corrective and preventative actions** The control plane migration that preceded these disruptions was a one-time, foundational piece of work. The actions below reflect the learnings we are carrying forward from the event to further strengthen the platform. 1. The updated network card driver has been rolled out across all hosts matching the affected hardware profile, in every region. This removes the underlying defect from our infrastructure, even though it hasn't been observed in any other region. 2. The conditions that allowed MAC flapping to surface as customer-visible instability have been addressed at multiple layers. Configuration changes have been deployed in the affected regions. The underlying network configuration has been standardized across the wider production estate, and we have tuned the network behavior that triggered the initial event. 3. During the incident, our engineering team deployed dedicated alerting in real time for the specific network conditions causing the disruptions, enabling faster detection and intervention throughout the response. We are continuing to strengthen proactive monitoring and early-warning detection across post-release windows, so that emerging anomalies are surfaced and investigated before they escalate into customer-visible disruptions. 4. The remaining infrastructure update that supports the network card fix is being completed across our other environments. This brings the full benefit of the fix to every part of our infrastructure. **What's next** One final migration weekend is scheduled for June 20, 2026. After this, the migration phase of the infrastructure modernization program is complete. **Closing** We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

1. 11. juni 2026 kl. 04.32 UTCinvestigating

   We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

2. 11. juni 2026 kl. 04.58 UTCinvestigating

   Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

3. 11. juni 2026 kl. 05.03 UTCidentified

   The symptoms currently being observed are similar to the platform issue experienced earlier today. Our engineering and operations teams have been immediately mobilized and are actively diagnosing the root cause. We treat any recurrence with the utmost urgency and priority. We sincerely apologize for this disruption, we treat any recurrence with the utmost urgency and priority. We will provide another update in 30 minutes, or sooner as we obtain more actionable technical details.

4. 11. juni 2026 kl. 05.25 UTCidentified

   We are beginning to see signs of platform recovery, and primary services are starting to stabilize. As systems come back online, a backlog of queued CloudWorks jobs has accumulated and is currently processing. Our engineering teams are closely monitoring the stability of the platform and tracking the queue clearance velocity. We will provide our next update in 30 minutes, or sooner as we confirm continued stability.

5. 11. juni 2026 kl. 05.44 UTCmonitoring

   The platform has successfully recovered and is exhibiting stable performance. We are now focused on clearing the accumulated backlog of CloudWorks jobs. Our engineering teams are actively managing and verifying the processing queue to ensure all delayed jobs complete as quickly and safely as possible. We will continue to supervise the queue clearance and will provide our next update in 30 minutes, or sooner as we approach full restoration. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

6. 11. juni 2026 kl. 06.14 UTCmonitoring

   The platform remains stable and fully operational. We are continuing to process the remaining backlog of CloudWorks jobs. Our engineering teams are actively overseeing the processing queues to ensure all jobs complete successfully and system performance remains steady. We appreciate your continued patience as we work through this remaining queue. We will provide our next update in 30 minutes, or sooner as queue clearance nears completion.

7. 11. juni 2026 kl. 06.30 UTCmonitoring

   Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

8. 11. juni 2026 kl. 11.05 UTCmonitoring

   We want to keep you informed with the latest update on the service disruption affecting our platform. What we've done We have identified the source of the instability and are actively working to resolve it. Our engineering team, in collaboration with our vendor, has already implemented a configuration change that has reduced the frequency of errors. We are monitoring the platform closely and have seen improvement as a result. We are aware that some customers are experiencing delays and interruptions with their CloudWorks integrations as a direct result of this incident. Our engineering team is actively identifying and resolving any affected integration jobs. Current status The platform is operational. Integration processing is being actively monitored and remediated. We will not consider this incident closed until we are fully satisfied that the platform is stable, all integration jobs are running normally, and the risk of recurrence has been addressed. We will now provide updates every 2 hours, as our investigation progresses and we work with our Vendor. We understand the impact this has had on your operations and we appreciate your patience.

9. 11. juni 2026 kl. 14.01 UTCmonitoring

   We want to keep you informed with the latest update on the service disruption affecting our platform. After collaboration with our Vendor, we have identified two fixes to our underlying infrastructure. The first fix has now been implemented successfully without further disruption and initial monitoring is proving positive. We are continuing to liaise with our Vendor for the secondary fix, to ensure no further disruption is caused. The platform remains stable and all Cloudworks integrations are working as expected and the backlog has been cleared. The incident will remain open and we will provide updates every 2 hours or sooner, as we continue to investigate and have full resolution. We understand the impact this has had on your operations and we appreciate your patience

10. 11. juni 2026 kl. 14.31 UTCresolved

    We want to provide you with the latest update regarding the recent service disruption affecting our platform. All agreed-upon fixes have been successfully implemented across our underlying infrastructure. Our ongoing monitoring shows that system performance remains stable and positive. Our engineering teams will continue to monitor the platform closely to ensure continued stability. Additionally, we are conducting thorough Root Cause Analysis (RCA) and this will be provided within 7 business days. We sincerely understand the impact this disruption has had on your daily operations, and we deeply appreciate your patience and continued partnership as we work to ensure a reliable experience.

11. 19. juni 2026 kl. 15.02 UTCpostmortem

    **June 8–12, 2026 Platform Disruptions** On June 8, 2026, at 11:05 UTC, our monitoring detected a brief drop in incoming traffic across the Anaplan platform, with automated monitoring checks failing across all affected regions \(us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan\). Over the four days, a series of related disruptions affected the same regions. Customers experienced intermittent difficulties logging in, opening models, and running integrations. The platform was fully stabilized on June 11, 2026, at 18:12 UTC. These disruptions are linked to our previously communicated infrastructure modernization program. On the weekend of June 6, we migrated our control plane, the part of the platform that directs how traffic is routed between services. This was the most complex of the planned migration weekends, and it was completed successfully, as had the two previous migration weekends. The issues described in this report emerged in the days following that migration. This report covers the seven linked incidents that occurred between June 8 and June 11, 2026. **Root cause** As part of our infrastructure modernization program, on the weekend of June 6, we completed a successful migration of our control plane. In the days that followed, we observed two discrete network-hardware issues that interacted to drive these disruptions. _Issue 1: Media Access Control \(MAC\) flapping \(June 8–9\)_ Every device on a network has a MAC address, a unique hardware identifier that network switches use to route traffic to the correct destination. In our environment, the MAC addresses involved are virtual — assigned to logical network gateways rather than to fixed physical hardware — which allows them to legitimately move between hosts as part of normal operation. MAC flapping occurs when a switch sees the same MAC address appearing on two different physical ports in rapid succession, forcing it repeatedly to update its routing tables. This briefly slows or interrupts traffic. For customers, this surfaced as a brief, self-recovering instability. Short bursts of load and intermittent errors appeared and cleared on their own within minutes. The trigger for this behavior was the specific way live production traffic interacted with the new post-migration network. To resolve the issue, we scaled capacity, engaged our vendor, and deployed configuration changes to contain the impact. _Issue 2: network card driver defect \(June 10–11\)_ Once the first set of mitigations were in place, we identified a second issue: A defect in the network card driver, which is the software that controls how a network card sends and receives data. The defect affected fewer than 0.005% of the cards in our estate. Those cards failed randomly and unpredictably, dropping traffic while still appearing healthy to our monitoring systems. This is known as a "gray failure" condition, because the affected components don’t flag themselves as broken. The cards sat in the part of the network that routes traffic between the regions impacted. This resulted in failures that cascaded across the platform and drove disruptions on June 10 and June 11. The defect hadn't been observed in previous migrations or in any other environment, and there were no indicators in pre-deployment testing. The gray failure pattern was also what initially masked the defect as a load issue, until further investigation pointed us to the driver itself. We engaged our vendor, who confirmed the defect. Working closely with them, we rapidly prepared, tested, and deployed the patch to the affected hosts on the evening of June 11, UTC. After that, the platform stabilized. **Recovery** From the first occurrence on June 8 through to permanent resolution on June 11, our engineering team led a continuous, round-the-clock response, working closely with our vendor to identify, diagnose, and resolve the underlying defect. We deployed configuration mitigations, repeatedly rerouted traffic between hosts and across alternative network paths, and scaled out capacity to restore service to customers as quickly as possible while the underlying defect was being addressed. The seven linked incidents and their impact windows were: * **June 8, 2026, 11:00–11:20 UTC** — A short network disruption from the initial MAC flapping event caused intermittent login failures and slow page loads. For most customers, this appeared as a brief 6-minute blip and recovered automatically. Some basic authentication users experienced a longer impact and needed to start a new browser session, with full recovery by 11:20 UTC. * **June 9, 2026, 11:05–11:29 UTC** — A recurrence of the same MAC flapping condition caused a similar brief disruption. Again, most customers experienced only a short blip of around 6 minutes, with basic authentication users seeing a longer impact. We applied scaling changes to address the issue. * **June 10, 2026, 11:02–12:40 UTC** — Customers across all affected regions experienced a loss of access to the platform for approximately 98 minutes. We worked with the vendor and applied configuration changes to address the issue. * **June 10–11, 2026, 23:06–00:04 UTC** — A disruption of approximately 58 minutes, caused when the network card defect affected the backup host that traffic had been moved to. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 03:43–05:20 UTC** — A disruption of approximately 97 minutes, as the next backup host was affected by the same defect. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 11:10–13:02 UTC** — A further recurrence of the network traffic surge caused customers to experience slow or failed access to the platform. We restored service by applying an underlying configuration change. * **June 11, 2026, 17:04–17:48 UTC** — A final disruption of approximately 44 minutes during which we moved traffic to a host running the updated network card driver. The platform was fully stabilized at 18:12 UTC on June 11, 2026, once traffic was successfully moved to a host running the updated network card driver. We then applied the same update to a second host for resilience. Monitoring continued through to midday Friday before the incident was closed. CloudWorks™ experienced a backlog of queued jobs during and immediately after each disruption. Our engineering team scaled out CloudWorks capacity to accelerate processing, and the backlog was fully cleared shortly after each recovery. **Corrective and preventative actions** The control plane migration that preceded these disruptions was a one-time, foundational piece of work. The actions below reflect the learnings we are carrying forward from the event to further strengthen the platform. 1. The updated network card driver has been rolled out across all hosts matching the affected hardware profile, in every region. This removes the underlying defect from our infrastructure, even though it hasn't been observed in any other region. 2. The conditions that allowed MAC flapping to surface as customer-visible instability have been addressed at multiple layers. Configuration changes have been deployed in the affected regions. The underlying network configuration has been standardized across the wider production estate, and we have tuned the network behavior that triggered the initial event. 3. During the incident, our engineering team deployed dedicated alerting in real time for the specific network conditions causing the disruptions, enabling faster detection and intervention throughout the response. We are continuing to strengthen proactive monitoring and early-warning detection across post-release windows, so that emerging anomalies are surfaced and investigated before they escalate into customer-visible disruptions. 4. The remaining infrastructure update that supports the network card fix is being completed across our other environments. This brings the full benefit of the fix to every part of our infrastructure. **What's next** One final migration weekend is scheduled for June 20, 2026. After this, the migration phase of the infrastructure modernization program is complete. **Closing** We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

1. 10. juni 2026 kl. 23.14 UTCinvestigating

   We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

2. 10. juni 2026 kl. 23.34 UTCinvestigating

   Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

3. 11. juni 2026 kl. 00.07 UTCidentified

   We are starting to observe the first initial signs of platform recovery. Our engineering teams are proceeding with extreme caution and are closely monitoring system stability and telemetry as services begin to stabilize. We remain actively engaged in verifying that this early recovery is sustained. We will provide our next update in 30 minutes, or sooner if we detect any changes in performance.

4. 11. juni 2026 kl. 00.41 UTCidentified

   The core platform has successfully recovered, and all primary services are fully operational. We are currently processing a backlog of queued jobs within Cloudworks resulting from the incident. While this backlog is being processed, some customers may experience delays in processing times. We will continue to track performance and will provide our next update in 30 minutes, or sooner as the backlog clears.

5. 11. juni 2026 kl. 00.57 UTCmonitoring

   We are pleased to report that the CloudWorks backlog is actively processing, and we are now seeing jobs successfully and steadily completing. System throughput has returned to normal operational levels as the queue continues to clear. Our engineering teams remain focused on monitoring the queue velocity until the backlog is fully exhausted and all services have returned to a completely nominal state. We will provide our next update in 30 minutes, or sooner once queue clearance is complete.

6. 11. juni 2026 kl. 01.15 UTCmonitoring

   We are currently processing a backlog of queued jobs within Cloudworks for US1 and US2 region. While this backlog is being processed, some customers may experience delays in processing times. We will continue to track performance and will provide our next update in 30 minutes, or sooner as the backlog clears.

7. 11. juni 2026 kl. 01.52 UTCresolved

   We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

8. 19. juni 2026 kl. 15.00 UTCpostmortem

   **June 8–12, 2026 Platform Disruptions** On June 8, 2026, at 11:05 UTC, our monitoring detected a brief drop in incoming traffic across the Anaplan platform, with automated monitoring checks failing across all affected regions \(us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan\). Over the four days, a series of related disruptions affected the same regions. Customers experienced intermittent difficulties logging in, opening models, and running integrations. The platform was fully stabilized on June 11, 2026, at 18:12 UTC. These disruptions are linked to our previously communicated infrastructure modernization program. On the weekend of June 6, we migrated our control plane, the part of the platform that directs how traffic is routed between services. This was the most complex of the planned migration weekends, and it was completed successfully, as had the two previous migration weekends. The issues described in this report emerged in the days following that migration. This report covers the seven linked incidents that occurred between June 8 and June 11, 2026. **Root cause** As part of our infrastructure modernization program, on the weekend of June 6, we completed a successful migration of our control plane. In the days that followed, we observed two discrete network-hardware issues that interacted to drive these disruptions. _Issue 1: Media Access Control \(MAC\) flapping \(June 8–9\)_ Every device on a network has a MAC address, a unique hardware identifier that network switches use to route traffic to the correct destination. In our environment, the MAC addresses involved are virtual — assigned to logical network gateways rather than to fixed physical hardware — which allows them to legitimately move between hosts as part of normal operation. MAC flapping occurs when a switch sees the same MAC address appearing on two different physical ports in rapid succession, forcing it repeatedly to update its routing tables. This briefly slows or interrupts traffic. For customers, this surfaced as a brief, self-recovering instability. Short bursts of load and intermittent errors appeared and cleared on their own within minutes. The trigger for this behavior was the specific way live production traffic interacted with the new post-migration network. To resolve the issue, we scaled capacity, engaged our vendor, and deployed configuration changes to contain the impact. _Issue 2: network card driver defect \(June 10–11\)_ Once the first set of mitigations were in place, we identified a second issue: A defect in the network card driver, which is the software that controls how a network card sends and receives data. The defect affected fewer than 0.005% of the cards in our estate. Those cards failed randomly and unpredictably, dropping traffic while still appearing healthy to our monitoring systems. This is known as a "gray failure" condition, because the affected components don’t flag themselves as broken. The cards sat in the part of the network that routes traffic between the regions impacted. This resulted in failures that cascaded across the platform and drove disruptions on June 10 and June 11. The defect hadn't been observed in previous migrations or in any other environment, and there were no indicators in pre-deployment testing. The gray failure pattern was also what initially masked the defect as a load issue, until further investigation pointed us to the driver itself. We engaged our vendor, who confirmed the defect. Working closely with them, we rapidly prepared, tested, and deployed the patch to the affected hosts on the evening of June 11, UTC. After that, the platform stabilized. **Recovery** From the first occurrence on June 8 through to permanent resolution on June 11, our engineering team led a continuous, round-the-clock response, working closely with our vendor to identify, diagnose, and resolve the underlying defect. We deployed configuration mitigations, repeatedly rerouted traffic between hosts and across alternative network paths, and scaled out capacity to restore service to customers as quickly as possible while the underlying defect was being addressed. The seven linked incidents and their impact windows were: * **June 8, 2026, 11:00–11:20 UTC** — A short network disruption from the initial MAC flapping event caused intermittent login failures and slow page loads. For most customers, this appeared as a brief 6-minute blip and recovered automatically. Some basic authentication users experienced a longer impact and needed to start a new browser session, with full recovery by 11:20 UTC. * **June 9, 2026, 11:05–11:29 UTC** — A recurrence of the same MAC flapping condition caused a similar brief disruption. Again, most customers experienced only a short blip of around 6 minutes, with basic authentication users seeing a longer impact. We applied scaling changes to address the issue. * **June 10, 2026, 11:02–12:40 UTC** — Customers across all affected regions experienced a loss of access to the platform for approximately 98 minutes. We worked with the vendor and applied configuration changes to address the issue. * **June 10–11, 2026, 23:06–00:04 UTC** — A disruption of approximately 58 minutes, caused when the network card defect affected the backup host that traffic had been moved to. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 03:43–05:20 UTC** — A disruption of approximately 97 minutes, as the next backup host was affected by the same defect. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 11:10–13:02 UTC** — A further recurrence of the network traffic surge caused customers to experience slow or failed access to the platform. We restored service by applying an underlying configuration change. * **June 11, 2026, 17:04–17:48 UTC** — A final disruption of approximately 44 minutes during which we moved traffic to a host running the updated network card driver. The platform was fully stabilized at 18:12 UTC on June 11, 2026, once traffic was successfully moved to a host running the updated network card driver. We then applied the same update to a second host for resilience. Monitoring continued through to midday Friday before the incident was closed. CloudWorks™ experienced a backlog of queued jobs during and immediately after each disruption. Our engineering team scaled out CloudWorks capacity to accelerate processing, and the backlog was fully cleared shortly after each recovery. **Corrective and preventative actions** The control plane migration that preceded these disruptions was a one-time, foundational piece of work. The actions below reflect the learnings we are carrying forward from the event to further strengthen the platform. 1. The updated network card driver has been rolled out across all hosts matching the affected hardware profile, in every region. This removes the underlying defect from our infrastructure, even though it hasn't been observed in any other region. 2. The conditions that allowed MAC flapping to surface as customer-visible instability have been addressed at multiple layers. Configuration changes have been deployed in the affected regions. The underlying network configuration has been standardized across the wider production estate, and we have tuned the network behavior that triggered the initial event. 3. During the incident, our engineering team deployed dedicated alerting in real time for the specific network conditions causing the disruptions, enabling faster detection and intervention throughout the response. We are continuing to strengthen proactive monitoring and early-warning detection across post-release windows, so that emerging anomalies are surfaced and investigated before they escalate into customer-visible disruptions. 4. The remaining infrastructure update that supports the network card fix is being completed across our other environments. This brings the full benefit of the fix to every part of our infrastructure. **What's next** One final migration weekend is scheduled for June 20, 2026. After this, the migration phase of the infrastructure modernization program is complete. **Closing** We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

1. 10. juni 2026 kl. 11.11 UTCinvestigating

   We are currently investigating an active incident that may affect Basic Authentication access. If you encounter issues when attempting to access the platform please use the following workaround while we resolve the issue: - Close your current session— Close the active browser tab or open a new Incognito/Private window. - Re-authenticate— Navigate to the portal and log in again with your credentials to establish a fresh session. We are actively monitoring the platform and will continue to do so until the issue is fully resolved. If you are still experiencing difficulties or have any questions, please reach out to Anaplan Support

2. 10. juni 2026 kl. 11.35 UTCinvestigating

   Since our last update, we have detected a further degradation in general platform performance. Our engineering teams are actively investigating the root cause with the highest priority, and we will provide further updates as the situation develops Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

3. 10. juni 2026 kl. 12.01 UTCinvestigating

   Following our previous notification, the ongoing performance issues have escalated, resulting in broader platform-wide degradation. Our senior engineering teams have successfully identified the root cause of the issue and are currently executing targeted remediation steps to restore normal operations as our absolute highest priority. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

4. 10. juni 2026 kl. 12.34 UTCinvestigating

   Our engineering teams continue to actively investigate the incident while simultaneously implementing targeted remediation steps to stabilize the platform. We are closely monitoring the system's response to these actions and will provide our updates every 30 minutes as we work to resolve this issue as quickly as possible.

5. 10. juni 2026 kl. 12.51 UTCidentified

   The general platform has successfully recovered and is operating normally; however, we are actively addressing a residual issue impacting Cloudworks that is currently preventing integration jobs from completing. Our technical teams remain focused on resolving this remaining component to restore full service across all integrations as quickly as possible. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

6. 10. juni 2026 kl. 13.18 UTCidentified

   We are pleased to report that integration jobs are now successfully completing, and our systems are actively processing the accumulated backlog across all regions. To accelerate this recovery, we have scaled out our service capacity, with a particular focus on the us7: Cloud - US region to expedite the clearance of its more significant backlog. We will provide further updates in 30 minutes or upon resolution.

7. 10. juni 2026 kl. 13.27 UTCidentified

   We are pleased to report that integration processing has returned to normal operational levels across all global regions, with the sole exception of us7: Cloud - US. The us7: Cloud - US region continues to steadily work through its remaining queue utilizing our expanded capacity, and we are monitoring progress closely to ensure a complete return to baseline performance. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

8. 10. juni 2026 kl. 13.55 UTCidentified

   As we continue our active recovery efforts, we have identified localized capacity constraints in the us1: Data Center - US East region that may intermittently affect customers attempting to load models. Our engineering teams are addressing this resource bottleneck to restore full service. The CloudWorks backlog in us7: Cloud - US has finished processing, and the service has returned to normal operations. While an estimated time to resolution is not yet established, our teams are treating this with the highest urgency. We will provide our next update in 30 minutes, or sooner if a resolution is reached.

9. 10. juni 2026 kl. 14.33 UTCinvestigating

   Our investigation indicates that the backend connectivity issues in US1, stemming from a localized network disruption, are specifically isolated to the loading of large models in excess of 200GB. Customers attempting to load smaller models should experience normal performance and remain unaffected as our network engineering teams actively work to restore stable pathways for larger model payloads. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

10. 10. juni 2026 kl. 15.04 UTCidentified

    Our network engineering teams continue to actively implement remediation steps to address the localized network issue in the us1: Data Center - US East region. We remain focused on resolving the backend connectivity disruptions affecting the loading of larger models, while smaller models continue to perform normally. We are closely monitoring system behavior as we deploy these targeted fixes and will provide our next update in 30 minutes, or sooner if significant progress is made. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

11. 10. juni 2026 kl. 15.27 UTCmonitoring

    Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

12. 10. juni 2026 kl. 16.35 UTCresolved

    We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

13. 19. juni 2026 kl. 14.58 UTCpostmortem

    **June 8–12, 2026 Platform Disruptions** On June 8, 2026, at 11:05 UTC, our monitoring detected a brief drop in incoming traffic across the Anaplan platform, with automated monitoring checks failing across all affected regions \(us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan\). Over the four days, a series of related disruptions affected the same regions. Customers experienced intermittent difficulties logging in, opening models, and running integrations. The platform was fully stabilized on June 11, 2026, at 18:12 UTC. These disruptions are linked to our previously communicated infrastructure modernization program. On the weekend of June 6, we migrated our control plane, the part of the platform that directs how traffic is routed between services. This was the most complex of the planned migration weekends, and it was completed successfully, as had the two previous migration weekends. The issues described in this report emerged in the days following that migration. This report covers the seven linked incidents that occurred between June 8 and June 11, 2026. **Root cause** As part of our infrastructure modernization program, on the weekend of June 6, we completed a successful migration of our control plane. In the days that followed, we observed two discrete network-hardware issues that interacted to drive these disruptions. _Issue 1: Media Access Control \(MAC\) flapping \(June 8–9\)_ Every device on a network has a MAC address, a unique hardware identifier that network switches use to route traffic to the correct destination. In our environment, the MAC addresses involved are virtual — assigned to logical network gateways rather than to fixed physical hardware — which allows them to legitimately move between hosts as part of normal operation. MAC flapping occurs when a switch sees the same MAC address appearing on two different physical ports in rapid succession, forcing it repeatedly to update its routing tables. This briefly slows or interrupts traffic. For customers, this surfaced as a brief, self-recovering instability. Short bursts of load and intermittent errors appeared and cleared on their own within minutes. The trigger for this behavior was the specific way live production traffic interacted with the new post-migration network. To resolve the issue, we scaled capacity, engaged our vendor, and deployed configuration changes to contain the impact. _Issue 2: network card driver defect \(June 10–11\)_ Once the first set of mitigations were in place, we identified a second issue: A defect in the network card driver, which is the software that controls how a network card sends and receives data. The defect affected fewer than 0.005% of the cards in our estate. Those cards failed randomly and unpredictably, dropping traffic while still appearing healthy to our monitoring systems. This is known as a "gray failure" condition, because the affected components don’t flag themselves as broken. The cards sat in the part of the network that routes traffic between the regions impacted. This resulted in failures that cascaded across the platform and drove disruptions on June 10 and June 11. The defect hadn't been observed in previous migrations or in any other environment, and there were no indicators in pre-deployment testing. The gray failure pattern was also what initially masked the defect as a load issue, until further investigation pointed us to the driver itself. We engaged our vendor, who confirmed the defect. Working closely with them, we rapidly prepared, tested, and deployed the patch to the affected hosts on the evening of June 11, UTC. After that, the platform stabilized. **Recovery** From the first occurrence on June 8 through to permanent resolution on June 11, our engineering team led a continuous, round-the-clock response, working closely with our vendor to identify, diagnose, and resolve the underlying defect. We deployed configuration mitigations, repeatedly rerouted traffic between hosts and across alternative network paths, and scaled out capacity to restore service to customers as quickly as possible while the underlying defect was being addressed. The seven linked incidents and their impact windows were: * **June 8, 2026, 11:00–11:20 UTC** — A short network disruption from the initial MAC flapping event caused intermittent login failures and slow page loads. For most customers, this appeared as a brief 6-minute blip and recovered automatically. Some basic authentication users experienced a longer impact and needed to start a new browser session, with full recovery by 11:20 UTC. * **June 9, 2026, 11:05–11:29 UTC** — A recurrence of the same MAC flapping condition caused a similar brief disruption. Again, most customers experienced only a short blip of around 6 minutes, with basic authentication users seeing a longer impact. We applied scaling changes to address the issue. * **June 10, 2026, 11:02–12:40 UTC** — Customers across all affected regions experienced a loss of access to the platform for approximately 98 minutes. We worked with the vendor and applied configuration changes to address the issue. * **June 10–11, 2026, 23:06–00:04 UTC** — A disruption of approximately 58 minutes, caused when the network card defect affected the backup host that traffic had been moved to. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 03:43–05:20 UTC** — A disruption of approximately 97 minutes, as the next backup host was affected by the same defect. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 11:10–13:02 UTC** — A further recurrence of the network traffic surge caused customers to experience slow or failed access to the platform. We restored service by applying an underlying configuration change. * **June 11, 2026, 17:04–17:48 UTC** — A final disruption of approximately 44 minutes during which we moved traffic to a host running the updated network card driver. The platform was fully stabilized at 18:12 UTC on June 11, 2026, once traffic was successfully moved to a host running the updated network card driver. We then applied the same update to a second host for resilience. Monitoring continued through to midday Friday before the incident was closed. CloudWorks™ experienced a backlog of queued jobs during and immediately after each disruption. Our engineering team scaled out CloudWorks capacity to accelerate processing, and the backlog was fully cleared shortly after each recovery. **Corrective and preventative actions** The control plane migration that preceded these disruptions was a one-time, foundational piece of work. The actions below reflect the learnings we are carrying forward from the event to further strengthen the platform. 1. The updated network card driver has been rolled out across all hosts matching the affected hardware profile, in every region. This removes the underlying defect from our infrastructure, even though it hasn't been observed in any other region. 2. The conditions that allowed MAC flapping to surface as customer-visible instability have been addressed at multiple layers. Configuration changes have been deployed in the affected regions. The underlying network configuration has been standardized across the wider production estate, and we have tuned the network behavior that triggered the initial event. 3. During the incident, our engineering team deployed dedicated alerting in real time for the specific network conditions causing the disruptions, enabling faster detection and intervention throughout the response. We are continuing to strengthen proactive monitoring and early-warning detection across post-release windows, so that emerging anomalies are surfaced and investigated before they escalate into customer-visible disruptions. 4. The remaining infrastructure update that supports the network card fix is being completed across our other environments. This brings the full benefit of the fix to every part of our infrastructure. **What's next** One final migration weekend is scheduled for June 20, 2026. After this, the migration phase of the infrastructure modernization program is complete. **Closing** We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

1. 10. juni 2026 kl. 09.48 UTCinvestigating

   We are currently investigating an issue impacting customers’ ability to run Cloudworks integrations. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

2. 10. juni 2026 kl. 10.15 UTCmonitoring

   Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

3. 10. juni 2026 kl. 10.42 UTCresolved

   We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

4. 19. juni 2026 kl. 15.12 UTCpostmortem

   **Introduction**   On June 10, 2026, at 09:48 UTC, customers in us1: Data Center - US East experienced slight delays in the processing and successful completion of CloudWorks™ integrations.   **Root cause**  During routine database patching on June 10, all regions completed without issue except for the us1: Data Center - US East region, where CloudWorks encountered an unexpected loss of database connectivity. This caused deadlocks within the scheduler service.  Our investigation determined that one remote connection had been dropped while a second remained active, resulting in connection conflicts and errors. The issue was remediated by performing a rolling restart of the scheduler service and clearing the database rules.  **Recovery**  Upon identifying the issue, our engineering team acted quickly to initiate a rolling restart of the scheduler service across the affected region. To fully resolve the connection conflict and errors, the team cleared the internal routing and caching rules associated with the database gateway. Following this action, the database connection errors ceased immediately, and manual validation confirmed that integration scheduling had been fully restored. The issue was completely resolved by 10:42 UTC.  **Corrective and preventative actions**  We are implementing the following actions to prevent recurrence and improve service reliability:  * We are developing enhanced system alerts to immediately detect database connectivity issues and abnormal error volumes.  * We are working to replicate the scenario in non-production environments to strengthen CloudWorks' ability to recover from database disconnections.   * We are currently reviewing the errors encountered, along with the relevant system settings, to determine whether any changes can be implemented to better handle this type of issue in the future.  * We are reviewing and optimizing the capacity and sizing of our integration services across all regions to ensure they are robust and resilient.  * We are establishing more detailed incident response runbooks and centralizing triage procedures to accelerate resolution of similar issues.   * We are strengthening our platform observability and system telemetry to improve our diagnostic capabilities and detect connection issues more rapidly.  We apologize for any impact this issue may have had on your business operations.` `We are continuously strengthening our systems and procedures to ensure we avoid future disruptions to your business and users.  If you have further questions or concerns, please visit our [Support website](https://www.google.com/url?q=https%3A%2F%2Fsupport.anaplan.com%2F). We appreciate your patience during this incident and value the trust you place in Anaplan.

1. 9. juni 2026 kl. 11.14 UTCinvestigating

   We are currently investigating an active incident that may affect Basic Authentication access. If you encounter errors when attempting to log in please do the following: - Close your current session— Close the active browser tab or open a new Incognito/Private window. - Re-authenticate— Navigate to the portal and log in again with your credentials to establish a fresh session. We are actively monitoring the platform and will continue to do so until the issue is fully resolved. If you are still experiencing difficulties or have any questions, please reach out to Anaplan Support We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

2. 9. juni 2026 kl. 11.28 UTCresolved

   We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

3. 19. juni 2026 kl. 14.45 UTCpostmortem

   **June 8–12, 2026 Platform Disruptions** On June 8, 2026, at 11:05 UTC, our monitoring detected a brief drop in incoming traffic across the Anaplan platform, with automated monitoring checks failing across all affected regions \(us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan\). Over the four days, a series of related disruptions affected the same regions. Customers experienced intermittent difficulties logging in, opening models, and running integrations. The platform was fully stabilized on June 11, 2026, at 18:12 UTC. These disruptions are linked to our previously communicated infrastructure modernization program. On the weekend of June 6, we migrated our control plane, the part of the platform that directs how traffic is routed between services. This was the most complex of the planned migration weekends, and it was completed successfully, as had the two previous migration weekends. The issues described in this report emerged in the days following that migration. This report covers the seven linked incidents that occurred between June 8 and June 11, 2026. **Root cause** As part of our infrastructure modernization program, on the weekend of June 6, we completed a successful migration of our control plane. In the days that followed, we observed two discrete network-hardware issues that interacted to drive these disruptions. _Issue 1: Media Access Control \(MAC\) flapping \(June 8–9\)_ Every device on a network has a MAC address, a unique hardware identifier that network switches use to route traffic to the correct destination. In our environment, the MAC addresses involved are virtual — assigned to logical network gateways rather than to fixed physical hardware — which allows them to legitimately move between hosts as part of normal operation. MAC flapping occurs when a switch sees the same MAC address appearing on two different physical ports in rapid succession, forcing it repeatedly to update its routing tables. This briefly slows or interrupts traffic. For customers, this surfaced as a brief, self-recovering instability. Short bursts of load and intermittent errors appeared and cleared on their own within minutes. The trigger for this behavior was the specific way live production traffic interacted with the new post-migration network. To resolve the issue, we scaled capacity, engaged our vendor, and deployed configuration changes to contain the impact. _Issue 2: network card driver defect \(June 10–11\)_ Once the first set of mitigations were in place, we identified a second issue: A defect in the network card driver, which is the software that controls how a network card sends and receives data. The defect affected fewer than 0.005% of the cards in our estate. Those cards failed randomly and unpredictably, dropping traffic while still appearing healthy to our monitoring systems. This is known as a "gray failure" condition, because the affected components don’t flag themselves as broken. The cards sat in the part of the network that routes traffic between the regions impacted. This resulted in failures that cascaded across the platform and drove disruptions on June 10 and June 11. The defect hadn't been observed in previous migrations or in any other environment, and there were no indicators in pre-deployment testing. The gray failure pattern was also what initially masked the defect as a load issue, until further investigation pointed us to the driver itself. We engaged our vendor, who confirmed the defect. Working closely with them, we rapidly prepared, tested, and deployed the patch to the affected hosts on the evening of June 11, UTC. After that, the platform stabilized. **Recovery** From the first occurrence on June 8 through to permanent resolution on June 11, our engineering team led a continuous, round-the-clock response, working closely with our vendor to identify, diagnose, and resolve the underlying defect. We deployed configuration mitigations, repeatedly rerouted traffic between hosts and across alternative network paths, and scaled out capacity to restore service to customers as quickly as possible while the underlying defect was being addressed. The seven linked incidents and their impact windows were: * **June 8, 2026, 11:00–11:20 UTC** — A short network disruption from the initial MAC flapping event caused intermittent login failures and slow page loads. For most customers, this appeared as a brief 6-minute blip and recovered automatically. Some basic authentication users experienced a longer impact and needed to start a new browser session, with full recovery by 11:20 UTC. * **June 9, 2026, 11:05–11:29 UTC** — A recurrence of the same MAC flapping condition caused a similar brief disruption. Again, most customers experienced only a short blip of around 6 minutes, with basic authentication users seeing a longer impact. We applied scaling changes to address the issue. * **June 10, 2026, 11:02–12:40 UTC** — Customers across all affected regions experienced a loss of access to the platform for approximately 98 minutes. We worked with the vendor and applied configuration changes to address the issue. * **June 10–11, 2026, 23:06–00:04 UTC** — A disruption of approximately 58 minutes, caused when the network card defect affected the backup host that traffic had been moved to. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 03:43–05:20 UTC** — A disruption of approximately 97 minutes, as the next backup host was affected by the same defect. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 11:10–13:02 UTC** — A further recurrence of the network traffic surge caused customers to experience slow or failed access to the platform. We restored service by applying an underlying configuration change. * **June 11, 2026, 17:04–17:48 UTC** — A final disruption of approximately 44 minutes during which we moved traffic to a host running the updated network card driver. The platform was fully stabilized at 18:12 UTC on June 11, 2026, once traffic was successfully moved to a host running the updated network card driver. We then applied the same update to a second host for resilience. Monitoring continued through to midday Friday before the incident was closed. CloudWorks™ experienced a backlog of queued jobs during and immediately after each disruption. Our engineering team scaled out CloudWorks capacity to accelerate processing, and the backlog was fully cleared shortly after each recovery. **Corrective and preventative actions** The control plane migration that preceded these disruptions was a one-time, foundational piece of work. The actions below reflect the learnings we are carrying forward from the event to further strengthen the platform. 1. The updated network card driver has been rolled out across all hosts matching the affected hardware profile, in every region. This removes the underlying defect from our infrastructure, even though it hasn't been observed in any other region. 2. The conditions that allowed MAC flapping to surface as customer-visible instability have been addressed at multiple layers. Configuration changes have been deployed in the affected regions. The underlying network configuration has been standardized across the wider production estate, and we have tuned the network behavior that triggered the initial event. 3. During the incident, our engineering team deployed dedicated alerting in real time for the specific network conditions causing the disruptions, enabling faster detection and intervention throughout the response. We are continuing to strengthen proactive monitoring and early-warning detection across post-release windows, so that emerging anomalies are surfaced and investigated before they escalate into customer-visible disruptions. 4. The remaining infrastructure update that supports the network card fix is being completed across our other environments. This brings the full benefit of the fix to every part of our infrastructure. **What's next** One final migration weekend is scheduled for June 20, 2026. After this, the migration phase of the infrastructure modernization program is complete. **Closing** We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

1. 8. juni 2026 kl. 13.25 UTCinvestigating

   We are currently investigating an issue impacting customers’ ability to run Cloudworks integrations. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

2. 8. juni 2026 kl. 13.52 UTCinvestigating

   Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to full resolution.  Access to the UI has been restored and we are currently investigating the degradation to integrations. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

3. 8. juni 2026 kl. 15.18 UTCinvestigating

   We are currently investigating an issue impacting impacting Cloudworks. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

4. 8. juni 2026 kl. 15.31 UTCmonitoring

   Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

5. 8. juni 2026 kl. 15.51 UTCresolved

   We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

6. 17. juni 2026 kl. 17.08 UTCpostmortem

   **Introduction**  On June 8, 2026, at 13:14 UTC, customers in our ap1: Cloud - Japan, eu1: Data Center - Netherlands, eu2: Data Center - Germany, us2: Data Center - US West, us5: Cloud - US East, us7: Cloud - US, and eu4: Cloud - Europe regions experienced delays and difficulties accessing the CloudWorks™ user interface. During this period, users experienced slow UI access and a temporary inability to create new integrations or run certain scheduled jobs. Existing workflows were unaffected, although some experienced minor delays in completion.  **Root cause**  The root cause of this incident was an incorrect configuration setting where certain backend components did not automatically pick up updated hostname configurations following a scheduled system migration. Consequently, these components continued to attempt connections using the outdated configuration, leading to connection failures. This prevented users from accessing the user interface and successfully initiating new integration runs. The issue was resolved by reloading the updated configuration on the affected services.  **Recovery**  Our engineering team identified the issue and took immediate action. We initiated a rolling restart of the job management service across the affected regions, which restored user interface access. To fully resolve the connection errors, the engineering team performed a comprehensive restart of all related service components in every affected region, forcing them to load the updated database configurations. Following these restarts, database connection errors immediately ceased, and manual validation confirmed that both user-interface access and integration scheduling were fully restored and functioning normally. By 15:52 UTC, the issue was fully resolved.  **Corrective and preventative actions**  We are implementing the following actions to prevent recurrence and improve service reliability:  * We are developing enhanced system alerts to immediately detect database connectivity issues and abnormal error volumes.  * We are reviewing and optimizing the capacity and sizing of our integration services across all regions to ensure they are robust and resilient.  * We are establishing more detailed incident response runbooks and centralizing triage procedures to accelerate resolution of similar configuration mismatches.  * We are strengthening our platform observability and system telemetry to improve our diagnostic capabilities and detect connection issues more rapidly.  * We are refining our strategy and APIs to proactively detect and manage delayed integration workflows.   We apologize for any impact this issue may have had on your business operations. We are continuously strengthening our systems and procedures to ensure we avoid future disruptions to your business and users.  If you have further questions or concerns, please visit our [Support website](https://www.google.com/url?q=https%3A%2F%2Fsupport.anaplan.com%2F). We appreciate your patience during this incident and value the trust you place in Anaplan.