Livestorm Status Page

May 27, 2026 · resolved May 27

This incident has been resolved. Service availability has been fully restored, and monitoring confirms that the platform is operating normally. The disruption was caused by a change introduced during a Kubernetes cluster upgrade, which affected internal cluster connectivity. We will continue reviewing the incident to prevent similar occurrences in the future. We apologize for the inconvenience.

May 19, 2026 · resolved May 19

The issue affecting Google and Microsoft SSO login has been resolved following the rollback. We have confirmed that SSO authentication is functioning as expected.

May 18, 2026 · resolved May 18

Following our monitoring over the past few minutes, we can confirm that there is no longer any ongoing impact related to this issue. Users should now be able to access the platform and its features as expected. We sincerely apologize for any inconvenience caused and appreciate your patience while we worked to resolve this.

May 14, 2026 · resolved May 14

This incident has now been resolved. The root cause was identified as an internal component being overwhelmed by an unusually high volume of scheduled jobs originating from a single source. We have since removed the problematic jobs and scaled the infrastructure accordingly. All features, including event creation, registration, access to event rooms, and automated actions, are now fully operational. . Please note that during the time of the incident, some automated actions and emails may have failed or timed out due to the system overload. This could have resulted in certain emails not being sent and some automated actions not being triggered. Unfortunately, these actions cannot be retroactively reprocessed or retriggered. We sincerely apologize for the inconvenience and are taking steps to prevent this from happening again.

May 14, 2026 · resolved May 14

This incident has been resolved. The root cause was identified as an internal component being overwhelmed by an abnormally large number of scheduled jobs originating from a single source. We have removed the offending jobs and scaled our infrastructure accordingly. All features, including event creation, registration, and automated actions, are now fully operational. We apologize for the inconvenience and will be taking steps to prevent this from happening again. Please note that during the time of the incident, some automated actions and emails may have failed or timed out due to the system overload. This could have resulted in certain emails not being sent and some automated actions not being triggered. Unfortunately, these actions cannot be retroactively reprocessed or retriggered. We sincerely apologize for the inconvenience and are taking steps to prevent this from happening again.