Staffbase 中断历史

1. 2026年9月4日 UTC 12:06identified

   一些客户可能会延迟发送从工作人员基地发出的电子邮件(现代电子邮件和通知电子邮件)。 我们的调查证实这些邮件是从我们一方成功发送的;延迟的原因是接收者的邮件提供者Microsoft 365/Outlook,在邮件端装入量大期间暂时推迟发送。 无需采取行动。 当接收邮件服务器通过队列工作时,延迟的电子邮件应当到达. 由于这个问题,一些拥有Microsoft 365/Outlook的客户现在可能无法收到我们的支持票的答案,所以通过支持.staffbase.com自由使用我们的票端. 感谢您在讨论这个问题时的耐心。 请联系支援小组@staffbase.com.

2. 2026年9月4日 UTC 15:05resolved

   这个问题已经解决。 我们对此造成的不便表示歉意。 请联系我们[[email protected]](https://[email protected]),以防你仍有问题. 我们很乐意帮忙!

3. 2026年9月4日 UTC 15:08resolved

   这个问题已经解决。 我们对此造成的不便表示歉意。 请联系我们@stabbase.com 以防你还有问题。 我们很乐意帮忙!

自动翻译自官方事件更新。

1. 2026年9月4日 UTC 11:47identified

   一些客户可能会延迟发送从工作人员基地发出的电子邮件(现代电子邮件和通知电子邮件)。 我们的调查证实这些邮件是从我们一方成功发送的;延迟的原因是接收者的邮件提供者Microsoft 365/Outlook,在邮件端装入量大期间暂时推迟发送。 无需采取行动。 当接收邮件服务器通过队列工作时,延迟的电子邮件应当到达. 由于这个问题,一些拥有Microsoft 365/Outlook的客户现在可能无法收到我们的支持票的答案,所以通过支持.staffbase.com自由使用我们的票端. 感谢您在讨论这个问题时的耐心。 请联系支援小组@staffbase.com.

2. 2026年9月4日 UTC 15:07resolved

   这个问题已经解决。 我们对此造成的不便表示歉意。 请联系我们@stabbase.com 以防你还有问题。 我们很乐意帮忙!

自动翻译自官方事件更新。

1. 2026年9月3日 UTC 09:54resolved

   在协调世界时9月2日15:15至15:30(17:15-17:30 CEST)之间,一些顾客遭遇了较高的出错率和缓慢的表现,影响了我们欧盟和美国托管的环境. 这是由于内部部署的变化造成的,一旦交通恢复正常,便在15分钟内自行解决。 我们对此造成的干扰感到遗憾。 如果你还看到任何相关问题.

自动翻译自官方事件更新。

1. 2026年9月3日 UTC 10:09resolved

   在协调世界时9月2日15:15至15:30(17:15-17:30 CEST)之间,一些顾客遭遇了较高的出错率和缓慢的表现,影响了我们欧盟和美国托管的环境. 这是由于内部部署的变化造成的,一旦交通恢复正常,便在15分钟内自行解决。 我们对此造成的干扰感到遗憾。 如果你还看到任何相关问题.

自动翻译自官方事件更新。

1. 2026年8月31日 UTC 10:08investigating

   受影响的特点:AI工作人员基地(Navigator、Podcast、电子邮件/Page生成) 有些顾客可能遇到AI工具的麻烦,在与他们互动时遇到错误信息. 我们的小组正在调查,并将努力尽快解决这个问题。 我们将很快分享更多信息。 我们为不方便而道歉。 请联系支援小组@staffbase.com.

2. 2026年8月31日 UTC 11:06monitoring

   我们已采取措施解决这一问题并恢复工作人员基地内所有人工智能工具/部件的全部功能。 我们将继续监测这些系统,直到我们确定这一问题得到充分解决.

3. 2026年8月31日 UTC 13:10resolved

   这一事件已经得到解决。 "导航"和其他被影响的AI功能再次全面运行. 我们对此造成的麻烦感到遗憾。 请联系我们@staffbase.com,如果你遇到其他问题的话。 我们很乐意帮忙!

自动翻译自官方事件更新。

1. 2026年8月31日 UTC 09:57investigating

   受影响的特点:AI工作人员基地(Navigator、Podcast、电子邮件/Page生成) 有些顾客可能遇到AI工具的麻烦,在与他们互动时遇到错误信息. 我们的小组正在调查,并将努力尽快解决这个问题。 我们将很快分享更多信息。 我们为不方便而道歉。 请联系支援小组@staffbase.com.

2. 2026年8月31日 UTC 10:18monitoring

   我们已采取措施解决这一问题并恢复工作人员基地内所有人工智能工具/部件的全部功能。 我们将继续监测这些系统,直到我们确定这一问题得到充分解决.

3. 2026年8月31日 UTC 12:09resolved

   这一事件已经得到解决。 "导航"和其他被影响的AI功能再次全面运行. 我们对此造成的麻烦感到遗憾。 请联系我们@staffbase.com,如果你遇到其他问题的话。 我们很乐意帮忙!

自动翻译自官方事件更新。

1. 2026年7月14日 UTC 15:06monitoring

   最新消息:我们已就该问题采取了对策。 功能已经恢复,我们正在监测所有环境以确认。 一旦监测证实完全稳定,我们将公布最后最新情况.

2. 2026年7月14日 UTC 15:06investigating

   有些用户可能会遇到一个问题,即表格,页面,或其他内容无法加载,而是显示错误消息"error.unknown.title". 我们的小组正在调查,并将努力尽快解决这个问题。 我们将很快分享更多信息。 我们为不方便而道歉。 请通过@stabbase.com获得我们的支持.

3. 2026年7月15日 UTC 08:11resolved

   这个问题已经解决。 我们对此造成的不便表示歉意。 请联系我们@stabbase.com 以防你还有问题。 我们很乐意帮忙!

4. 2026年7月15日 UTC 08:11monitoring

   我们正在继续监测任何其他问题.

5. 2026年7月27日 UTC 16:10resolved

   **摘要** 2026年7月14日,从3:50 PM到4:59 PM\(CEST\)之间,所有系统的客户都经历了影响多平台功能的服务中断. 我们的团队成功地确定了原因,恢复了全面服务功能。 ** Happened ** 最近更新引入了一个认证配置问题,导致包括页面加载、通知、电子邮件、分析以及链接跟踪在内的多个平台功能返回出错。 我们的小组查明并解决了这一问题,恢复了所有受影响系统的正常运作。 页:1 ** 未来的改进** 我们将对受影响的服务部分的运作进行更多的检查,并增强我们今后更快地发现和解决类似问题的能力。 感谢大家在我们努力改进服务和防止今后发生意外时的耐心和理解。 如果您有任何问题或关切,请毫不犹豫地联系我们的客户支助小组,地址是:[[email protected]] (mailto:[email protected]).

自动翻译自官方事件更新。

1. 2026年7月14日 UTC 14:10investigating

   有些用户可能会遇到一个问题,即表格,页面,或其他内容无法加载,而是显示错误消息"error.unknown.title". 我们的小组正在调查,并将努力尽快解决这个问题。 我们将很快分享更多信息。 我们为不方便而道歉。 请通过@stabbase.com获得我们的支持.

2. 2026年7月14日 UTC 14:54monitoring

   最新消息:我们已就该问题采取了对策。 功能已经恢复,我们正在监测所有环境以确认。 一旦监测证实完全稳定,我们将公布最后最新情况.

3. 2026年7月15日 UTC 07:37monitoring

   我们正在继续监测任何其他问题.

4. 2026年7月15日 UTC 08:08resolved

   这个问题已经解决。 我们对此造成的不便表示歉意。 请联系我们@stabbase.com 以防你还有问题。 我们很乐意帮忙!

5. 2026年7月27日 UTC 15:26postmortem

   ** 概要** 2026年7月14日,从3:50到4:59 PM\(CEST\),所有系统的客户都经历了影响多平台功能的服务中断. 我们的团队成功地确定了原因,恢复了全面服务功能。 ** 发生了什么事** 最近的一项更新引入了一个认证配置问题,导致包括页面加载、通知、电子邮件、分析以及链接跟踪在内的多个平台功能返回出错。 我们的小组查明并解决了这一问题,恢复了所有受影响系统的正常运作。 ** 影响** 在2026年7月14日的3:50至4:59 PM\(CEST\)之间,欧洲、美洲和亚太系统的客户可能遇到访问网页、通知、电子邮件、分析以及链接跟踪功能的错误。 ** 未来的改进** 我们将对受影响的服务部分的运作进行更多的检查,并在今后更迅速地发现和解决类似问题。 感谢大家在我们努力改进服务和防止今后发生意外时的耐心和理解。 如果您有任何问题或关切,请毫不犹豫地联系我们的客户支助小组,地址是:[[email protected]] (mailto:[email protected]).

自动翻译自官方事件更新。

1. 2026年7月9日 UTC 14:12investigating

   我们正在调查一个影响我们美国环境创建新的工作室电子邮件草稿和模板的问题。 在创建新草案时, 您可能会看到一个成功的保存确认, 但草案不会出现在您的草案列表中 。 现有草案和以前发送的电子邮件不受影响。 欧盟环境中的客户不受影响。 我们的团队正在积极努力查明并解决这一原因。 一旦掌握更多信息,我们将公布最新情况.

2. 2026年7月9日 UTC 15:11monitoring

   解决影响我们美国环境的新工作室电子邮件草稿的问题。 制作和观看新的草案和模板现在应像预期的那样发挥作用。 我们将继续监测这些系统,直到我们确定这一问题得到充分解决.

3. 2026年7月10日 UTC 07:11resolved

   这一事件已经得到解决。 我们对此造成的麻烦感到遗憾。 请联系我们@staffbase.com,如果你遇到其他问题的话。 我们很乐意帮忙!

4. 2026年7月14日 UTC 13:11resolved

   ** 摘要** 2026年7月9日,在上午9:01至下午4:06(CEST)之间,美洲系统的客户遇到一个问题,即新设立的工作人员基地雇员电子邮件草稿、排定的电子邮件和发送的电子邮件在各自的列表视图中没有出现。 我们的团队成功地确定了原因,恢复了全面服务功能。 ** Happened ** 一个负责充入电子邮件列表视图的背景索引进程停止了正确运行,因此新创建的草稿,预定的电子邮件,以及发送的电子邮件,尽管被成功保存,但却没有出现在各自的列表中. 用户收到确认其内容被保存,但无法定位以查看,编辑或发送. 其他区域没有受到影响。 我们的小组查明并解决了这一问题,恢复了所有受影响内容的正常可见度。 ** 2026年7月9日Between 9:01 AM和4:06 PM\(CEST\),美洲系统的客户可能无法找到新创建的员工基地员工电子邮件草稿,预定邮件,或在其列表视图中发送邮件,尽管内容保存成功. 以前创造的内容始终是显而易见的。 在这次事件中没有丢失任何数据。 ** 未来的改进** 我们将对受影响的服务部分的运作进行更多的检查,并增强我们今后更快地发现和解决类似问题的能力。 感谢大家在我们努力改进服务和防止今后发生意外时的耐心和理解。 如果您有任何问题或关切,请毫不犹豫地联系我们的客户支助小组,地址是:[[email protected]] (mailto:[email protected]).

自动翻译自官方事件更新。

1. 2026年7月9日 UTC 14:01investigating

   我们正在调查一个影响我们美国环境创建新的工作室电子邮件草稿和模板的问题。 在创建新草案时, 您可能会看到一个成功的保存确认, 但草案不会出现在您的草案列表中 。 现有草案和以前发送的电子邮件不受影响。 欧盟环境中的客户不受影响。 我们的团队正在积极努力查明并解决这一原因。 一旦掌握更多信息,我们将公布最新情况.

2. 2026年7月9日 UTC 14:19monitoring

   解决影响我们美国环境的新工作室电子邮件草稿的问题。 制作和观看新的草案和模板现在应像预期的那样发挥作用。 我们将继续监测这些系统,直到我们确定这一问题得到充分解决.

3. 2026年7月10日 UTC 06:29resolved

   这一事件已经得到解决。 我们对此造成的麻烦感到遗憾。 请联系我们@staffbase.com,如果你遇到其他问题的话。 我们很乐意帮忙!

4. 2026年7月14日 UTC 12:19postmortem

   ** 概要** 2026年7月9日,9:01 AM到4:06 PM\(CEST\)之间,美洲系统的客户经历了一个新创建的员工基地员工电子邮件草稿,预定邮件,发送邮件在各自的列表视图中没有出现的问题. 我们的团队成功地确定了原因,恢复了全面服务功能。 ** 发生了什么事** 负责填充电子邮件列表视图的背景索引进程停止了正确运行,所以新创建的草稿、预定的电子邮件和发送的电子邮件虽然被成功保存,但却没有出现在各自的列表中。 用户收到确认其内容被保存,但无法定位以查看,编辑或发送. 其他区域没有受到影响。 我们的小组查明并解决了这一问题,恢复了所有受影响内容的正常可见度。 ** 影响** 2026年7月9日9:01至4:06 PM\(CEST\)之间,美洲系统的客户可能无法找到新创建的员工基地员工邮件草稿,预定邮件,或在其列表视图中发送邮件,尽管内容被成功保存. 以前创造的内容始终是显而易见的。 在这次事件中没有丢失任何数据。 ** 未来的改进** 我们将对受影响的服务部分的运作进行更多的检查,并在今后更迅速地发现和解决类似问题。 感谢大家在我们努力改进服务和防止今后发生意外时的耐心和理解。 如果您有任何问题或关切,请毫不犹豫地联系我们的客户支助小组,地址是:[[email protected]] (mailto:[email protected]).

自动翻译自官方事件更新。

1. 2026年7月8日 UTC 11:09investigating

   受影响的特性: 菜单通知 一些用户可能会遇到未读通知计数在通知菜单中无法正确更新的问题. 我们的小组正在调查,并将努力尽快解决这个问题。 我们将很快分享更多信息。 您可以通过前往工作室来查看您的应用程序在哪个系统托管 > 设置 > API 访问并检查标题旁边的标记 。 我们为不方便而道歉。 请通过@stabbase.com获得我们的支持.

2. 2026年7月8日 UTC 13:13monitoring

   最新消息:我们已针对这个阻止未读通知适当更新的问题采取了补救措施。 功能已经恢复,我们正在监测所有环境以确认。 一旦监测证实完全稳定,我们将公布最后最新情况.

3. 2026年7月9日 UTC 12:12resolved

   这个问题已经解决。 我们对此造成的不便表示歉意。 请联系我们@stabbase.com 以防你还有问题。 我们很乐意帮忙!

4. 2026年7月9日 UTC 14:12resolved

   **摘要** 2026年7月8日,在7:06 AM至2:05 PM\(CEST\)之间,欧洲系统的客户在某些菜单项目,例如新闻页和文件夹上遇到不正确的未读指标. 我们的团队成功地确定了原因,恢复了全面服务功能。 ** 最新更新导致某些菜单项目(如新闻页和文件夹)出现未读指标,以显示某些用户的不正确信息。 一些菜单项继续显示不再可见内容的未读数,而另一些则完全停止显示一个指标. 我们的小组查明并解决了这个问题,恢复了受影响菜单项的未读准确指标。 作为一项预防措施,还对美洲和亚洲/太平洋系统进行了监测,没有发现对这些区域的客户产生影响。 ** 2026年7月8日Between 7:06 AM和2:05 PM\(CEST\),欧洲系统的客户可能已经在某些菜单项目上看到未读出的指标,如新闻页和文件夹,没有反映当前内容,在某些情况下显示无法清除或根本没有指标的计数. 在这次事件中没有丢失任何数据。 ** 未来的改进** 我们将对菜单未读指标的显示进行额外检查,并增强我们今后更快地发现和解决类似问题的能力。 感谢大家在我们努力改进服务和防止今后发生意外时的耐心和理解。 如果您有任何问题或关切,请毫不犹豫地联系我们的客户支助小组,地址是:[[email protected]] (mailto:[email protected]).

自动翻译自官方事件更新。

1. 2026年7月8日 UTC 10:18investigating

   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. 2026年7月8日 UTC 12:13monitoring

   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. 2026年7月9日 UTC 11:43resolved

   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. 2026年7月9日 UTC 13:59postmortem

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

1. 2026年7月6日 UTC 13:57investigating

   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. 2026年7月6日 UTC 15:13monitoring

   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. 2026年7月7日 UTC 12:52resolved

   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. 2026年7月8日 UTC 13:47postmortem

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

1. 2026年6月25日 UTC 17:18investigating

   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. 2026年6月25日 UTC 17:23investigating

   We are continuing to investigate this issue.

3. 2026年6月25日 UTC 18:02monitoring

   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. 2026年6月25日 UTC 19:02resolved

   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. 2026年7月13日 UTC 15:08postmortem

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

1. 2026年6月18日 UTC 20:03investigating

   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. 2026年6月18日 UTC 21:02identified

   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. 2026年6月18日 UTC 22:25resolved

   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. 2026年6月24日 UTC 15:04postmortem

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

1. 2026年6月18日 UTC 17:06investigating

   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. 2026年6月18日 UTC 17:07investigating

   We are continuing to investigate this issue.

3. 2026年6月18日 UTC 17:22monitoring

   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. 2026年6月18日 UTC 19:18resolved

   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. 2026年6月23日 UTC 13:25postmortem

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

1. 2026年6月18日 UTC 12:31resolved

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

1. 2026年6月11日 UTC 13:48investigating

   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. 2026年6月11日 UTC 14:05identified

   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. 2026年6月11日 UTC 14:11monitoring

   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. 2026年6月11日 UTC 14:27resolved

   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. 2026年6月16日 UTC 15:22postmortem

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

1. 2026年6月3日 UTC 13:49investigating

   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. 2026年6月3日 UTC 14:52resolved

   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. 2026年6月8日 UTC 14:19postmortem

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

1. 2026年6月2日 UTC 14:14investigating

   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. 2026年6月2日 UTC 15:34monitoring

   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. 2026年6月3日 UTC 13:07resolved

   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. 2026年6月5日 UTC 08:50postmortem

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