Staffbase Outage History

Started Mar 28, 2026, 04:20 AM UTC· resolved Mar 28, 2026, 05:21 AM UTC

1. investigating Mar 28, 2026, 04:20 AM UTC

   Affected feature: SSO login Users may experience difficulties logging into the app or intranet via Single Sign-On (SSO). Our teams are actively working to identify the root cause and resolve the issue as quickly as possible. We will provide updates as soon as more information becomes available. To check which system your application is hosted on, navigate to Studio → Settings → API Access and review the tag displayed next to the title. We apologize for any inconvenience this may cause. If you have questions or require assistance, please contact our support team at [email protected]

2. investigating Mar 28, 2026, 04:31 AM UTC

   We are continuing to investigate this issue.

3. investigating Mar 28, 2026, 04:33 AM UTC

   We are continuing to investigate this issue.

4. investigating Mar 28, 2026, 04:42 AM UTC

   We have potentially identified the source of the issue affecting SAML-based configurations and are continuing to investigate the root cause. Our teams are actively working to validate this finding and implement a resolution as quickly as possible. We will share further updates as more information becomes available. Thank you for your continued patience.

5. monitoring Mar 28, 2026, 05:19 AM UTC

   A fix has been implemented and we are monitoring the results.

6. resolved Mar 28, 2026, 05:21 AM UTC

   Incident Update – Resolved The issue affecting SAML-based configurations has been identified and resolved. The impact was less severe than initially anticipated. We observed a temporary degradation in performance in the Pacific region, which has now been fully addressed. At this time, all systems related to the main incident are operating normally. Please note that there are still elevated error rates in the prod/de1 environment; however, these are unrelated to the original incident. Our teams are actively monitoring logs and metrics to ensure overall system stability and to identify any remaining customer-specific issues. We apologize for any inconvenience caused and appreciate your patience while we worked to resolve this matter.

Read the full incident report →

Started Mar 25, 2026, 03:41 PM UTC· resolved Mar 25, 2026, 07:36 PM UTC

1. investigating Mar 25, 2026, 03:41 PM UTC

   Affected feature: App/Intranet & Employee Email We have received reports that some customers in the Americas region are experiencing very slow or unresponsive behavior in the App/Intranet and Staffbase Employee Email. Our teams are investigating the behavior 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 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 Mar 25, 2026, 04:30 PM UTC

   Our engineering teams took immediate actions to restore full service. We will continue to closely monitor the systems and provide a final update to confirm full resolution.

3. resolved Mar 25, 2026, 07:36 PM UTC

   The issue is resolved, and the system has remained stable. 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. postmortem Apr 01, 2026, 07:45 AM UTC

   **Summary** On March 25, 2026, between 4:29pm and 5:29pm \(UTC\), customers on the Americas System experienced a period of severe performance degradation and service unavailability. The issue was identified as a database resource constraint, which was mitigated and fully resolved the same day. **What Happened** The Americas System experienced a performance bottleneck within its internal database layer. Engineering teams identified that a specific background service required additional memory capacity to handle the current data load. To resolve the incident, we increased the allocated capacity for this system in two stages. Performance returned to normal levels by 5:28pm, followed by a period of monitoring before final resolution. **Impact** Between 4:29pm and 5:28pm \(UTC\), some customers on the Americas System were unable to reliably use the platform. **Future Improvements** We are taking the following steps to improve service resilience: * **Environment Parity:** Standardizing resource ratios across all global regions to ensure consistent headroom. * **Enhanced Monitoring:** Implementing specific telemetry for resource utilization to detect capacity requirements more quickly. We apologize for the inconvenience this caused. Thank you for your patience while we work to improve our services. If you have any questions, please reach out to our support team at [[email protected]](mailto:[email protected]).

Read the full incident report →

Started Feb 26, 2026, 06:56 PM UTC· resolved Feb 26, 2026, 07:33 PM UTC

1. investigating Feb 26, 2026, 06:56 PM UTC

   Affected feature: Studio, Email. Some administrators may be experiencing an inability to upload media or send emails in the US system. 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 Feb 26, 2026, 07:21 PM UTC

   We have made changes on the backend to resolve the issue and media uploads and email sending should be possible again. We will continue to monitor the systems until we are sure the issue is fully resolved.

3. resolved Feb 26, 2026, 07:33 PM UTC

   The issue is resolved, and the system has remained stable. 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. postmortem Mar 12, 2026, 05:21 PM UTC

   **Summary** On February 26, 2026, between 19:49 and 20:24 \(UTC\), customers on the US Server experienced issues uploading media files and sending emails containing attachments. The issue was identified and resolved the same day. **What Happened** A background process responsible for managing file uploads and email delivery reached a system utilization limit, which prevented new tasks from being processed. Once the issue was identified, our team made the necessary adjustments to stabilize the system and restore normal operation. Following these adjustments, all pending tasks were processed successfully and service was fully restored by 20:24 \(UTC\). **Impact** Between 19:49 and 20:24 \(UTC\), customers on the US Server were temporarily unable to upload images or videos within the Studio. Additionally, the delivery of emails with media attachments was affected during this timeframe. Other platform functionalities remained available to users throughout this period. **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 Feb 23, 2026, 04:55 PM UTC· resolved Feb 23, 2026, 09:41 PM UTC

1. investigating Feb 23, 2026, 04:55 PM UTC

   Affected feature: Calendar Plugin Some customers may be experiencing an error with the calendar plugin not loading with a 401 error. 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. monitoring Feb 23, 2026, 07:26 PM UTC

   A fix has been implemented and we're monitoring the results. Calendars should now be available again.

3. resolved Feb 23, 2026, 09:41 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 20, 2026, 12:31 PM UTC· resolved Feb 23, 2026, 10:32 AM UTC

1. investigating Feb 20, 2026, 12:31 PM UTC

   Affected feature: App/Intranet & EMail We are currently experiencing a major disruption on the US system. The App/Intranet and EMail are not accessible at the moment. Our teams are investigating this with the highest priority and are working to restore the service as quickly as possible. We will share further updates soon. We sincerely apologize for the inconvenience. If you have any urgent questions, please reach out to our support at [email protected]

2. investigating Feb 20, 2026, 12:36 PM UTC

   We are continuing to investigate this issue.

3. identified Feb 20, 2026, 01:23 PM UTC

   We’ve identified the issue and are seeing slight improvements with the affected products becoming available again. Our team is still actively investigating and we will provide further updates as soon as more information becomes available.

4. monitoring Feb 20, 2026, 01:52 PM UTC

   We have implemented measures to address the issue, and the affected products are available again. Our team continues to monitor the situation closely.

5. investigating Feb 20, 2026, 02:33 PM UTC

   We are currently experiencing partial outages in the system again and are actively investigating the cause. Our team is working to restore normal operations as quickly as possible and will provide updates as soon as more information becomes available.

6. monitoring Feb 20, 2026, 03:47 PM UTC

   The system is now operating normally again, and services are fully available. We will continue to monitor performance closely over the coming period to ensure ongoing stability and will provide further updates.

7. resolved Feb 23, 2026, 10:32 AM UTC

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

8. postmortem Feb 24, 2026, 10:22 AM UTC

   **Postmortem** **Summary** As our investigation of the incident is now complete, we would like to share more details about the issue that occurred on **February 20, 2026, between 12:45 PM CET and 4:17 PM CET** in our **US hosting environment**. **What happened** A recent backend release unintentionally activated a new search-related configuration, which triggered an unusually high volume of background processing. This caused excessive database activity that quickly consumed available storage capacity. As a result, the database became unstable, which led to backend services becoming temporarily unavailable. While initial recovery actions restored service, the issue briefly recurred before additional mitigation measures were applied. Once the underlying cause was identified, we implemented safeguards to stop the background processing, increased database storage capacity, and stabilized the system. **Impact** During the specified timeframe, customers hosted in the US environment were unable to access their apps, intranet, emails, and other dependent services. The total duration of the disruption was around **2 hours and 26 minutes**, across several shorter outage windows. During this time, users were unable to log in or use the platform. Other regions were not affected. **Future Improvements** We are taking several steps to help prevent similar incidents in the future, including: * Improving safeguards around feature activations to prevent unexpected load on critical systems * Increasing database storage resilience and ensuring additional capacity headroom * Enhancing monitoring and alerting to detect abnormal storage growth earlier * Introducing additional safety mechanisms to protect database stability We recognize the significance of this incident and have addressed it with the highest level of urgency and attention. Maintaining a secure, stable, and reliable platform is central to our commitment to you. We sincerely regret the disruption and any inconvenience it may have caused. Please rest assured that we are continuously strengthening our systems and processes to uphold the level of performance and reliability you expect from us. We appreciate your understanding and patience throughout this situation. Please contact us at [**[email protected]**](mailto:[email protected]) if you have any further questions.

Read the full incident report →

Started Feb 19, 2026, 03:42 PM UTC· resolved Feb 27, 2026, 03:22 PM UTC

1. investigating Feb 19, 2026, 03:42 PM UTC

   Affected feature: App/Intranet & Employee Email We have received reports that some customers on the US system are experiencing very slow or unresponsive behavior in the App/Intranet and Staffbase Employee Email. Our teams are investigating the behavior 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 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 Feb 19, 2026, 07:05 PM UTC

   We have taken measures to address the degraded performance on the US system, and performance levels are back to normal. Users should now experience normal loading times in the App/Intranet and Employee Email. 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 Feb 27, 2026, 03:22 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 Feb 18, 2026, 05:13 PM UTC· resolved Feb 19, 2026, 09:45 AM UTC

1. investigating Feb 18, 2026, 05:13 PM UTC

   Affected feature: App/Intranet & Employee Email We have received reports that some customers on the US system are experiencing very slow or unresponsive behavior in the App/Intranet and Staffbase Employee Email. Our teams are investigating the behavior 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 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 Feb 18, 2026, 05:34 PM UTC

   We have taken measures to address the degraded performance on the US system, and performance levels are improving. Users should now experience normal behavior again in the App/Intranet and Employee Email. 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 Feb 19, 2026, 09:45 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!

Read the full incident report →

Started Feb 13, 2026, 06:56 PM UTC· resolved Feb 13, 2026, 11:10 PM UTC

1. investigating Feb 13, 2026, 06:56 PM UTC

   Affected feature: Email Modern Some email recipients may be experiencing an issue wherein the header image on emails sent via Email Modern are not displaying in the email as received. 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 Feb 13, 2026, 10:25 PM UTC

   We have found the cause of Email Header Image not displaying in the received email and are now working to put a fix in place.

3. monitoring Feb 13, 2026, 10:51 PM UTC

   We have released an update to resolve the issue and the email header images should be rendered again in the received email. We will continue to monitor the systems until we are sure the issue is fully resolved.

4. monitoring Feb 13, 2026, 10:55 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Feb 13, 2026, 11:10 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!

6. postmortem Feb 19, 2026, 02:24 PM UTC

   **Postmortem** **Summary** As our investigation of the incident is now complete, we would like to share more details about the issue that occurred between **February 13, 11:15 AM CEST**, and **February 14, 08:30 AM CEST**. **What happened** A bug in our email tracking functionality caused certain images in emails to be modified incorrectly during sending. As a result, some images could not be displayed when emails were delivered to recipients. This issue only affected live email sends and did not impact test emails, which followed a different sending process. Once the issue was identified, we implemented a mitigation to ensure tracking functionality would no longer interfere with image display. A permanent fix was then deployed to fully resolve the underlying problem. **Impact** During the specified timeframe, recipients of affected emails may have experienced missing images, such as header or content images, when viewing emails. This impacted the visual presentation of emails but did not affect email delivery itself. **Future Improvements** We are implementing measures to help prevent similar incidents in the future, including: * Improving automated test coverage for email functionality * Simplifying tracking logic to reduce complexity * Enhancing monitoring and investigation capabilities ‌ We are sorry for the inconvenience this has caused. Please contact us at [**[email protected]**](mailto:[email protected]) if you have any further questions regarding this topic.

Read the full incident report →

Started Feb 12, 2026, 10:10 AM UTC· resolved Feb 12, 2026, 04:42 PM UTC

1. investigating Feb 12, 2026, 10:10 AM UTC

   Customers may be experiencing slower performance and longer loading times on our german system. 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 Feb 12, 2026, 10:37 AM UTC

   We have implemented changes to resolve the issue and see performance going back to normal. We will continue to monitor the systems until we are sure the issue is fully resolved.

3. resolved Feb 12, 2026, 04:42 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 Feb 18, 2026, 03:11 PM UTC

   ## **Summary** Now that our investigation of the incident is complete, we would like to share more details about the issue that occurred between **February 12, 10:45 CET and 12:00 CET**. ## **What happened** A configuration setting that did not fully account for how memory is utilized during high-traffic periods caused our system to slow down. This alarmed our teams, who immediately worked on increasing system capacity and restoring the performance of our system. ## **Impact** During the mentioned timeframe, users on our **German system** experienced long loading times and unresponsiveness when accessing the app or intranet. This was particularly noticeable when using the **search functionality**, which may have failed to return results or timed out. ## **Future Improvements** We will explore options to introduce additional testing setups and more granular monitoring to prevent similar issues in the future. We have also permanently increased the performance of our storage infrastructure. Please contact us at [[email protected]](mailto:[email protected]) if you have any further questions or feedback regarding this topic.

Read the full incident report →

Started Feb 05, 2026, 05:00 PM UTC· resolved Feb 05, 2026, 05:00 PM UTC

1. resolved Feb 05, 2026, 05:04 PM UTC

   Affected feature: Studio Page Management Between February 4th, 5:15 PM CET and February 5th, 5:45 PM CET, some users may have noticed incorrect “Updated” timestamps for pages in the Studio. Many pages were erroneously labeled as updated during a specific window on February 4th. Our engineering team identified the root cause and has restored the timestamps to reflect the actual last content change. As of 5:45 PM CET today, all timestamps have been corrected. No action is required from users. 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. postmortem Feb 17, 2026, 01:15 PM UTC

   **Summary** As our investigation of the incident is now complete, we would like to share more details about the issue that occurred between February 4th, 5:15 PM CET and February 5th, 5:45 PM CET leading to incorrect update time stamps for some pages. **What happened** In preparation for our February 12th release, a new property was added to the “Update Reminder” feature. While deploying this configuration change, a system process unintentionally triggered a timestamp refresh for all pages where an update reminder was active. This caused the system to treat the configuration change as a content update. **Impact** Between February 4th, 5:15 PM CET and February 5th, 5:45 PM CET, pages with an active update reminder displayed an incorrect timestamp. This reflected the timing of our internal system change rather than actual edits made to the page content. Our developers successfully identified the cause and reverted the timestamps for all impacted pages by February 5th, 5:45 PM CET. No page content was modified or lost during this process. **Future improvements** We will implement additional safety guards that prevent configuration changes from leading the system to interpret them as content changes. 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 Jan 26, 2026, 10:27 AM UTC· resolved Mar 06, 2026, 08:52 AM UTC

1. investigating Jan 26, 2026, 10:27 AM UTC

   Affected feature: App & Intranet We have received reports that the Staffbase App and Intranet may not load correctly when accessed via mobile data on the Telekom network. This behavior does not occur consistently and seems to affect only some users. Initial analysis suggests that the issue may be related to the network routing (peering) between Telekom and our CDN provider Cloudflare. Our teams are currently investigating the behavior and will work to address it as quickly as possible. We will share more information as soon as it becomes available. We apologize for the inconvenience. If you have any questions regarding this topic, please reach out to our support at [email protected]

2. monitoring Jan 29, 2026, 03:17 PM UTC

   We are aware that some users on the Telekom network may still experience intermittent loading issues within the app. The root cause has been identified as a routing issue between Telekom and Cloudflare, the global CDN provider. While this is an external network conflict, we take the situation very seriously and are in contact with Cloudflare to expedite a sustainable solution. We estimate that only a small number of users are affected. If you are currently experiencing issues, we recommend fully closing the app, waiting a few minutes, and then restarting it. In many cases, this allows the network to re-establish a stable connection. Another possible solution is to connect via a different network—for example, switching from Wi-Fi to mobile data. We are monitoring the situation closely and will provide further updates as soon as more information becomes available. Thank you for your patience and understanding.

3. resolved Mar 06, 2026, 08:52 AM UTC

   This incident has been resolved. Summary: Our internal systems are fully operational and performing as expected. We understand how important consistent performance is for your work, and we appreciate your patience while we investigated these reports. Root Cause Analysis: Throughout our investigation, we identified that intermittent loading delays when accessing the Staffbase App or Intranet were caused by external network routing and capacity constraints within the Deutsche Telekom AG network (including subsidiary providers using Telekom infrastructure). These delays typically occur during general peak internet traffic hours. Because this behavior originates from interconnections between independent network providers, it is outside of Staffbase’s direct technical control. This is not a malfunction of the Staffbase application, and other affected global platforms are experiencing similar symptoms during those occurrences. Next Steps: While we continue to monitor the situation alongside our infrastructure partners, we recommend that affected users or their IT departments reach out to their internet service provider (ISP) for further assistance. If you have any further questions, our team is here to help at [email protected].

Read the full incident report →

Started Jan 22, 2026, 10:04 AM UTC· resolved Jan 22, 2026, 05:08 PM UTC

1. identified Jan 22, 2026, 10:04 AM UTC

   Affected feature: CSV Import We’re currently seeing issues with the CSV import in cases where entries include commas, quotation marks, or line breaks. These special characters can lead to incorrect or failed imports. Our teams have identified this behavior and are already working on a fix. We will continue to monitor the situation and share updates as soon as possible. We apologize for the inconvenience this may cause. If you have any questions or need support with a specific import, feel free to reach out to us at [email protected].

2. monitoring Jan 22, 2026, 01:22 PM UTC

   A fix has been implemented to resolve the issue affecting CSV imports that included commas, quotation marks, or line breaks. Imports should now work as expected again. We will continue to monitor the behavior to ensure everything is functioning correctly. If you notice any remaining issues or need assistance, please don’t hesitate to contact our support at [email protected]

3. resolved Jan 22, 2026, 05: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 Jan 16, 2026, 07:58 PM UTC· resolved Jan 16, 2026, 09:20 PM UTC

1. identified Jan 16, 2026, 07:58 PM UTC

   We have identified the root cause for analytics not being shown for emails send out in the last 6 hours (starting 3:00 PM CET) and will now take steps to fix the issue. No data is lost and the analytics for the affected mails will be available again after this incident is resolved.

2. resolved Jan 16, 2026, 09:20 PM UTC

   The issue is resolved and analytics are shown again for the affected mails. 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 Jan 20, 2026, 01:46 PM UTC

   ## Summary As our investigation of the incident is complete, we would like to provide you with more detailed information about the incident that occurred on **January 16, between 03:00 p.m. and 10:20 p.m. \(CET\)**, leading to issues with the visibility of analytics data for sent emails. ## What happened The incident was triggered by a **database migration** that inadvertently impacted the synchronization of mail analytics. This caused a delay in the processing and display of performance metrics for emails sent during the affected window. Once the root cause was identified, our engineering team implemented a fix to restore data flow. We have confirmed that **no data was lost**; all analytics tracked during this period were successfully backfilled and are now visible. ## Impact Between **03:00 p.m. and 10:20 p.m. \(CET\)**, users were unable to view analytics for emails sent out during this window. While the emails were delivered successfully and recipient interactions were still being tracked by our systems, the data was not being rendered in the user interface. ## Future improvements To prevent similar occurrences and ensure system stability during maintenance, we will **implement a different strategy for updating data** to ensure a more performant migration and a **reasonable update duration**. 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 Jan 08, 2026, 08:21 AM UTC· resolved Jan 08, 2026, 08:21 AM UTC

1. resolved Jan 08, 2026, 08:21 AM UTC

   Affected feature: user actions—including updates, creation of news or posts, as well as email click and open tracking. Some users & administrators may have experienced not working update or deletion options for news, blocked usage of the trash feature, or changes to installations on prod/de1 not saving in the prod/de1 environment. This also affected some actions performed via API token starting at 6:51 AM CET. Our teams resolved the issue at 8:48 AM CET. 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. postmortem Jan 14, 2026, 10:08 AM UTC

   **Summary** As our investigation of the incident is complete, we would like to provide you with more detailed information about the incident that occurred on January 8, between 06:51 a.m. and 08:45 a.m. \(CET\), leading to errors with user actions - including updates, creation of news or posts, as well as email click and open tracking. ‌ **What happened** Our internal server messaging system experienced connectivity issues after a regular restart. This led to some sent internal server messages not being processed as intended on the German system. By adjusting the configuration responsible and implementing additional resilience measures, we were able to correct the behavior and fully restore the availability. ‌ **Impact** Between 06:51 a.m. and 08:45 a.m. \(CET\), our system reported issues when performing updates on the Employee App & Intranet as well as some click rate actions on Staffbase Email. Some update and publishing actions could not be performed and led to error messages. **‌** **Future improvements** We will implement additional checks for the operation of the affected service component and optimize the subsequent alerting to ensure that no more outages will occur due to lost syncs after regular restarts. 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].

Read the full incident report →

Started Dec 05, 2025, 09:09 AM UTC· resolved Dec 05, 2025, 09:39 AM UTC

1. investigating Dec 05, 2025, 09:09 AM UTC

   Affected feature: App/Intranet/Email and Ticket System We are currently investigating an outage affecting both our platforms and our ticketing system. The issue appears to be related to a Cloudflare service error, which is causing interruptions in access and functionality. Our team is actively monitoring the situation and working with Cloudflare to identify the root cause and restore full service as quickly as possible. For more details on the Cloudflare incident, please refer to: https://www.cloudflarestatus.com/history We apologize for the inconvenience.

2. monitoring Dec 05, 2025, 09:26 AM UTC

   Cloudflare has implemented a fix for the issue that caused our platform and ticketing system to become unavailable. All services should now be operational again. We continue to monitor the performance.

3. resolved Dec 05, 2025, 09:39 AM UTC

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

4. postmortem Dec 11, 2025, 11:38 AM UTC

   **Summary:** As our investigation of the incident is complete, we would like to provide details about the outage that occurred between December 5, 2025, 09:53 CET and December 5, 2025, 10:15 CET. **What happened:** All environments were temporarily unreachable. This affected both customer-facing applications and the ticket system. The outage was caused by an external Cloudflare service disruption. It was resolved once Cloudflare implemented a fix, approximately 40 minutes after the initial impact. All applications and environments became accessible again, and normal operations resumed. **Impact:** During the incident, customers were unable to access any of their applications or the ticket system. No data was lost, and all systems remained intact. **Future improvements:** We are evaluating ways to improve internal monitoring and accessibility during external outages, including ensuring that internal tools remain available even if external providers experience disruptions. For further inquiries or assistance, please contact us at [**[email protected]**](mailto:[email protected]).

Read the full incident report →

Started Nov 25, 2025, 04:48 PM UTC· resolved Nov 25, 2025, 08:51 PM UTC

1. investigating Nov 25, 2025, 04:48 PM UTC

   Customers may be experiencing an issue in the App where restoring a page from its version history does not complete as expected. Customers have reported that selecting a version to restore results in no changes being applied. 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. monitoring Nov 25, 2025, 05:49 PM UTC

   We have released an update to resolve the issue. Page Version History should be working as intended again We will continue to monitor the systems until we are sure the issue is fully resolved. If you have any questions, or are still having difficulties, please reach out to our support at [email protected].

3. resolved Nov 25, 2025, 08:51 PM UTC

   The issue regarding page version history is resolved. Please get in touch with us at [email protected] in case you're still having any problems.

Read the full incident report →

Started Nov 25, 2025, 09:12 AM UTC· resolved Nov 25, 2025, 10:45 AM UTC

1. investigating Nov 25, 2025, 09:12 AM UTC

   Affected feature: Pages Some customers may be experiencing an issue where newly created pages do not appear in the Studio or via search. 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. investigating Nov 25, 2025, 10:03 AM UTC

   We have identified that the issue impacts not only Pages but also additional features such as News, Forms, Surveys, Calendars, and other content-related functionalities. Newly created content may not appear in the Studio or via search. Our teams continue to investigate the root cause and are working to resolve the incident as quickly as possible. We will provide further updates as soon as we have more information.

3. resolved Nov 25, 2025, 10:45 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. postmortem Dec 11, 2025, 09:56 AM UTC

   **Summary:** As our investigation of the incident is complete, we would like to provide you with more detailed information about the incident that occurred on November 24, 2025, between 17:30 CET and November 25, 2025, 11:43 CET. **What happened:** Due to malformed documents in our system, newly created content was temporarily not appearing in Studio overview or search. The issue impacted Pages as well as other features, including News, Forms, Surveys, Calendars, and other content-related functionalities. Our team removed the affected documents and cleaned up system indexes, restoring full search and Studio functionality. **Impact:** During the incident, users were unable to locate newly created content via Studio or search. All content remained accessible through direct links or menu navigation. **Future improvements:** We are adding stricter data validation and enhanced monitoring to prevent similar issues in the future. For further inquiries or assistance, please feel free to contact us at [[email protected]](mailto:[email protected]).

Read the full incident report →

Started Nov 17, 2025, 12:15 PM UTC· resolved Nov 24, 2025, 12:54 PM UTC

1. investigating Nov 17, 2025, 12:15 PM UTC

   We have received reports that some media files are currently not loaded on the US system. Our teams are investigating the behavior 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 the Studio > Settings > API Access and checking the tag next to the title. We apologize for the inconvenience this may cause. If you have any questions regarding this topic, please reach out to our support at [email protected].

2. monitoring Nov 17, 2025, 04:20 PM UTC

   We have increased resources to resolve the issue and media files should be loading again. We will continue to monitor the systems until we are sure the issue is fully resolved.

3. monitoring Nov 18, 2025, 05:02 AM UTC

   The issue has recurred and persists. We have escalated the investigation to the highest priority, requiring direct and immediate involvement from our dedicated Infrastructure team to resolve the underlying cause.

4. investigating Nov 18, 2025, 09:27 AM UTC

   Ongoing investigations indicate that there might be minor limitations in the DE system, which may likewise affect Staffbase Email. We’ll continue to keep you updated as we learn more. We’re sorry for the disruption. If you have any questions in the meantime, please feel free to reach out to us at [email protected].

5. monitoring Nov 18, 2025, 04:53 PM UTC

   Over the past few hours, the platform has remained stable. Our engineering teams are closely monitoring all systems and actively working on the underlying issue with the highest priority. They are reviewing logs, running additional diagnostics, and applying targeted optimizations to ensure overall stability and prevent further disruptions. We will continue to keep you updated as we make progress.

6. resolved Nov 24, 2025, 12:54 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!

7. postmortem Dec 16, 2025, 02:38 PM UTC

   **Summary:** As our investigation of the incident is complete, we would like to provide details about the outage that occurred between November 17, 2025, 11:00AM and November 18, 2025, 2:00PM \(CET\). **What happened:** German and US environment were experiencing random failures loading images, videos, and posts across multiple pages. The issue also affected notifications and potentially other services, causing slow or failed requests. Implementing a fix solved the issue and normal operations resumed. **Impact:** During the incident, some users experienced failed loading of media files and other content unable to reload them. No data was lost, and all systems remained intact. **Future improvements:** We are evaluating ways to improve internal monitoring and the underlying network infrastructure. For further inquiries or assistance, please contact us at [**[email protected]**](mailto:[email protected]).

Read the full incident report →

Started Nov 05, 2025, 08:07 AM UTC· resolved Nov 05, 2025, 03:45 PM UTC

1. investigating Nov 05, 2025, 08:07 AM UTC

   We’re currently investigating an issue where custom fonts cause reactions (likes, comments, shares) to appear misaligned on the web. Our team is working to identify the cause and will share updates as they become available. We apologize for the interruption. In case you have any questions about this topic, please let us know at [email protected].

2. monitoring Nov 05, 2025, 11:46 AM UTC

   We have resolved the issue and formatting should be back to normal. We will continue to monitor the systems until we are sure the issue is fully resolved.

3. resolved Nov 05, 2025, 03:45 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. postmortem Nov 05, 2025, 04:32 PM UTC

   **Summary:** As our investigation of the incident is complete, we would like to provide you with more detailed information about the incident that occurred on November 5, 2025, between 08:00 CET and 13:00 CET. **What happened:** A recent update introduced an unintended side effect; custom fonts weren’t shown or misaligned and likes, comments, breadcrumbs to appear visually distorted in the app. **Impact:** During the incident period, users experienced distorted formatting issues. These visual and functional inconsistency affected the usability and appearance of the product. **Future improvements:** Immediate corrective action was taken, and a fix for the formatting issue has been successfully deployed. Thank you for your understanding while we continue to improve the reliability and consistency of our platform. For further inquiries or assistance, please feel free to contact us at [[email protected]](mailto:[email protected]).

Read the full incident report →

Started Nov 01, 2025, 05:00 PM UTC· resolved Nov 01, 2025, 05:00 PM UTC

1. resolved Nov 03, 2025, 02:49 PM UTC

   Between Saturday, November 1 around 6 PM CET and Sunday, November 2 around 2 PM CET, some manual and API-based post creations were temporarily disrupted. As a result, some users were unable to publish posts and received an error message. In some cases, affected posts were later published multiple times. Scheduled posts were not affected and were sent out as planned. The issue was caused by an internal service overload, which prevented certain requests from being processed correctly. Our teams resolved the issue on Sunday and post creation has been fully functional since then. We apologize for the inconvenience. If you have any questions regarding this topic, please reach out to our support at [email protected].

2. postmortem Nov 24, 2025, 09:21 AM UTC

   **Summary** Over the weekend of November 1–2, 2025, some users experienced issues when creating news posts. The posts were actually saved, but the system incorrectly reported a failure because an internal service was temporarily unavailable. This led to confusion and, in some cases, duplicate posts. **What Happened?** A core internal service that handles post-related updates became unavailable. As a result, the post was created, but the system was unable to process the final confirmation step. Users saw an error message even though their post existed. Some automated follow-up actions didn’t run as expected. **Impact** Some users experienced error messages, inconsistent post statuses, or duplicate posts when retrying. Overall platform stability was not affected. **Future Improvements** We will work on strengthening our monitoring, improving the reliability of the post-creation flow, and adding safeguards to prevent temporary service issues from showing up as false errors for users.

Read the full incident report →

Started Oct 31, 2025, 12:28 PM UTC· resolved Oct 31, 2025, 12:53 PM UTC

1. investigating Oct 31, 2025, 12:28 PM UTC

   Affected feature: Pages We have received reports of some customers experiencing issues with saving pages that contain a large amount of content. Our team has started investigating the issue and is working to resolve it as quickly as possible. 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 any inconvenience that may be caused. If you have any questions regarding this topic, please reach out to our support at [email protected].

2. resolved Oct 31, 2025, 12:53 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 Oct 15, 2025, 07:18 AM UTC· resolved Oct 15, 2025, 08:42 AM UTC

1. investigating Oct 15, 2025, 07:18 AM UTC

   Some customers may be experiencing issues with the Link Tile Widgets display appearing incorrectly. 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. investigating Oct 15, 2025, 07:20 AM UTC

   We are continuing to investigate this issue.

3. investigating Oct 15, 2025, 07:22 AM UTC

   We are continuing to investigate this issue.

4. investigating Oct 15, 2025, 07:23 AM UTC

   We are continuing to investigate this issue.

5. resolved Oct 15, 2025, 08:42 AM UTC

   This incident has been resolved. A fix has been implemented, and the Link Tile Widgets are now displaying correctly again. We apologize for any inconvenience this may have caused. Please contact us at [email protected] should you experience any further issues. We’re happy to help!

6. postmortem Oct 20, 2025, 08:37 AM UTC

   **Summary:** As our investigation of the incident is complete, we would like to provide you with more detailed information about the incident that occurred on October 15, 2025, between 08:45 CET and 10:34 CET. **What happened:** During a routine rollout of a bug fix that included modifications to the Link Tile Widget, an unintended side effect occurred, causing the Link Tile Widget to appear visually distorted - specifically, elongated in style. **Impact:** During the incident period, users experienced distorted styling in the Link Tile Widget view. Despite the visual issue, all links remained fully functional and clickable. **Future improvements:** Immediate corrective action was taken, and a fix for the styling issue has been successfully deployed. To ensure visual or styling issues are detected earlier, we have implemented additional manual visual testing steps prior to each new release.For further inquiries or assistance, please feel free to contact us at [[email protected]](mailto:[email protected]).

Read the full incident report →