Harvey

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-14 05:44 UTC

   We are currently investigating reports of an issue affecting the AU region. Our team is working to identify the root cause, and we will provide updates as soon as we have more information.

2. monitoring 2026-08-14 05:56 UTC

   The issue affecting issue affecting the AU region access has been resolved, and we are now monitoring the situation to ensure stability. We will provide further updates if necessary.

3. resolved 2026-08-14 06:04 UTC

   The issue affecting he AU region access has been resolved, and we are now monitoring the situation to ensure stability. We will provide further updates if necessary.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-08 08:25 UTC

   We are currently investigating reports of an issue affecting login and verification across all Harvey instances. Our team is working to identify the root cause and will provide updates as soon as we have more information.

2. resolved 2026-06-08 08:37 UTC

   The issue affecting login and verification across all Harvey instances has been resolved.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-03 01:56 UTC

   We are currently investigating an issue affecting file uploads and semantic search in the AU region. Uploading new documents and search queries relying on embeddings are impacted. Our team is actively working to restore full service and will provide updates as soon as possible.

2. identified 2026-06-03 03:44 UTC

   The issue affecting file uploads and semantic search in the AU region has been identified. Our team is actively working on a solution to resolve the issue. We will continue to update you on progress.

3. resolved 2026-06-03 06:11 UTC

   The issue affecting file uploads and semantic search in the AU region has been fully resolved. All systems are now operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-19 22:45 UTC

   We are doing a quick data migration process at midnight which will cause less than five minutes of downtime on the platform. We appreciate your patience.

2. resolved 2026-05-19 23:24 UTC

   The data migration process is complete. All systems are now operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-21 17:57 UTC

   We are currently investigating reports of intermittent performance degradation. Our team is working to identify the root cause, and we will provide updates as soon as we have more information.

2. resolved 2026-04-21 18:01 UTC

   The issue causing degraded performance has been fully resolved. All systems are now operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-16 23:19 UTC

   We are currently investigating reports of an issue affecting vault & review tables. Our team is working to identify the root cause, and we will provide updates as soon as we have more information.

2. investigating 2026-04-16 23:42 UTC

   We are currently investigating reports of an issue affecting vault & review tables. Our team is working to identify the root cause, and we will provide updates as soon as we have more information.

3. monitoring 2026-04-16 23:49 UTC

   We have implemented mitigations for the issue affecting Vault review tables and are now monitoring the situation to ensure stability.

4. monitoring 2026-04-17 00:07 UTC

   We have implemented mitigations for the issue affecting Vault review tables. At this time, the impact is limited to customers in the Canada region who may experience delays or issues with review tables generating.

5. resolved 2026-04-17 00:42 UTC

   The issue affecting Vault review tables has been fully resolved. All systems are now operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-14 16:19 UTC

   We are currently investigating reports of latency issues affecting document processing. Our team is working to identify the root cause, and we will provide updates as soon as we have more information.

2. resolved 2026-04-14 17:46 UTC

   The issue affecting document processing latency has been fully resolved. All systems are now operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-02 17:57 UTC

   Some users may be experiencing degraded performance within Harvey. Our team is working to identify the root cause, and we will provide updates as soon as we have more information.

2. resolved 2026-04-02 18:46 UTC

   The issue preventing some US users from accessing has been fully resolved. All systems are now operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-23 15:34 UTC

   We are currently investigating reports of an slowness affecting Vault and Assistant in our EU instance. Our team is working to identify the root cause, and we will provide updates as soon as we have more information.

2. investigating 2026-03-23 15:52 UTC

   We are currently investigating reports of slowness affecting a small number of files when using Vault or Assistant in our EU Instance. Our team is working to identify the root cause, and we will provide updates as soon as we have more information.

3. resolved 2026-03-23 16:21 UTC

   The issue causing slowness in the EU instance has been fully resolved. All systems are now operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-16 14:54 UTC

   We are currently investigating reports of an issue affecting the loading speed in the US Instance. Our team is working to identify the root cause, and we will provide updates as soon as we have more information.

2. identified 2026-03-16 16:10 UTC

   The issue affecting US instance load slowness has been identified. Our team is actively working on a solution to resolve the issue. We will continue to update you on progress.

3. monitoring 2026-03-16 17:15 UTC

   The issue affecting US Instance slowness has been resolved, and we are now monitoring the situation to ensure stability. We will provide further updates if necessary.

4. resolved 2026-03-16 19:21 UTC

   The issue affecting US processing times has been fully resolved. All systems are now operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-22 20:26 UTC

   We are currently experiencing an issue preventing passcodes from being sent to users with passcode authentication enabled. Our team is actively working on a resolution.

2. monitoring 2026-01-22 20:50 UTC

   We were able to resolve the issue preventing passcodes from being sent and are closely monitoring to ensure stability.

3. resolved 2026-01-22 22:22 UTC

   The issue preventing passcodes from being sent has been fully resolved.

4. monitoring 2026-01-23 03:34 UTC

   The issue affecting Outlook service, and we are now monitoring the situation to ensure stability. We will provide further updates if necessary.

5. monitoring 2026-01-23 03:39 UTC

   The email delivery issue affecting Outlook and Exchange users is ongoing due to a Microsoft infrastructure issue, and we are monitoring the situation to ensure stability. We will provide further updates if necessary.

6. resolved 2026-01-23 05:49 UTC

   The email delivery issue affecting Outlook and Exchange users, caused by a Microsoft infrastructure issue, has been fully resolved. All systems are now operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-20 22:47 UTC

   We’re investigating reports of intermittent Playbook run issues across the web app and Harvey for Word. As well as document editing issues in Harvey for Word.

2. identified 2026-01-21 00:16 UTC

   The issue affecting Playbook functionality and Harvey for Microsoft Word.has been identified. Our team is actively working on a solution to resolve the issue. We will continue to update you on progress.

3. resolved 2026-01-21 03:17 UTC

   The issue affecting Playbook functionality and Microsoft Word for Harvey has been fully resolved. All systems are now operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-05 15:29 UTC

   We are currently investigating reports of an issue affecting document processing in Vault. Our team is working to identify the root cause, and we will provide updates as soon as we have more information.

2. identified 2025-11-05 15:46 UTC

   The issue affecting Vault uploads has been identified. Our team is actively working on a solution to resolve the issue. We will continue to update you on progress.

3. monitoring 2025-11-05 17:24 UTC

   The issue affecting Vault uploads has been resolved, and we are now monitoring the situation to ensure stability. We will provide further updates if necessary.

4. monitoring 2025-11-05 17:25 UTC

   The issue affecting [system/product] has been resolved, and we are now monitoring the situation to ensure stability. We will provide further updates if necessary.

5. monitoring 2025-11-05 17:28 UTC

   The issue affecting Vault uploads has been resolved, and we are now monitoring the situation to ensure stability. We will provide further updates if necessary.

6. resolved 2025-11-05 18:03 UTC

   The issue affecting Vault uploads has been fully resolved. All systems are now operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-11-04 18:13 UTC

   We are currently investigating reports of an issue affecting document processing in Vault. Our team has identified the issue and we are working to resolve. We will provide updates as soon as we have more information.

2. monitoring 2025-11-04 18:47 UTC

   The issue affecting processing in Vault has been resolved, and we are now monitoring the situation to ensure stability. We will provide further updates if necessary.

3. resolved 2025-11-04 19:05 UTC

   The issue affecting processing in Vault has been fully resolved. All systems are now operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-29 18:26 UTC

   We are currently investigating reports of an issue affecting document viewing. Our team is working to identify the root cause, and we will provide updates as soon as we have more information.

2. monitoring 2025-10-29 18:56 UTC

   The issue affecting doc viewing has been resolved, and we are now monitoring the situation to ensure stability. We will provide further updates if necessary.

3. monitoring 2025-10-29 18:58 UTC

   The issue affecting document viewing has been resolved, and we are now monitoring the situation to ensure stability. We will provide further updates if necessary.

4. resolved 2025-10-29 19:27 UTC

   The issue affecting document viewing has been fully resolved. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Azure Front Door – Connectivity issues across multiple regions.

1. identified 2025-10-29 17:11 UTC

   We are currently investigating reports of an issue affecting app usage of all OfficeJS applications (Word Add-in, Outlook, Web). Microsoft is addressing the issue on their end and we will provide updates as soon as we have more information.

2. monitoring 2025-10-29 22:28 UTC

   The issue affecting Microsoft-Add Ins has been resolved per Microsoft Azure recovery, and we are now monitoring the situation to ensure stability. We will provide further updates if necessary.

3. resolved 2025-10-30 00:37 UTC

   The issue affecting Microsoft Add-ins has been fully resolved. All systems are now operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Azure Front Door – Connectivity issues across multiple regions.

1. investigating 2025-10-29 16:33 UTC

   We are currently investigating reports of an issue affecting logins (receiving passwordless code) due to an outage with Azure. Our team is working to identify the root cause, and we will provide updates as soon as we have more information.

2. resolved 2025-10-29 18:08 UTC

   The issue affecting users not receiving passwordless codes for login has been fully resolved. All systems are now operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-09 18:49 UTC

   We're currently experiencing service disruptions due to connectivity issues from several internet providers to Microsoft. Our team is monitoring the situation closely and service will be restored as connectivity is reestablished. We apologize for any inconvenience.

2. resolved 2025-10-09 19:01 UTC

   The issue has been fully resolved, all systems are now operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-27 14:48 UTC

   We are currently investigating reports of an issue affecting Vault and Assistant in our US instance. Our team is working to identify the root cause, and we will provide updates as soon as we have more information.

2. monitoring 2025-05-27 15:26 UTC

   The issue affecting Vault and Assistant has been resolved, and we are now monitoring the situation to ensure stability. We will provide further updates if necessary.

3. resolved 2025-05-27 15:35 UTC

   The issue affecting Vault and Assistant has been fully resolved. All systems are now operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Harvey's status page.