Staffbase Communications Control Outage History

Staffbase Communications Control partial outage View live status →

Staffbase Communications Control had 1 outage in the last 2 years totaling 6h 36m of downtime — averaging 0 incidents per month.

There was 1 Staffbase Communications Control outage since May 26, 2025 totaling 6h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.dirico.io

Critical May 26, 2025

Temporary Outage: Communications Control Page

Detected by Pingoru
May 26, 2025, 08:54 AM UTC
Resolved
May 26, 2025, 03:31 PM UTC
Duration
6h 36m
Affected: LoginPublishing
Timeline · 4 updates
  1. identified May 26, 2025, 08:54 AM UTC

    We are currently experiencing an issue with the Communications Control page, which is temporarily unavailable. Our team is actively working on resolving the problem, and we expect the login functionality to be restored very soon. We apologize for the inconvenience. If you have any questions regarding this matter, please contact our support team at [email protected].

  2. monitoring May 26, 2025, 10:04 AM UTC

    We have successfully published a fix to resolve the issue, and the login to the Communications Control page is now working again. We will continue to monitor the systems closely to ensure the issue is fully resolved and does not reoccur. Thank you for your patience. If you have any questions regarding this matter, please contact our support team at [email protected].

  3. monitoring May 26, 2025, 12:51 PM UTC

    We have identified that some issues with content publishing may have occurred following the downtime of Communications Control. Content remained in the "Planned" status and was not published as scheduled. The publishing functionality is now working as expected again. We recommend reviewing any content scheduled between this morning and now to ensure nothing was missed. We apologize for the inconvenience and thank you for your understanding. If you have any questions regarding this matter, please contact our support team at [email protected].

  4. resolved May 26, 2025, 03:31 PM UTC

    This incident has been resolved.

Read the full incident report →