Livestorm Status

This incident has been resolved. Event registration is fully operational, and all attendees can register and receive their access link normally. Already-registered attendees were unaffected and no data was lost. We apologize for the disruption and appreciate your patience.

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.

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

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.

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.

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.

The issue has now been resolved following the rollback of the recent infrastructure update. Normal behavior has been restored, and no further impact has been observed. We apologize for any inconvenience this may have caused and appreciate your patience. We will continue monitoring to ensure ongoing stability and prevent recurrence.

This incident has been resolved.

The issue affecting the Events list for a subset of users has been resolved and the service is now operating normally. Our team will continue monitoring the situation to ensure everything remains stable.

The incident has been resolved. The backend change introducing the Ruby/OpenSSL upgrade has been rolled back, and normal functionality has been restored. Monitoring confirms that the system is stable and event duplication is working as expected. We apologize for any inconvenience this may have caused.

The scheduled maintenance has been completed.

The maintenance operation has successfully been completed and we can confirm that users should face no further impact on the platform.

The scheduled maintenance has been completed.

The maintenance operation has now been completed successfully and our teams have confirmed that the platform should now be working as expected. We thank you for your patience and apologise for any inconveniences this might have caused.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The maintenance operation has now been completed and our components continue to function as expected. No user-facing impact has been noticed during the course of the maintenance and users were able to access the platform without any issues. 
Thank you for your patience.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.