Staffbase outage history

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.

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.

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

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

We are aware of the critical PHP vulnerabilities recently published (CVE-2026-109618 and CVE-2026-109619) and have been monitoring the situation closely. Emergency web application firewall rules addressing these vulnerabilities were deployed by Cloudflare on 21-Oct-2026 and are active across our infrastructure. The core Staffbase platform does not use the affected components. A small number of plugins did; these were moved to hardened base images on 21-Oct-2026, and the patched PHP versions have been rolled out to all affected components as of 22-Oct-2026. We have seen no indication of exploitation in our environment. All systems have been operating normally throughout, and no further action is required. If you have any questions regarding this topic, please reach out to our support team at [[email protected]](mailto:[email protected]).

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

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!

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.

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.

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!

We are investigating an issue with Microsoft Azure affecting parts of our European services. Some customers may experience intermittent errors or slow loading when using Common Features. We are monitoring the situation closely and will provide further updates as more information becomes available.

The issue is worsening and our European services are currently unavailable for many customers. We have identified an ongoing issue with Microsoft Azure affecting the platform and are monitoring the situation closely.

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.

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!

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

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.

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.

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!

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

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!

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!

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

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!

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.

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.

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

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.

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!

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

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.

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!

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.

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

We are continuing to monitor for any further issues.

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!

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

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

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.

We are continuing to monitor for any further issues.

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!

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

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.

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.

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!

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

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.

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.

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!

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

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

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.

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!

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

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

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.

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!

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

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

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.

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!

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

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

We are continuing to investigate this issue.

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.

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!

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