L
Outage recap · Legora

Legora outage — November 10, 2026

On November 10, 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.

Increase in latencies in the EU Region

minor
Started
Nov 10, 6:12 AM EST
Resolved
Nov 10, 7:01 AM EST
Duration
49 min

Legora's updates (2)

  1. investigating · Nov 10, 6:12 AM EST

    We are investigating increased latencies in the EU Region.

  2. resolved · Nov 10, 7:01 AM EST

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

What our checks recorded

We checked Legora 10 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 392 ms, against 413 ms over the 24 hours before. Legora posted the incident at Nov 10, 6:12 AM EST.

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

Elevated error rate in Agent

major
Started
Nov 10, 1:19 PM EST
Resolved
Nov 10, 1:39 PM EST
Duration
19 min

Legora's updates (4)

  1. investigating · Nov 10, 1:19 PM EST

    We are investigating an increased error rate in the Agent.

  2. investigating · Nov 10, 1:25 PM EST

    We are investigating an increased error rate for the Agent in EU. The team is working on a fix.

  3. investigating · Nov 10, 1:38 PM EST

    The elevated error rate has been fixed, and the Agent is fully operational again.

  4. resolved · Nov 10, 1:39 PM EST

    The elevated error rate has been fixed, and the Agent is fully operational again.

What our checks recorded

We checked Legora 4 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 331 ms, against 402 ms over the 24 hours before. Legora posted the incident at Nov 10, 1:19 PM EST.

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.