L
Outage recap · Legora

Legora outage — September 15, 2026

On September 15, 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.

Outlook & Word add-in unavailable for some users

major
Started
Sep 15, 5:51 PM EDT
Resolved
Sep 16, 12:42 AM EDT
Duration
6h 51m

Legora's updates (4)

  1. identified · Sep 15, 5:51 PM EDT

    We’ve identified an issue affecting the availability of our Word and Outlook add-ins for some users

  2. identified · Sep 15, 8:29 PM EDT

    We identified the cause of the issue impacting availability of our Word and Outlook add-ins for some users and are actively working with Microsoft to have them listed again.

  3. monitoring · Sep 15, 9:23 PM EDT

    The add-ins are listed on Microsoft's marketplace again, and we are monitoring for any remaining availability issues.

  4. resolved · Sep 16, 12:42 AM EDT

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

What our checks recorded

We checked Legora 82 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 173 ms, against 192 ms over the 24 hours before. Legora posted the incident at Sep 15, 5:51 PM EDT.

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

Elevated agent error rate in the AU Region

major
Started
Sep 15, 9:58 PM EDT
Resolved
Sep 16, 1:31 AM EDT
Duration
3h 33m

Legora's updates (4)

  1. investigating · Sep 15, 9:58 PM EDT

    Customers using the AU instance may be unable to send messages or receive agent responses. We are investigating and working to restore service.

  2. identified · Sep 15, 11:28 PM EDT

    We identified the cause of the increased increased error rate with Agent responses in the AU Region and are actively working to resolve the issue.

  3. identified · Sep 16, 1:11 AM EDT

    We continue to work to resolve the issue. We have identified a path to resolution and are carrying out the steps needed to restore service.

  4. resolved · Sep 16, 1:31 AM EDT

    We mitigate the issue and the service is operating normally.

What our checks recorded

We checked Legora 43 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 163 ms, against 197 ms over the 24 hours before. Legora posted the incident at Sep 15, 9:58 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.