Staffbase incident

[App/Intranet] [German System] - Long loading times

Major Resolved View vendor source →

Staffbase experienced a major incident on April 22, 2025 affecting Core API (Europe) [SLA], lasting 3h 48m. The incident has been resolved; the full update timeline is below.

Started
Apr 22, 2025, 07:07 AM UTC
Resolved
Apr 22, 2025, 10:55 AM UTC
Duration
3h 48m
Detected by Pingoru
Apr 22, 2025, 07:07 AM UTC

Affected components

Core API (Europe) [SLA]

Update timeline

  1. investigating Apr 22, 2025, 07:07 AM UTC

    Customers hosted on our German System may be experiencing longer loading times. 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 Apr 22, 2025, 08:59 AM UTC

    Our teams are seeing performance metrics being back to normal and customers should no longer experience long loading times. We will continue to monitor the situation and update you shortly.

  3. resolved Apr 22, 2025, 10:55 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!

  4. postmortem Apr 23, 2025, 02:15 PM UTC

    **Summary:** Now that our investigation of the incident is complete, we would like to share more details about the issue that occurred on April 22 between 08:45 CET and 10:50 CET. ‌ **What happened:** A change to our infrastructure was rolled out which caused an unforeseen delay in requests and slowed our backend down. This alarmed our teams who immediately worked on restoring the performance of our system. **‌** **Impact:** During the mentioned timeframe, users on our German system experienced long loading times or unresponsiveness when accessing the app or intranet. **‌** **Future Improvements:** We will explore options to introduce additional testing setups to prevent similar issues in the future. Please contact us at [[email protected]](mailto:[email protected]) if you have any further questions or feedback regarding this topic.