L
Outage recap · Legora

Legora outage — September 4, 2026

On September 4, 2026, Legora had a reported incident on Legora's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Increased Latency and Errors in AP Region

minor
Started
Sep 4, 2:47 AM EDT
Resolved
Sep 4, 5:19 AM EDT
Duration
2h 32m

Legora's updates (5)

  1. investigating · Sep 4, 2:47 AM EDT

    We are investigating an increase in the latency while logging in the AP Region.

  2. identified · Sep 4, 2:52 AM EDT

    We identified the cause of the increased latency in the AP Region and are actively mitigating it.

  3. identified · Sep 4, 3:32 AM EDT

    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.

  4. identified · Sep 4, 4:35 AM EDT

    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.

  5. resolved · Sep 4, 5:19 AM EDT

    The issue has been resolved and the system is operating normally.

What our checks recorded

We checked Legora 30 times from Legora's start time to its resolution, once every five minutes. Every one of them reached Legora's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 260 ms, against 181 ms over the 24 hours before. Legora posted the incident at Sep 4, 2:47 AM EDT.

Updates are Legora's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with Legora. This recap summarizes incidents published on Legora's official status page.