Staffbase driftsforstyrrelser

1. 4. september 2026 kl. 12.06 UTCidentified

   Nogle kunder kan opleve forsinket levering af e-mails sendt fra Staffbase (e-mail moderne og anmeldelse e-mails). Vores undersøgelse bekræftede, at e-mails blev sendt med succes fra vores side; forsinkelsen skyldes modtagerens mail udbyder, Microsoft 365 / Outlook, midlertidigt udsætte indgående meddelelser i en periode med høj belastning på deres ende. Der er ikke brug for handling. Forsinkede e-mails skal ankomme som den modtagende mail server fungerer gennem sin kø. På grund af dette problem, nogle kunder med Microsoft 365 / Outlook måske ikke være i stand til at modtage svar på vores Support Billetter lige nu, så er du velkommen til at bruge vores billet portal via support.staff base.com. Tak for Deres tålmodighed, mens dette behandles. Hvis du har spørgsmål vedrørende dette emne, bedes du kontakte vores supporthold på support @ staff base.com.

2. 4. september 2026 kl. 15.05 UTCresolved

   Problemet er løst. Vi undskylder for den ulejlighed, det har forårsaget. Kontakt os venligst på [support @ staff base.com] (https: / / support @ staff base.com), hvis du stadig har problemer. Vi hjælper gerne!

3. 4. september 2026 kl. 15.08 UTCresolved

   Problemet er løst. Vi undskylder for den ulejlighed, det har forårsaget. Kontakt os på support @ bemande.com, hvis du stadig har problemer. Vi hjælper gerne!

Automatisk oversat fra den officielle hændelsesopdatering.

1. 4. september 2026 kl. 11.47 UTCidentified

   Nogle kunder kan opleve forsinket levering af e-mails sendt fra Staffbase (e-mail moderne og anmeldelse e-mails). Vores undersøgelse bekræftede, at e-mails blev sendt med succes fra vores side; forsinkelsen skyldes modtagerens mail udbyder, Microsoft 365 / Outlook, midlertidigt udsætte indgående meddelelser i en periode med høj belastning på deres ende. Der er ikke brug for handling. Forsinkede e-mails skal ankomme som den modtagende mail server fungerer gennem sin kø. På grund af dette problem, nogle kunder med Microsoft 365 / Outlook måske ikke være i stand til at modtage svar på vores Support Billetter lige nu, så er du velkommen til at bruge vores billet portal via support.staff base.com. Tak for Deres tålmodighed, mens dette behandles. Hvis du har spørgsmål vedrørende dette emne, bedes du kontakte vores supporthold på support @ staff base.com.

2. 4. september 2026 kl. 15.07 UTCresolved

   Problemet er løst. Vi undskylder for den ulejlighed, det har forårsaget. Kontakt os på support @ bemande.com, hvis du stadig har problemer. Vi hjælper gerne!

Automatisk oversat fra den officielle hændelsesopdatering.

1. 3. september 2026 kl. 09.54 UTCresolved

   Mellem 15: 15 og 15: 30 UTC (17: 15- 17: 30 CEST) den 2. september oplevede nogle kunder forhøjede fejlrater og langsomme resultater, der påvirkede både vores EU- og US- hostede miljøer. Dette var forårsaget af en intern implementering ændring og løst på egen hånd inden for omkring femten minutter, når trafikken blev omdirigeret tilbage til normal. Vi beklager forstyrrelsen. Hvis du stadig ser nogen relaterede spørgsmål, bedes du kontakte os på support @ bemanding base.com - vi er glade for at hjælpe.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 3. september 2026 kl. 10.09 UTCresolved

   Mellem 15: 15 og 15: 30 UTC (17: 15- 17: 30 CEST) den 2. september oplevede nogle kunder forhøjede fejlrater og langsomme resultater, der påvirkede både vores EU- og US- hostede miljøer. Dette var forårsaget af en intern implementering ændring og løst på egen hånd inden for omkring femten minutter, når trafikken blev omdirigeret tilbage til normal. Vi beklager forstyrrelsen. Hvis du stadig ser nogen relaterede spørgsmål, bedes du kontakte os på support @ bemanding base.com - vi er glade for at hjælpe.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 31. august 2026 kl. 10.08 UTCinvestigating

   Påvirkede funktion: Staffbase AI (Navigator, Podcast, E-mail / side generation) Nogle kunder kan opleve problemer med vores AI-værktøjer og støder på fejlmeddelelser, når de interagerer med dem. Vores hold undersøger og vil arbejde på at løse dette så hurtigt som muligt. Vi deler snart mere information. Vi undskylder ulejligheden. Hvis du har spørgsmål vedrørende dette emne, bedes du kontakte vores supporthold på support @ staff base.com.

2. 31. august 2026 kl. 11.06 UTCmonitoring

   Vi har truffet foranstaltninger til at løse problemet og genoprette den fulde funktionalitet af alle AI værktøjer / dele i Staffbase. Vi vil fortsat overvåge systemerne, indtil vi er sikre på, at problemet er løst fuldt ud.

3. 31. august 2026 kl. 13.10 UTCresolved

   Denne hændelse er blevet løst. Navigatoren og andre berørte AI-funktioner er fuldt funktionsdygtige igen. Vi beklager de problemer, det har skabt. Kontakt os venligst på support @ bemanding base.com hvis du oplever yderligere problemer. Vi hjælper gerne!

Automatisk oversat fra den officielle hændelsesopdatering.

1. 31. august 2026 kl. 09.57 UTCinvestigating

   Påvirkede funktion: Staffbase AI (Navigator, Podcast, E-mail / side generation) Nogle kunder kan opleve problemer med vores AI-værktøjer og støder på fejlmeddelelser, når de interagerer med dem. Vores hold undersøger og vil arbejde på at løse dette så hurtigt som muligt. Vi deler snart mere information. Vi undskylder ulejligheden. Hvis du har spørgsmål vedrørende dette emne, bedes du kontakte vores supporthold på support @ staff base.com.

2. 31. august 2026 kl. 10.18 UTCmonitoring

   Vi har truffet foranstaltninger til at løse problemet og genoprette den fulde funktionalitet af alle AI værktøjer / dele i Staffbase. Vi vil fortsat overvåge systemerne, indtil vi er sikre på, at problemet er løst fuldt ud.

3. 31. august 2026 kl. 12.09 UTCresolved

   Denne hændelse er blevet løst. Navigatoren og andre berørte AI-funktioner er fuldt funktionsdygtige igen. Vi beklager de problemer, det har skabt. Kontakt os venligst på support @ bemanding base.com hvis du oplever yderligere problemer. Vi hjælper gerne!

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. juli 2026 kl. 15.06 UTCmonitoring

   Opdatering: Vi har indsat en rettelse til problemet. Funktionaliteten er blevet genoprettet, og vi overvåger nu alle miljøer for at bekræfte det. Vi vil sende en endelig opdatering, når overvågningen bekræfter fuld stabilitet.

2. 14. juli 2026 kl. 15.06 UTCinvestigating

   Nogle brugere kan støde på et problem, hvor formularer, sider eller andet indhold undlader at indlæse og i stedet vise fejlmeddelelsen "error.unknown.title". Vores hold undersøger og vil arbejde på at løse dette så hurtigt som muligt. Vi deler snart mere information. Vi undskylder ulejligheden. Hvis du har spørgsmål vedrørende dette emne, bedes du kontakte os på support @ bemanding base.com.

3. 15. juli 2026 kl. 08.11 UTCresolved

   Problemet er løst. Vi undskylder for den ulejlighed, det har forårsaget. Kontakt os på support @ bemande.com, hvis du stadig har problemer. Vi hjælper gerne!

4. 15. juli 2026 kl. 08.11 UTCmonitoring

   Vi fortsætter med at overvåge for yderligere spørgsmål.

5. 27. juli 2026 kl. 16.10 UTCresolved

   * * Oversigt * * Den 14. juli 2026, mellem 3: 50 PM og 4: 59 PM\ (CEST\), kunder på tværs af alle systemer oplevede serviceafbrydelser påvirker flere platform funktioner. Vores hold har med succes identificeret årsagen og genoprettet fuld service funktionalitet. * * Hvad der skete * * En nylig opdatering indført en godkendelse konfiguration problem, der forårsagede flere platform funktioner, herunder sideindlæsning, meddelelser, e-mail, analytics, og link sporing, at returnere fejl. Vores team identificerede problemet og løste det, genoprette normale operationer på tværs af alle berørte systemer. * * Indvirkning * * Mellem 3: 50 PM og 4: 59 PM\ (CEST\) den 14. juli 2026, kunder på det europæiske, Amerika, og Asien / Stillehavet Systems kan have oplevet fejl adgang sider, meddelelser, e-mail, analytics, og link tracking funktioner. * * Fremtidige forbedringer * * Vi vil gennemføre yderligere kontroller for driften af den berørte service komponent og forbedre vores evne til at opdage og løse lignende spørgsmål hurtigere i fremtiden. Tak for Deres tålmodighed og forståelse, mens vi arbejder på at forbedre vores tjenester og forhindre fremtidige hændelser. Hvis du har spørgsmål eller bekymringer, så tøv ikke med at kontakte vores kundesupport team på [support @ bemande.com] (mailto: support @ bemande.com).

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. juli 2026 kl. 14.10 UTCinvestigating

   Nogle brugere kan støde på et problem, hvor formularer, sider eller andet indhold undlader at indlæse og i stedet vise fejlmeddelelsen "error.unknown.title". Vores hold undersøger og vil arbejde på at løse dette så hurtigt som muligt. Vi deler snart mere information. Vi undskylder ulejligheden. Hvis du har spørgsmål vedrørende dette emne, bedes du kontakte os på support @ bemanding base.com.

2. 14. juli 2026 kl. 14.54 UTCmonitoring

   Opdatering: Vi har indsat en rettelse til problemet. Funktionaliteten er blevet genoprettet, og vi overvåger nu alle miljøer for at bekræfte det. Vi vil sende en endelig opdatering, når overvågningen bekræfter fuld stabilitet.

3. 15. juli 2026 kl. 07.37 UTCmonitoring

   Vi fortsætter med at overvåge for yderligere spørgsmål.

4. 15. juli 2026 kl. 08.08 UTCresolved

   Problemet er løst. Vi undskylder for den ulejlighed, det har forårsaget. Kontakt os på support @ bemande.com, hvis du stadig har problemer. Vi hjælper gerne!

5. 27. juli 2026 kl. 15.26 UTCpostmortem

   * * Oversigt * * Den 14. juli 2026, mellem 3: 50 PM og 4: 59 PM\ (CEST\), kunder på tværs af alle systemer oplevede serviceafbrydelser påvirker flere platform funktioner. Vores hold har med succes identificeret årsagen og genoprettet fuld service funktionalitet. Hvad skete der? En nylig opdatering indført en godkendelse konfiguration problem, der forårsagede flere platform funktioner, herunder sideindlæsning, meddelelser, e-mail, analytics, og link sporing, at returnere fejl. Vores team identificerede problemet og løste det, genoprette normale operationer på tværs af alle berørte systemer. * * Indvirkning * * Mellem 3: 50 PM og 4: 59 PM\ (CEST\) den 14. juli 2026, kunder på det europæiske, Amerika, og Asien / Stillehavet Systems kan have oplevet fejl adgang sider, meddelelser, e-mail, analytics, og link tracking funktioner. * * Fremtidige forbedringer * * Vi vil gennemføre yderligere kontroller af driften af den berørte tjenestekomponent og forbedre vores evne til at opdage og løse lignende problemer hurtigere i fremtiden. Tak for Deres tålmodighed og forståelse, mens vi arbejder på at forbedre vores tjenester og forhindre fremtidige hændelser. Hvis du har spørgsmål eller bekymringer, så tøv ikke med at kontakte vores kundesupport team på [support @ bemande.com] (mailto: support @ bemande.com).

Automatisk oversat fra den officielle hændelsesopdatering.

1. 9. juli 2026 kl. 14.12 UTCinvestigating

   Vi undersøger et problem, der påvirker oprettelsen af nye Studio Email-udkast og skabeloner i vores amerikanske miljø. Når du opretter et nyt udkast, kan du se en vellykket gemme bekræftelse, men udkastet ikke vises på din Drafts liste bagefter. Eksisterende udkast og tidligere sendte e-mails er ikke påvirket. Kunder i vores EU-miljø er ikke berørt. Vores team arbejder aktivt på at identificere og løse sagen. Vi vil sende en opdatering, så snart vi har flere oplysninger.

2. 9. juli 2026 kl. 15.11 UTCmonitoring

   Vi har indsat en rettelse til at løse problemet, der påvirker nye Studio E-mail-udkast i vores amerikanske miljø. Oprettelse og visning af nye udkast og skabeloner skal nu fungere som forventet. Vi vil fortsat overvåge systemerne, indtil vi er sikre på, at problemet er løst fuldt ud.

3. 10. juli 2026 kl. 07.11 UTCresolved

   Denne hændelse er blevet løst. Vi beklager de problemer, det har skabt. Kontakt os venligst på support @ bemanding base.com hvis du oplever yderligere problemer. Vi hjælper gerne!

4. 14. juli 2026 kl. 13.11 UTCresolved

   * * Oversigt * * Den 9. juli 2026, mellem 9: 01 AM og 4: 06 PM\ (CEST\), kunder på Americas System oplevede et problem, hvor nyoprettede Staffbase Medarbejder e-mail udkast, planlagte e-mails, og sendte e-mails ikke vises i deres respektive liste visninger. Vores hold har med succes identificeret årsagen og genoprettet fuld service funktionalitet. * * Hvad der skete * * En baggrund indeksering proces ansvarlig for at befolke e-liste visninger stoppede med at fungere korrekt, så nyoprettede udkast, planlagte e-mails, og sendte e-mails blev ikke vist i deres respektive lister, selvom de blev gemt med succes. Brugerne modtog bekræftelse på, at deres indhold blev gemt, men kunne ikke finde det til at se, redigere eller sende. Andre regioner blev ikke berørt. Vores team identificeret problemet og løst det, genoprette normal synlighed for alt berørt indhold. * * Indvirkning * * Mellem 9: 01 AM og 4: 06 PM\ (CEST\) den 9. juli 2026, kunder på Americas System kan have været ude af stand til at finde nyoprettede Staffbase Medarbejder e-mail udkast, planlagte e-mails, eller sendt e-mails i deres liste visninger, selvom indholdet blev gemt med succes. Tidligere skabt indhold forblev synlige overalt. Ingen data blev tabt under denne hændelse. * * Fremtidige forbedringer * * Vi vil gennemføre yderligere kontroller for driften af den berørte service komponent og forbedre vores evne til at opdage og løse lignende spørgsmål hurtigere i fremtiden. Tak for Deres tålmodighed og forståelse, mens vi arbejder på at forbedre vores tjenester og forhindre fremtidige hændelser. Hvis du har spørgsmål eller bekymringer, så tøv ikke med at kontakte vores kundesupport team på [support @ bemande.com] (mailto: support @ bemande.com).

Automatisk oversat fra den officielle hændelsesopdatering.

1. 9. juli 2026 kl. 14.01 UTCinvestigating

   Vi undersøger et problem, der påvirker oprettelsen af nye Studio Email-udkast og skabeloner i vores amerikanske miljø. Når du opretter et nyt udkast, kan du se en vellykket gemme bekræftelse, men udkastet ikke vises på din Drafts liste bagefter. Eksisterende udkast og tidligere sendte e-mails er ikke påvirket. Kunder i vores EU-miljø er ikke berørt. Vores team arbejder aktivt på at identificere og løse sagen. Vi vil sende en opdatering, så snart vi har flere oplysninger.

2. 9. juli 2026 kl. 14.19 UTCmonitoring

   Vi har indsat en rettelse til at løse problemet, der påvirker nye Studio E-mail-udkast i vores amerikanske miljø. Oprettelse og visning af nye udkast og skabeloner skal nu fungere som forventet. Vi vil fortsat overvåge systemerne, indtil vi er sikre på, at problemet er løst fuldt ud.

3. 10. juli 2026 kl. 06.29 UTCresolved

   Denne hændelse er blevet løst. Vi beklager de problemer, det har skabt. Kontakt os venligst på support @ bemanding base.com hvis du oplever yderligere problemer. Vi hjælper gerne!

4. 14. juli 2026 kl. 12.19 UTCpostmortem

   * * Oversigt * * Den 9. juli 2026, mellem 9: 01 AM og 4: 06 PM\ (CEST\), kunder på Americas System oplevede et problem, hvor nyoprettede Staffbase Medarbejder e-mail udkast, planlagte e-mails, og sendte e-mails ikke vises i deres respektive liste visninger. Vores hold har med succes identificeret årsagen og genoprettet fuld service funktionalitet. Hvad skete der? En baggrund indeksering proces ansvarlig for at befolke e-mail-listevisninger stoppet fungerer korrekt, så nyoprettede udkast, planlagte e-mails, og sendte e-mails blev ikke vist i deres respektive lister, selvom de blev gemt med succes. Brugerne modtog bekræftelse på, at deres indhold blev gemt, men kunne ikke finde det til at se, redigere eller sende. Andre regioner blev ikke berørt. Vores team identificeret problemet og løst det, genoprette normal synlighed for alt berørt indhold. * * Indvirkning * * Mellem 9: 01 AM og 4: 06 PM\ (CEST\) den 9. juli 2026, kunder på Americas System kan have været ude af stand til at finde nyoprettede Staffbase Medarbejder e-mail udkast, planlagte e-mails, eller sendt e-mails i deres liste visninger, selv om indholdet blev gemt med succes. Tidligere skabt indhold forblev synlige overalt. Ingen data blev tabt under denne hændelse. * * Fremtidige forbedringer * * Vi vil gennemføre yderligere kontroller af driften af den berørte tjenestekomponent og forbedre vores evne til at opdage og løse lignende problemer hurtigere i fremtiden. Tak for Deres tålmodighed og forståelse, mens vi arbejder på at forbedre vores tjenester og forhindre fremtidige hændelser. Hvis du har spørgsmål eller bekymringer, så tøv ikke med at kontakte vores kundesupport team på [support @ bemande.com] (mailto: support @ bemande.com).

Automatisk oversat fra den officielle hændelsesopdatering.

1. 8. juli 2026 kl. 11.09 UTCinvestigating

   Påvirkede funktion: Menu Meddelelser Nogle brugere kan opleve et problem, hvor ulæste notifikationstal ikke opdateres korrekt i meddelelsesmenuen. Vores hold undersøger og vil arbejde på at løse dette så hurtigt som muligt. Vi deler snart mere information. Du kan se på hvilket system din ansøgning er vært ved at gå til Studio > Indstillinger > API Adgang og kontrol af mærket ved siden af titlen. Vi undskylder ulejligheden. Hvis du har spørgsmål vedrørende dette emne, bedes du kontakte os på support @ bemanding base.com.

2. 8. juli 2026 kl. 13.13 UTCmonitoring

   Opdatering: Vi har indsat en rettelse til problemet, der forhindrede ulæste meddelelser til korrekt opdatering. Funktionaliteten er blevet genoprettet, og vi overvåger nu alle miljøer for at bekræfte det. Vi vil sende en endelig opdatering, når overvågningen bekræfter fuld stabilitet.

3. 9. juli 2026 kl. 12.12 UTCresolved

   Problemet er løst. Vi undskylder for den ulejlighed, det har forårsaget. Kontakt os på support @ bemande.com, hvis du stadig har problemer. Vi hjælper gerne!

4. 9. juli 2026 kl. 14.12 UTCresolved

   * * Oversigt * * Den 8. juli 2026, mellem 7: 06 AM og 2: 05 PM\ (CEST\), kunder på det europæiske system oplevede forkerte ulæste indikatorer på visse menupunkter, såsom nyhedssider og mapper. Vores hold har med succes identificeret årsagen og genoprettet fuld service funktionalitet. * * Hvad der skete * * En nylig opdatering forårsagede ulæste indikatorer på visse menupunkter, såsom nyhedssider og mapper, for at vise forkerte oplysninger for nogle brugere. Nogle menupunkter fortsatte med at vise ulæste tæller for indhold, der ikke længere var synlige, mens andre stoppede med at vise en indikator overhovedet. Vores team identificeret problemet og løst det, genoprette nøjagtige ulæste indikatorer for berørte menupunkter. Amerikanerne og Asien / Stillehavet blev også overvåget som en forholdsregel, og der blev ikke observeret nogen virkning for kunderne i disse regioner. * * Indvirkning * * Mellem 7: 06 AM og 2: 05 PM\ (CEST\) den 8. juli 2026, kunder på det europæiske system kan have set ulæste indikatorer på visse menupunkter, såsom nyhedssider og mapper, der ikke afspejler nuværende indhold, i nogle tilfælde viser tal, der ikke kunne ryddes eller ingen indikator overhovedet. Ingen data blev tabt under denne hændelse. * * Fremtidige forbedringer * * Vi vil gennemføre yderligere kontroller for visning af menu ulæste indikatorer og forbedre vores evne til at opdage og løse lignende spørgsmål hurtigere i fremtiden. Tak for Deres tålmodighed og forståelse, mens vi arbejder på at forbedre vores tjenester og forhindre fremtidige hændelser. Hvis du har spørgsmål eller bekymringer, så tøv ikke med at kontakte vores kundesupport team på [support @ bemande.com] (mailto: support @ bemande.com).

Automatisk oversat fra den officielle hændelsesopdatering.

1. 8. juli 2026 kl. 10.18 UTCinvestigating

   Affected feature: Menu Notifications Some users may experience an issue where the unread notification count does not update correctly in the notification menu. Our teams are investigating and will work to resolve this as fast as we can. We will share more information soon. You can see on which system your application is hosted by going to the Studio > Settings > API Access and checking the tag next to the title. We apologize for the inconvenience. If you have any questions regarding this topic, please reach out to our support at [email protected].

2. 8. juli 2026 kl. 12.13 UTCmonitoring

   Update: We have deployed a fix for the issue that prevented unread notifications to properly update. Functionality has been restored, and we are now monitoring all environments to confirm. We will post a final update once monitoring confirms full stability.

3. 9. juli 2026 kl. 11.43 UTCresolved

   The issue is resolved. We apologize for the inconvenience this has caused. Please get in touch with us at [email protected] in case you're still having any problems. We’re happy to help!

4. 9. juli 2026 kl. 13.59 UTCpostmortem

   **Summary** On July 8, 2026, between 7:06 AM and 2:05 PM \(CEST\), customers on the European System experienced incorrect unread indicators on certain menu items, such as news pages and folders. Our teams successfully identified the cause and restored full service functionality. **What Happened** A recent update caused unread indicators on certain menu items, such as news pages and folders, to display incorrect information for some users. Some menu items continued to show unread counts for content that was no longer visible, while others stopped displaying an indicator at all. Our team identified the issue and resolved it, restoring accurate unread indicators for affected menu items. The Americas and Asia/Pacific Systems were also monitored as a precaution, and no impact was observed for customers in those regions. **Impact** Between 7:06 AM and 2:05 PM \(CEST\) on July 8, 2026, customers on the European System may have seen unread indicators on certain menu items, such as news pages and folders, that did not reflect current content, in some cases showing counts that could not be cleared or no indicator at all. No data was lost during this incident. **Future Improvements** We will implement additional checks for the display of menu unread indicators and improve our ability to detect and resolve similar issues more quickly in the future. Thank you for your patience and understanding while we work to improve our services and prevent future incidents. If you have any questions or concerns, please do not hesitate to reach out to our customer support team at [[email protected]](mailto:[email protected]).

1. 6. juli 2026 kl. 13.57 UTCinvestigating

   Affected feature: AI Navigator We have received reports that some customers are experiencing issues with AI Navigator, where new requests do not load results and instead return to the start of the request. Our teams are investigating and will work to resolve this as quickly as possible. We will share more information soon. You can see on which system your application is hosted by going to Studio > Settings > API Access and checking the tag next to the title. We apologize for the inconvenience. If you have any questions regarding this topic, please reach out to our support team at [email protected].

2. 6. juli 2026 kl. 15.13 UTCmonitoring

   Update: We have deployed a fix for the issue that prevented users from starting new conversations in the Navigator AI Assistant. Functionality has been restored, and we are now monitoring all environments to confirm. Impact was limited to starting new conversations in the AI Assistant. Other platform features were not affected. We will post a final update once monitoring confirms full stability.

3. 7. juli 2026 kl. 12.52 UTCresolved

   This incident has been resolved. We are sorry for the trouble this has caused. Please contact us at [email protected] should you experience any further issues. We’re happy to help!

4. 8. juli 2026 kl. 13.47 UTCpostmortem

   **Summary** On July 6, 2026, between 1:00 PM and 5:05 PM \(CEST\), customers on the European System, Americas System, and Asia/Pacific System experienced issues starting new conversations with the AI Assistant. Our teams successfully identified the cause and restored full service functionality. **What Happened** A recent update introduced a version mismatch between two internal system components supporting the AI Assistant. As a result, users were unable to start new AI Assistant conversations, with the interface appearing unresponsive and no error message shown. Other App/Intranet features continued to operate normally. Our team identified the issue and resolved it, restoring full functionality for the AI Assistant. **Impact** Between 1:00 PM and 5:05 PM \(CEST\) on July 6, 2026, users on the European System, Americas System, and Asia/Pacific System may have been unable to start new AI Assistant conversations. Existing conversations were not affected, and no other platform features were impacted. **Future Improvements** We will implement additional checks for the operation of the AI Assistant service and improve our ability to detect and resolve similar issues more quickly in the future. Thank you for your patience and understanding while we work to improve our services and prevent future incidents. If you have any questions or concerns, please do not hesitate to reach out to our customer support team at [[email protected]](mailto:[email protected]).

1. 25. juni 2026 kl. 17.18 UTCinvestigating

   Affected feature: Staffbase App/Intranet Some users may be experiencing slow performance when accessing their Staffbase app. Our teams are investigating and will work to resolve this as fast as we can. We will share more information soon. You can see on which system your application is hosted by going to the Studio > Settings > API Access and checking the tag next to the title. We apologize for the inconvenience. If you have any questions regarding this topic, please reach out to our support at [email protected].

2. 25. juni 2026 kl. 17.23 UTCinvestigating

   We are continuing to investigate this issue.

3. 25. juni 2026 kl. 18.02 UTCmonitoring

   We have rolled out a rollback release to resolve the issue and the performance of accessing the Staffbase App is restored. We will continue to monitor the systems until we are sure the issue is fully resolved.

4. 25. juni 2026 kl. 19.02 UTCresolved

   The issue is resolved. We apologize for the inconvenience this has caused. Please get in touch with us at [email protected] in case you're still having any problems. We’re happy to help!

5. 13. juli 2026 kl. 15.08 UTCpostmortem

   **Summary** On Jun 25, 2026, between 6:40 PM and 8:05 PM \(CEST\), customers on the European System and Americas System experienced issues with performance degradation and/or accessibility issues to their Staffbase platform. Our teams successfully identified the cause and restored full service functionality. **What Happened** A recent update introduced a backend release that have caused the api/menu call to return full menu payloads. As a result, users would experience performance issues with loading their Staffbase instance, with the loading time ranging up to 10 seconds. Other App/Intranet features continued to operate normally. Our team identified the issue and resolved it, restoring full functionality for the backend system. **Impact** Between 6:40 PM and 8:05 PM \(CEST\) on Jun 25, 2026, users on the European System and Americas System may have experienced performance degradation or been unable to access their Staffbase platform. **Future Improvements** We will implement additional checks for the backend releases and improve our ability to detect and resolve similar issues more quickly in the future. Thank you for your patience and understanding while we work to improve our services and prevent future incidents. If you have any questions or concerns, please do not hesitate to reach out to our customer support team at [[email protected]](mailto:[email protected]).

1. 18. juni 2026 kl. 20.03 UTCinvestigating

   We have received reports that some customers on the Americas system are experiencing an error when attempting to open pre-existing drafts in Email Modern, or drafts stop responding Our teams are currently investigating the root cause. You can see on which system your application is hosted by going to Studio > Settings > API Access tab. We apologize for the inconvenience. If you have any questions, please reach out to our support team at [email protected].

2. 18. juni 2026 kl. 21.02 UTCidentified

   We have identified the cause of the issues affecting drafts in Email Modern on the Americas system. Our teams are actively working to implement a fix and restore full functionality. We will provide a further update as soon as the fix is in place. If you have any questions, please reach out to our support team at [email protected].

3. 18. juni 2026 kl. 22.25 UTCresolved

   We have deployed a fix for the errors affecting drafts in the Email Modern environment. All systems are operating normally. We apologize for any inconvenience this may have caused. If you continue to experience issues loading or editing drafts, please contact our support team at [email protected].

4. 24. juni 2026 kl. 15.04 UTCpostmortem

   **Summary** — On June 18, between 8:56 PM and 12:24 PM \(CEST\), customers across all systems encountered issues accessing pre-existing email drafts, or experienced unresponsiveness when interacting with certain elements in drafts in Staffbase Email Modern. Our teams successfully identified the cause and restored full service functionality. **What Happened** — A recent update introduced a change to the email editing component that affected how certain draft content was processed. Some drafts failed to open and displayed an error message, while others contained elements that caused the page to become unresponsive when accessed. Our team identified and resolved the issue, restoring normal access to all affected drafts. **Impact** — Between 8:56 PM and 12:24 PM \(CEST\) on June 18, users with certain pre-existing email drafts may have experienced an error message when attempting to open those drafts, or found the page unresponsive. Drafts without the affected content continued to work normally. **Future Improvements** — We will implement additional checks for the operation of the affected service component and improve our ability to detect and resolve similar issues more quickly in the future. Thank you for your patience and understanding while we work to improve our services and prevent future incidents. If you have any questions or concerns, please do not hesitate to reach out to our customer support team at [[email protected]](mailto:[email protected]).

1. 18. juni 2026 kl. 17.06 UTCinvestigating

   We have received reports that some customers on the European and Americas systems are experiencing issues with email analytics failing to load. Affected areas include sent email statistics, audience data, and email designer. You can see on which system your application is hosted by going to Studio > Settings > API Access tab. Our teams are actively investigating the issue. We will provide a further update as soon as we have more information. We apologize for the inconvenience. If you have any questions, please reach out to our support team at [email protected].

2. 18. juni 2026 kl. 17.07 UTCinvestigating

   We are continuing to investigate this issue.

3. 18. juni 2026 kl. 17.22 UTCmonitoring

   All systems are back up and operational. Our teams are continuing to investigate the underlying cause and are actively monitoring all systems to ensure stability. We apologize for any inconvenience this may have caused. If you are still experiencing issues, please reach out to our support team at [email protected].

4. 18. juni 2026 kl. 19.18 UTCresolved

   The issues affecting email analytics have been resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused. If you are still experiencing issues, please reach out to our support team at [email protected].

5. 23. juni 2026 kl. 13.25 UTCpostmortem

   **Summary** — On June 18, between 6:33 PM and 7:08 PM \(CEST\), customers on the European System and Americas System experienced an inability to view email analytics, audience data, and click maps in Staffbase Employee Email. Our teams successfully identified the cause and restored full service functionality. **What Happened** — A recent update to Staffbase Employee Email introduced an issue that caused analytics and sent email data to fail loading. This affected the analytics overview, audience data, click maps, and the details panel within individual sent emails. Our team identified the cause, reverted the recent update, and confirmed that all affected data was loading as expected following the fix. **Impact** — Between approximately 6:33 PM and 7:08 PM \(CEST\), users on the European System and Americas System were unable to view email statistics, audience data, and click maps in Staffbase Employee Email. In some cases, data either failed to load or took several minutes to appear, making the analytics workflow effectively unavailable during this period. **Future Improvements** — We will implement additional checks for the operation of the affected service component and improve our ability to detect and resolve similar issues more quickly in the future. Thank you for your patience and understanding while we work to improve our services and prevent future incidents. If you have any questions or concerns, please do not hesitate to reach out to our customer support team at [[email protected]](mailto:[email protected]).

1. 18. juni 2026 kl. 12.31 UTCresolved

   Between 11:30 and 11:39 CEST customers on the Americas system were unable to access the App/Intranet/Email platform. The disruption lasted approximately 9 minutes. We re-deployed a release connected to the service disruption the day before but part of that change didn’t apply as expected and briefly reproduced a similar outage. This was quickly identified and the update was rolled back to restore full functionality. We apologize for any inconvenience this may have caused. If you have any questions or feedback please reach out to our support team at [email protected].

1. 11. juni 2026 kl. 13.48 UTCinvestigating

   Some customers are experiencing long loading times and apps being not reachable. Our teams are investigating and will work to resolve this as fast as we can. We will share more information soon. We apologize for the inconvenience. If you have any questions regarding this topic, please reach out to our support at [email protected].

2. 11. juni 2026 kl. 14.05 UTCidentified

   We have identified the cause of the service disruption affecting App & Intranet. The German environment is now recovering and service is being restored for affected users. Our teams are continuing to work on fully restoring performance for the US environment, where some users may still experience slow loading times or errors. We will provide a further update as soon as we have more information. We apologize for the inconvenience. If you have any questions, please reach out to our support team at [email protected].

3. 11. juni 2026 kl. 14.11 UTCmonitoring

   All systems are back up and operational. Our teams are continuing to investigate the underlying cause and are actively monitoring all systems to ensure stability. We will publish a post-mortem here on our status page once our investigation is complete. We apologize for any inconvenience this may have caused. If you are still experiencing issues, please reach out to our support team at [email protected].

4. 11. juni 2026 kl. 14.27 UTCresolved

   The availability and performance issues have been fully resolved. All systems are operating normally. A Post Mortem for this incident will be published following our internal review. We apologize for any inconvenience this may have caused. If you are still experiencing issues, please reach out to our support team at [email protected].

5. 16. juni 2026 kl. 15.22 UTCpostmortem

   **Summary** — Our investigation of the incident is complete, and we would like to provide details about the service disruption that affected access to our platform on June 11, 2026, between approximately 3:27 PM and 4:05 PM \(CEST\). Customers on the European and Americas systems experienced a temporary loss of access. Our teams successfully identified the cause and restored full service functionality. **What Happened** — A recent backend update introduced a change to database query handling that consumed more system resources in production than anticipated from testing. As a result, backend services became temporarily unavailable, preventing users from accessing the platform. Our team identified the cause, reverted the change, and restored normal operations. **Impact** — Between approximately 3:27 PM and 4:05 PM \(CEST\) on June 11, 2026, users on the European and Americas systems were temporarily unable to access App/Intranet. The European system was affected from approximately 3:27 PM to 3:54 PM, and the Americas system from approximately 3:27 PM to 4:05 PM \(CEST\). **Future Improvements** — We have confirmed that recently added data fields are properly indexed and optimized for full production scale, and we have refined our recent database queries for efficiency. We have also enabled automated validation of our database indexing so that potential issues are caught proactively. In addition, we continue to enhance our internal monitoring and refine our rollback procedures so we can detect and resolve similar issues even faster in the future. Thank you for your patience and understanding while we work to improve our services and prevent future incidents. If you have any questions or concerns, please do not hesitate to reach out to our customer support team at [[email protected]](mailto:[email protected]).

1. 3. juni 2026 kl. 13.49 UTCinvestigating

   Affected feature: Video Upload We have received reports that some customers are currently unable to upload videos to the platform, even when the files meet our technical requirements. Our teams are actively investigating the issue. We will provide a further update as soon as we have more information. We apologize for the inconvenience. If you have any questions, please reach out to our support team at [email protected].

2. 3. juni 2026 kl. 14.52 UTCresolved

   The video upload issues for some specific videos affecting all systems have been resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused. If you are still experiencing issues, please reach out to our support team at [email protected].

3. 8. juni 2026 kl. 14.19 UTCpostmortem

   **Summary** As our investigation of the incident is complete, we would like to provide details about the service disruption that affected video uploads between approximately May 29, 2026, at 11:35 AM and June 3, 2026, at 4:43 PM \(CEST\). Customers on the European, Americas, and Asia/Pacific Systems experienced failures when uploading certain videos to the platform. Our teams successfully identified the cause and restored full service functionality. **What Happened** A recent update to an internal service component introduced an issue that caused certain video files to stall during the upload process without completing. Affected uploads appeared to progress normally but would not reach completion, and the uploaded content would not be published. Our team identified the issue and restored normal operations. **Impact** Between approximately May 29, 2026, 11:35 AM and June 3, 2026, at 4:43 PM \(CEST\), users on the European, Americas, and Asia/Pacific Systems may have experienced failures when uploading specific video files. Affected uploads would appear to progress but would stall during processing and not be published. Other video uploads and platform features continued to function normally during this period. **Future Improvements** We will implement additional checks for the operation of the affected service component and improve our ability to detect and resolve similar issues more quickly in the future. Thank you for your patience and understanding while we work to improve our services and prevent future incidents. If you have any questions or concerns, please do not hesitate to reach out to our customer support team at [[email protected]](mailto:[email protected]).

1. 2. juni 2026 kl. 14.14 UTCinvestigating

   Affected feature: User Provisioning / Conditional Groups We have received reports that new users onboarded via Single Sign-On (SSO) are not being automatically assigned to their Conditional Groups at the time of account creation. Profile field values are transferred correctly during provisioning. However, the group assignment does not take effect until a profile field is manually updated afterward. Our teams are currently investigating the issue. We apologize for the inconvenience. If you have any questions regarding this topic, please reach out to our support team at [email protected].

2. 2. juni 2026 kl. 15.34 UTCmonitoring

   We have taken measures to address the issue affecting Conditional Group assignment for new SSO users, and the fix is now being rolled out across all systems. We will continue to monitor the situation closely to ensure new users are assigned to their Conditional Groups correctly upon account creation. If you continue to experience this issue, please contact our support team at [email protected].

3. 3. juni 2026 kl. 13.07 UTCresolved

   The issue affecting Conditional Group assignments for new users created via SSO has been resolved. New users are now automatically assigned to the correct Conditional Groups based on their profile field values upon account creation. We apologize for any inconvenience this may have caused. If you are still experiencing issues, please reach out to our support team at [email protected].

4. 5. juni 2026 kl. 08.50 UTCpostmortem

   **Summary** As our investigation is now complete, we would like to provide details about an issue where new users created via SSO were not automatically assigned to their Conditional Groups. The incident was initially assessed as potentially affecting all systems. Following our investigation, we confirmed that only the European System was impacted. Our team identified the root cause, deployed a fix on June 2, 2026, and confirmed full resolution on June 3, 2026. **What Happened** Following a recent update, the process responsible for assigning users to Conditional Groups based on their profile attributes was not triggered correctly during SSO account creation. New users were created successfully and their profile information was transferred, but the subsequent group assignment step was silently skipped. Our team identified the issue and implemented a fix that restored the correct behavior for new SSO user accounts. **Impact** New users created via SSO on the European System were not automatically assigned to their Conditional Groups at account creation. Affected users did not receive the expected group memberships and required manual profile updates to trigger the assignment until the fix was applied. No impact was observed on the Americas System or the Asia/Pacific System. The fix was deployed on June 2, 2026, and confirmed fully effective on June 3, 2026. **Future Improvements** We will implement additional checks for the operation of the affected service component and improve our ability to detect and resolve similar issues more quickly in the future. Thank you for your patience and understanding while we work to improve our services and prevent future incidents. If you have any questions or concerns, please do not hesitate to reach out to our customer support team at [[email protected]](mailto:[email protected]).