Is Livestorm down?

We have identified an issue that prevented some attendees from completing registration on Livestorm event registration pages. During the affected period, clicking the "Receive access link" button did not complete the sign-up. Already-registered attendees and their access links were not affected, and no data was lost. We have identified the cause and applied a fix. Registration is being restored, and we are monitoring to confirm full recovery. We'll post an update shortly. We apologize for the inconvenience.

A fix has been deployed and event registration is now working normally. Attendees can complete registration and receive their access link as expected. We are monitoring closely to confirm everything remains stable. Thank you for your patience.

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.

We are currently investigating an issue causing some users to encounter a 503 Service Temporarily Unavailable error when accessing the platform. Our team is actively working to identify the root cause and restore normal service as quickly as possible. We will provide further updates as soon as more information becomes available.

A change introduced during a Kubernetes cluster upgrade disrupted internal connections within our infrastructure, resulting in service unavailability. We are currently evaluating a rollback to restore connectivity and resume normal service as quickly as possible. We will provide another update as soon as remediation is underway.

The remediation has been applied and service availability has been restored. We are monitoring the platform closely to ensure that internal connectivity remains stable and that no further disruptions occur following the Kubernetes cluster upgrade issue.

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.

We have identified an issue causing login attempts via Google SSO and Microsoft SSO to fail silently. Our team is actively investigating the root cause and working to mitigate the issue as quickly as possible.

We have identified the cause of the issue: recent changes made to strengthen reCAPTCHA security introduced an unintended side effect that disrupted SSO login. We are rolling back these changes and continuing to monitor the situation closely.

The rollback has been completed, and SSO login via Google and Microsoft is now functioning as expected. We are continuing to monitor the situation closely to ensure the issue is fully resolved.

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

Our team has identified an ongoing issue where the platform is experiencing higher-than-usual loading times. At the moment, the Events list page may fail to load, and event creation may intermittently fail. Some users may also experience slow or unresponsive pages. We are actively investigating the root cause and rolling out fixes. We will share another update as soon as more information becomes available.

Our team was successfully able to mitigate the issue and the platform is now accessible as required. We're continuing to monitor the issue to ensure that users have no further impact in regards to this. We apologize for any inconvenience caused to this end.

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.

We have identified an issue with the event creation and registration. When attempting to create or register to an event, the operation does not complete successfully and the user sees an "Internal Server Error" We are currently investigating the issue and we will update you soon.

We have identified the root cause of this incident. An internal infrastructure component is experiencing saturation, causing event creation and registration operations to fail with an "Internal Server Error." We are actively working on mitigation and will provide updates as the situation progresses.

Event creation and registration should now be working as expected. We are monitoring the situation following the actions taken by our engineering team. Please let us know if you continue to experience any issues.

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. We sincerely apologize for the inconvenience and are taking steps to prevent this from happening again.

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. We sincerely apologize for the inconvenience and are taking steps to prevent this from happening again.