L
Outage recap · Legora

Legora outage — September 21, 2026

On September 21, 2026, Legora had 2 reported incidents 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 US region

minor
Started
Sep 21, 11:44 AM EDT
Resolved
Sep 21, 12:29 PM EDT
Duration
44 min

Legora's updates (3)

  1. investigating · Sep 21, 11:44 AM EDT

    We are investigating an increased error rate and latency in the US Region. Customers on dedicated storage are not affected.

  2. monitoring · Sep 21, 11:56 AM EDT

    We mitigated the increased increased error rate in the XX Region and are monitoring the system.

  3. resolved · Sep 21, 12:29 PM EDT

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

What our checks recorded

We checked Legora 9 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 265 ms, against 165 ms over the 24 hours before. Legora posted the incident at Sep 21, 11:44 AM EDT.

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

Unavailability for some tenants on AP

major
Started
Sep 21, 10:18 PM EDT
Resolved
Sep 21, 11:18 PM EDT
Duration
1h

Legora's updates (5)

  1. investigating · Sep 21, 10:18 PM EDT

    We are investigating an issue preventing some customers from logging in to the AP instance. Our engineering team is working to restore access.

  2. identified · Sep 21, 11:12 PM EDT

    We've identified the root cause and are working to mitigate it

  3. resolved · Sep 21, 11:18 PM EDT

    Access to the AP instance has been restored. We have resolved the issue and will continue to review the incident.

  4. investigating · Sep 21, 11:36 PM EDT

    We are continuing to investigate reports that some customers are unable to log in to the AP instance. Our engineering team is working to restore access.

  5. resolved · Sep 21, 11:38 PM EDT

    Access to the AP instance has been restored. We have resolved the issue and will continue to review the incident.

What our checks recorded

We checked Legora 12 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 124 ms, against 176 ms over the 24 hours before. Legora posted the incident at Sep 21, 10:18 PM 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.