Staffbase incident

[App/Intranet] [DE System] – Post publishing disruption between November 1st and 2nd.

Minor Resolved View vendor source →

Staffbase experienced a minor incident on November 3, 2025, lasting —. The incident has been resolved; the full update timeline is below.

Started
Nov 03, 2025, 02:49 PM UTC
Resolved
Nov 01, 2025, 05:00 PM UTC
Duration
Detected by Pingoru
Nov 03, 2025, 02:49 PM UTC

Update timeline

  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.