Staffbase Outage History

Started Oct 21, 2026, 09:52 AM UTC· resolved Oct 21, 2026, 10:20 AM UTC

1. investigating Oct 21, 2026, 09:52 AM UTC

   Customers hosted in our US region may be unable to access the Staffbase App and Intranet. We are investigating the disruption and working to restore access.

2. identified Oct 21, 2026, 10:01 AM UTC

   Customers hosted in our US region may continue to experience issues accessing the Staffbase App and Intranet. We have identified the issue and are working on a fix to restore access.

3. monitoring Oct 21, 2026, 10:11 AM UTC

   We have implemented a fix to address the access issues affecting the Americas system, and access is returning to normal. We will continue to monitor the system closely to ensure access remains stable. If you continue to experience issues accessing your application, please contact our support at [[email protected]](mailto:[email protected] "[email protected]").

4. resolved Oct 21, 2026, 10:20 AM UTC

   The access issues affecting the Americas system have been resolved. Full service has been restored and 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. Thank you for your patience. If you are still experiencing issues, please reach out to our support team at [[email protected]](mailto:[email protected] "[email protected]").

Read the full incident report →

Started Oct 21, 2026, 07:00 AM UTC· resolved Oct 21, 2026, 07:00 AM UTC

1. resolved Oct 21, 2026, 02:52 PM UTC

   We are aware of the critical PHP vulnerabilities published today (CVE-2026-109618 and CVE-2026-109619) and have been monitoring the situation closely since this morning. Emergency web application firewall rules addressing these vulnerabilities were deployed by Cloudflare earlier today and are active across our infrastructure. We have seen no indication of exploitation in our environment. The core Staffbase platform does not use the affected components. A small number of plugins do. These have already been moved to hardened base images, and we will roll out the patched PHP versions as soon as they become available in those base images. All systems are operating normally. We will continue to monitor the situation and provide an update if anything changes. If you have any questions regarding this topic, please reach out to our support team at [[email protected]](mailto:[email protected]).

Read the full incident report →

Started Oct 14, 2026, 08:39 AM UTC· resolved Oct 14, 2026, 08:48 AM UTC

1. investigating Oct 14, 2026, 08:39 AM UTC

   We have received reports that customers using Email Modern on the European and Americas systems are currently unable to send emails. Affected users may see a "Something went wrong" error message when attempting to send. Our teams are actively investigating the issue and working to restore email sending as quickly as possible. You can see on which system your application is hosted by going to the Studio > Settings > API Access tab. We apologize for the inconvenience. If you have any questions regarding this topic, please reach out to our support team at [[email protected]](mailto:[email protected] "[email protected]").

2. resolved Oct 14, 2026, 08:48 AM UTC

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

Read the full incident report →

Started Oct 08, 2026, 10:09 AM UTC· resolved Oct 08, 2026, 12:05 PM UTC

1. identified Oct 08, 2026, 10:09 AM UTC

   We are investigating a service disruption from Azure affecting App & Intranet in our European environment. Our team is assessing the impact and working to restore normal service with highest priority.

2. monitoring Oct 08, 2026, 10:25 AM UTC

   We have taken measures to address the issue affecting European services, and service availability has improved. Microsoft Azure continues to report an active regional degradation. We are monitoring the platform closely while recovery is verified.

3. resolved Oct 08, 2026, 12:05 PM UTC

   Service availability for our European services has been restored, and we are no longer observing issues related to the regional Microsoft Azure degradation. We apologize for the inconvenience this has caused. Please get in touch with us at [[email protected]](mailto:[email protected] "[email protected]") in case you're still having any problems. We’re happy to help!

Read the full incident report →

Started Sep 21, 2026, 09:30 AM UTC· resolved Sep 22, 2026, 08:15 AM UTC

1. investigating Sep 21, 2026, 09:30 AM UTC

   We have received reports that some customers on the European system are experiencing severely degraded performance when using the Staffbase web application. You can see on which system your application is hosted by going to Studio > Settings > API Access. We apologize for the inconvenience. If you have any questions regarding this topic, please reach out to our support team at [[email protected]](mailto:[email protected] "[email protected]").

2. identified Sep 21, 2026, 11:10 AM UTC

   Performance levels on the European system have returned to normal. However, we have identified that the Search function is currently not working as expected. Our teams are investigating this issue and working on a resolution.

3. monitoring Sep 21, 2026, 04:20 PM UTC

   We have taken measures to address the degraded performance and the issue affecting Search on the European system. Performance levels have improved and Search functionality has been restored. We will continue to monitor the system closely to ensure everything remains stable.

4. resolved Sep 22, 2026, 08:15 AM UTC

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

Read the full incident report →

Started Sep 04, 2026, 12:06 PM UTC· resolved Sep 04, 2026, 03:05 PM UTC

1. identified Sep 04, 2026, 12:06 PM UTC

   Some customers might experience delayed delivery of emails sent from Staffbase (Email Modern and notification emails). Our investigation confirmed the emails were sent successfully from our side; the delay is caused by the recipient's mail provider, Microsoft 365/Outlook, temporarily deferring incoming messages during a period of high load on their end. No action is needed. Delayed emails should arrive as the receiving mail server works through its queue. Due to this issue, some customers with Microsoft 365/Outlook might not be able to receive answers to our Support Tickets right now, so feel free to use our ticket portal via support.staffbase.com. Thank you for your patience while this is being addressed. If you have any questions regarding this topic, please reach out to our support team at [email protected].

2. resolved Sep 04, 2026, 03:05 PM UTC

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

3. resolved Sep 04, 2026, 03:08 PM UTC

   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!

Read the full incident report →

Started Sep 02, 2026, 03:30 PM UTC· resolved Sep 02, 2026, 03:30 PM UTC

1. resolved Sep 03, 2026, 10:09 AM UTC

   Between 15:15 and 15:30 UTC (17:15-17:30 CEST) on September 2, some customers experienced elevated error rates and slow performance, affecting both our EU- and US-hosted environments. This was caused by an internal deployment change and resolved on its own within about fifteen minutes once traffic was rerouted back to normal. We’re sorry for the disruption this caused. If you’re still seeing any related issues, please reach out to us at [email protected] - we’re happy to help.

Read the full incident report →

Started Aug 31, 2026, 10:08 AM UTC· resolved Aug 31, 2026, 12:09 PM UTC

1. investigating Aug 31, 2026, 10:08 AM UTC

   Affected feature: Staffbase AI (Navigator, Podcast, Email/Page generation) Some customers may be experiencing trouble with our AI tools and encountering error messages when interacting with them. 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 team at [email protected].

2. monitoring Aug 31, 2026, 11:06 AM UTC

   We have taken measures to resolve the issue and restore the full functionality of all AI tools/parts within Staffbase. We will continue to monitor the systems until we are sure the issue is fully resolved.

3. resolved Aug 31, 2026, 01:10 PM UTC

   This incident has been resolved. The Navigator and other affected AI features are fully functional again. 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!

Read the full incident report →

Started Jul 14, 2026, 03:06 PM UTC· resolved Jul 15, 2026, 08:08 AM UTC

1. monitoring Jul 14, 2026, 03:06 PM UTC

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

2. investigating Jul 14, 2026, 03:06 PM UTC

   Some users may encounter an issue where forms, pages, or other content fail to load and instead display the error message "error.unknown.title". 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].

3. resolved Jul 15, 2026, 08:11 AM UTC

   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. monitoring Jul 15, 2026, 08:11 AM UTC

   We are continuing to monitor for any further issues.

5. resolved Jul 27, 2026, 04:10 PM UTC

   **Summary**On July 14, 2026, between 3:50 PM and 4:59 PM \(CEST\), customers across all systems experienced service interruptions affecting multiple platform features. Our teams successfully identified the cause and restored full service functionality. **What Happened**A recent update introduced an authentication configuration issue that caused several platform features, including page loading, notifications, email, analytics, and link tracking, to return errors. Our team identified the issue and resolved it, restoring normal operations across all affected systems. **Impact**Between 3:50 PM and 4:59 PM \(CEST\) on July 14, 2026, customers on the European, Americas, and Asia/Pacific Systems may have experienced errors accessing pages, notifications, email, analytics, and link tracking features. **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]).

Read the full incident report →

Started Jul 09, 2026, 02:12 PM UTC· resolved Jul 10, 2026, 06:29 AM UTC

1. investigating Jul 09, 2026, 02:12 PM UTC

   We are investigating an issue affecting the creation of new Studio Email drafts and templates in our US environment. When creating a new draft, you may see a successful save confirmation, but the draft does not appear in your Drafts list afterward. Existing drafts and previously sent emails are not affected. Customers hosted in our EU environment are not affected. Our team is actively working to identify and resolve the cause. We will post an update as soon as we have more information.

2. monitoring Jul 09, 2026, 03:11 PM UTC

   We have deployed a fix to resolve the issue affecting new Studio Email drafts in our US environment. Creating and viewing new drafts and templates should now work as expected. We will continue to monitor the systems until we are sure the issue is fully resolved.

3. resolved Jul 10, 2026, 07:11 AM UTC

   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. resolved Jul 14, 2026, 01:11 PM UTC

   **Summary**On July 9, 2026, between 9:01 AM and 4:06 PM \(CEST\), customers on the Americas System experienced an issue where newly created Staffbase Employee Email drafts, scheduled emails, and sent emails did not appear in their respective list views. Our teams successfully identified the cause and restored full service functionality. **What Happened**A background indexing process responsible for populating email list views stopped functioning correctly, so newly created drafts, scheduled emails, and sent emails were not appearing in their respective lists even though they were saved successfully. Users received confirmation that their content was saved but could not locate it to view, edit, or send. Other regions were not affected. Our team identified the issue and resolved it, restoring normal visibility for all affected content. **Impact**Between 9:01 AM and 4:06 PM \(CEST\) on July 9, 2026, customers on the Americas System may have been unable to locate newly created Staffbase Employee Email drafts, scheduled emails, or sent emails in their list views, even though the content was saved successfully. Previously created content remained visible throughout. No data was lost during this incident. **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]).

Read the full incident report →

Started Jul 08, 2026, 11:09 AM UTC· resolved Jul 09, 2026, 11:43 AM UTC

1. investigating Jul 08, 2026, 11:09 AM UTC

   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. monitoring Jul 08, 2026, 01:13 PM UTC

   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. resolved Jul 09, 2026, 12:12 PM UTC

   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. resolved Jul 09, 2026, 02:12 PM UTC

   **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]).

Read the full incident report →

Started Jul 06, 2026, 01:57 PM UTC· resolved Jul 07, 2026, 12:52 PM UTC

1. investigating Jul 06, 2026, 01:57 PM UTC

   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. monitoring Jul 06, 2026, 03:13 PM UTC

   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. resolved Jul 07, 2026, 12:52 PM UTC

   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. postmortem Jul 08, 2026, 01:47 PM UTC

   **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]).

Read the full incident report →

Started Jun 25, 2026, 05:18 PM UTC· resolved Jun 25, 2026, 07:02 PM UTC

1. investigating Jun 25, 2026, 05:18 PM UTC

   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. investigating Jun 25, 2026, 05:23 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jun 25, 2026, 06:02 PM UTC

   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. resolved Jun 25, 2026, 07:02 PM UTC

   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. postmortem Jul 13, 2026, 03:08 PM UTC

   **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]).

Read the full incident report →

Started Jun 18, 2026, 08:03 PM UTC· resolved Jun 18, 2026, 10:25 PM UTC

1. investigating Jun 18, 2026, 08:03 PM UTC

   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. identified Jun 18, 2026, 09:02 PM UTC

   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. resolved Jun 18, 2026, 10:25 PM UTC

   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. postmortem Jun 24, 2026, 03:04 PM UTC

   **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]).

Read the full incident report →

Started Jun 18, 2026, 04:30 PM UTC· resolved Jun 18, 2026, 07:18 PM UTC

1. investigating Jun 18, 2026, 05:06 PM UTC

   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. investigating Jun 18, 2026, 05:07 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jun 18, 2026, 05:22 PM UTC

   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. resolved Jun 18, 2026, 07:18 PM UTC

   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. postmortem Jun 23, 2026, 01:25 PM UTC

   **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]).

Read the full incident report →

Started Jun 12, 2026, 09:30 AM UTC· resolved Jun 12, 2026, 09:30 AM UTC

1. resolved Jun 18, 2026, 12:31 PM UTC

   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].

Read the full incident report →

Started Jun 11, 2026, 01:48 PM UTC· resolved Jun 11, 2026, 02:27 PM UTC

1. investigating Jun 11, 2026, 01:48 PM UTC

   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. identified Jun 11, 2026, 02:05 PM UTC

   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. monitoring Jun 11, 2026, 02:11 PM UTC

   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. resolved Jun 11, 2026, 02:27 PM UTC

   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. postmortem Jun 16, 2026, 03:22 PM UTC

   **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]).

Read the full incident report →

Started Jun 03, 2026, 01:49 PM UTC· resolved Jun 03, 2026, 02:52 PM UTC

1. investigating Jun 03, 2026, 01:49 PM UTC

   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. resolved Jun 03, 2026, 02:52 PM UTC

   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. postmortem Jun 08, 2026, 02:19 PM UTC

   **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]).

Read the full incident report →

Started Jun 02, 2026, 02:14 PM UTC· resolved Jun 03, 2026, 01:07 PM UTC

1. investigating Jun 02, 2026, 02:14 PM UTC

   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. monitoring Jun 02, 2026, 03:34 PM UTC

   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. resolved Jun 03, 2026, 01:07 PM UTC

   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. postmortem Jun 05, 2026, 08:50 AM UTC

   **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]).

Read the full incident report →

Started May 20, 2026, 03:09 PM UTC· resolved May 21, 2026, 07:10 AM UTC

1. investigating May 20, 2026, 03:09 PM UTC

   Affected feature: Emails Some customers may be experiencing that emails are not being received by their users. 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. monitoring May 20, 2026, 04:20 PM UTC

   We have adjusted the available resources to resolve the issue, and customers should see sent emails hitting their users' inboxes again. We will continue to monitor the systems until we are sure the issue is fully resolved.

3. resolved May 21, 2026, 07:10 AM UTC

   This incident has been resolved, and all delayed emails have been sent successfully. 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!

Read the full incident report →

Started Apr 27, 2026, 11:48 AM UTC· resolved Apr 27, 2026, 02:46 PM UTC

1. investigating Apr 27, 2026, 11:48 AM UTC

   Affected feature: App/Intranet/Email We have received reports that some customers on the Europe System are experiencing very slow or unresponsive behavior in the App/Intranet. Our teams are investigating the behavior 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. monitoring Apr 27, 2026, 01:21 PM UTC

   We have taken measures to address the degraded performance on the Europe System, and performance levels are improving. Users should now experience normal behavior again in the App/Intranet. We will continue to monitor the system closely to ensure performance remains stable. If you continue to experience slow or unresponsive behavior, please contact our support at [email protected]. We’re happy to help.

3. resolved Apr 27, 2026, 02:46 PM UTC

   The issue causing degraded performance on the Europe System has been resolved, and all systems are operating normally. We apologize for any inconvenience this may have caused. If you continue to experience any issues, please reach out to our support at [email protected].

4. postmortem Apr 30, 2026, 09:14 AM UTC

   **Summary** On April 27, 2026, between 1:25 PM and 2:16 PM \(CEST\) and again between 4:02 PM and 4:06 PM \(CEST\), customers on the European System experienced service interruptions and inconsistent platform performance. Our teams successfully identified the cause and restored full service functionality. **What Happened** A recent update introduced a specific background process that led to unexpectedly high system utilization within our internal system. This caused the internal system to reach its processing limits, resulting in slow loading times and connectivity errors for the platform. To resolve the issue, our team reverted the recent update and performed a manual reset of the affected internal service components to clear the backlog of processes. While a similar trend was briefly observed on the Americas System, preemptive adjustments were made to ensure that service there remained stable. **Impact** Between 1:25 PM and 2:16 PM \(CEST\) and between 4:02 PM and 4:06 PM \(CEST\), customers on the European System experienced intermittent service interruptions. During these periods, users may have encountered difficulties accessing the App and Intranet or experienced significant delays while navigating the platform. While some symptoms were briefly detected on the Americas System, there was no significant impact on functionality for customers in that region. **Future Improvements** We will implement additional checks for the operation of the affected service component and optimize the subsequent alerting to ensure that similar issues are detected and resolved 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]).

Read the full incident report →

Started Apr 24, 2026, 05:03 PM UTC· resolved Apr 28, 2026, 01:18 PM UTC

1. investigating Apr 24, 2026, 05:03 PM UTC

   Affected feature: Entra Contact Syncing Some customers may be experiencing a delay in sending test emails on Email Modern. We have not noticed this to be an issue affecting all customers, only some. 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. identified Apr 24, 2026, 06:57 PM UTC

   We have identified the cause of the synchronization failures, our teams are currently working on applying the necessary configuration fixes to restore normal synchronization behavior. We will provide another update as soon as more information is available. We apologize for the inconvenience. If you have any questions regarding this topic, please reach out to our support at [email protected].

3. monitoring Apr 27, 2026, 12:58 PM UTC

   We have implemented the necessary configuration fixes to address the synchronization failures, and we are seeing an improvement in behavior. Users should now experience normal synchronization behavior again. We will continue to monitor the system closely to ensure stability remains consistent. If you continue to experience issues with your synchronization, please contact our support team at [email protected]. We’re happy to help.

4. resolved Apr 28, 2026, 01:18 PM UTC

   The issue causing synchronization failures has been resolved, and all systems are operating normally. We apologize for any inconvenience this may have caused. If you continue to experience any issues, please reach out to our support at [email protected].

Read the full incident report →

Started Apr 23, 2026, 01:29 PM UTC· resolved Apr 23, 2026, 03:35 PM UTC

1. investigating Apr 23, 2026, 01:29 PM UTC

   Affected feature: News & Media We have received reports that some customers are experiencing issues when creating News posts. Additionally, we are aware that images may not load correctly for some users. Our teams are investigating the behavior 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. identified Apr 23, 2026, 01:46 PM UTC

   We have identified the root cause of the issues affecting News post creation and image loading. Our teams are now working to implement a fix to restore full functionality. We will provide a further update as soon as more information is available.

3. resolved Apr 23, 2026, 03:35 PM UTC

   The issue regarding News post creation and image loading has been resolved. All systems are operating normally. 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!

Read the full incident report →

Started Apr 06, 2026, 01:20 PM UTC· resolved Apr 06, 2026, 02:17 PM UTC

1. investigating Apr 06, 2026, 01:20 PM UTC

   Affected feature: Email Modern Some customers may be experiencing an inability to find posts via the News Block that were published after April 1st, 2026. 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. resolved Apr 06, 2026, 02:17 PM UTC

   The issue is resolved, and newly published News Posts are discoverable in the News Block in Staffbase Email. 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!

3. postmortem Apr 08, 2026, 12:43 PM UTC

   **Resolved**: Issues with News Block content availability on Americas system **Summary** Between April 3rd and April 8th, some customers on our Americas system experienced issues when using the News Block within Email Modern. During this time, newly published posts were not appearing in the search results, preventing them from being easily inserted into email drafts. **Root Cause** The issue was caused by a technical limitation in our automated search indexing process. This prevented the news search from updating with new news posts, meaning any content published after the start of the incident was not recognized by the News Block or other search-dependent features. **Resolution** Our engineering teams identified the bottleneck in the search indexing process and increased the available resources for this system. This allowed the backlog of posts to be processed and restored full functionality to the news post search. **Next Steps** To prevent this from happening again, we have permanently adjusted the resource allocation for this process and improved our monitoring to alert us earlier if search index delays occur. We apologize for the inconvenience this caused and for the additional manual effort required to link posts during this period. If you have any remaining questions, please reach out to our support team at [[email protected]](mailto:[email protected]).

Read the full incident report →

Started Mar 30, 2026, 02:20 PM UTC· resolved Mar 30, 2026, 05:58 PM UTC

1. investigating Mar 30, 2026, 02:20 PM UTC

   Affected feature: Test Emails Some customers may be experiencing a delay in sending test emails on Email Modern. We have not noticed this to be an issue affecting all customers, only some. 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. resolved Mar 30, 2026, 05:58 PM UTC

   The issue is resolved, and all customers are reporting test sends to be working again for all drafts. 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 with test sends. We’re happy to help!

Read the full incident report →