Critical incident

Livestorm: Elevated Errors Affecting Platform Access

Current status of Livestorm: Operational — live Livestorm status

Timeline

1. May 27, 2026, 15:08 UTC
   investigating
   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.
2. May 27, 2026, 15:22 UTC
   identified
   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.
3. May 27, 2026, 15:24 UTC
   monitoring
   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.
4. May 27, 2026, 15:33 UTC
   resolved
   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.

Updates as published by Livestorm (original).