Staffbase incident
[App/Intranet/Email] - App Reachability and Latency Issues
Staffbase experienced a critical incident on June 11, 2026 affecting Core API (Americas) [SLA] and Core API (Europe) [SLA], lasting 39m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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].
- 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].
- 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].
- 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].
- 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]).