Legora incident

Increased Latency and Errors in AP Region

Minor Resolved View vendor source →

Legora experienced a minor incident on September 4, 2026 affecting AP instance, lasting 2h 32m. The incident has been resolved; the full update timeline is below.

Started
Sep 04, 2026, 06:47 AM UTC
Resolved
Sep 04, 2026, 09:19 AM UTC
Duration
2h 32m
Detected by Pingoru
Sep 04, 2026, 06:47 AM UTC

Affected components

AP instance

Update timeline

  1. investigating Sep 04, 2026, 06:47 AM UTC

    Status: Investigating We are investigating an increase in the latency while logging in the AP Region. Affected components AP instance (Degraded performance)

  2. identified Sep 04, 2026, 06:52 AM UTC

    Status: Identified We identified the cause of the increased latency in the AP Region and are actively mitigating it. Affected components AP instance (Degraded performance)

  3. identified Sep 04, 2026, 07:32 AM UTC

    Status: Identified We are continuing to investigate increased latency and errors affecting the AP instance. Our team is working with our cloud provider and exploring mitigation options. Some users may continue to experience slow or failed logins and slow page loads. Affected components AP instance (Degraded performance)

  4. identified Sep 04, 2026, 08:35 AM UTC

    Status: Identified We continue to investigate increased latency and errors affecting the AP instance. We are working with our cloud provider and testing mitigation options for connectivity to services in Australia East. Some users may continue to experience slow or failed logins and slow page loads. Affected components AP instance (Degraded performance)

  5. resolved Sep 04, 2026, 09:19 AM UTC

    Status: Resolved The issue has been resolved and the system is operating normally. Affected components AP instance (Operational)