Staffbase incident

[App/Intranet/E-Mail] [US System] – Service currently unavailable

Critical Resolved View vendor source →
Started
Feb 20, 2026, 12:31 PM UTC
Resolved
Feb 23, 2026, 10:32 AM UTC
Duration
2d 22h
Detected by Pingoru
Feb 20, 2026, 12:31 PM UTC

Affected components

Core API (Americas) [SLA]Web Application (Americas) [SLA]Staffbase Email API (Americas)Native App - iOSNative App - Android

Update timeline

  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.

Looking to track Staffbase downtime and outages?

Pingoru polls Staffbase's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Staffbase reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Staffbase alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Staffbase for free

5 free monitors · No credit card required