Elevated Errors Affecting Platform Access

Update timeline

1. investigating May 27, 2026, 03:08 PM UTC

   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. identified May 27, 2026, 03:22 PM UTC

   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. monitoring May 27, 2026, 03:24 PM UTC

   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. resolved May 27, 2026, 03:33 PM UTC

   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.