Vellum

Affected: APIs, Vellum Assistant Platform, Web Application, Documents Endpoint, Predict Endpoint

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-09-01 15:37 UTC

   We are currently monitoring a cloud provider outage causing intermittent networking issues

2. investigating 2026-09-01 15:51 UTC

   We are continuing to investigate this issue.

3. investigating 2026-09-01 16:01 UTC

   We are continuing to investigate this issue.

4. resolved 2026-09-01 19:26 UTC

   This incident has been resolved.

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

Affected: Predict Endpoint

Failure mode: A provider or third-party service this vendor depends on failed. 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-02-03 00:17 UTC

   We are currently investigating this issue.

2. resolved 2026-02-03 00:29 UTC

   This incident has been resolved.

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

Affected: Predict Endpoint

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-27 20:28 UTC

   We are currently investigating this issue.

2. monitoring 2026-01-27 20:40 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-01-27 21:12 UTC

   This incident has been resolved.

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

Affected: Predict Endpoint

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-27 18:59 UTC

   We are currently investigating this issue.

2. resolved 2026-01-27 19:17 UTC

   This incident has been resolved.

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

Affected: Web Application

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-01-19 11:40 UTC

   Users are unable to log in to the Vellum webapp

2. monitoring 2026-01-19 11:53 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-01-19 12:08 UTC

   This incident has been resolved.

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

Affected: Predict Endpoint

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. 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-09 19:25 UTC

   We are currently investigating increased latency on workflow executions

2. resolved 2026-01-09 21:38 UTC

   This incident has been resolved.

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

Affected: Web Application

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-08 22:09 UTC

   We are currently investigating the issue

2. monitoring 2026-01-08 22:10 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-01-09 00:53 UTC

   This incident has been resolved.

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

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-01-08 20:09 UTC

   The Vellum webapp experienced an outage for 6 minutes as a result of an infrastructure issue

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

Affected: APIs, Web Application, Documents Endpoint, Predict Endpoint

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-12-18 21:15 UTC

   We are currently investigating this issue.

2. investigating 2025-12-18 21:31 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-12-18 21:31 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-12-18 21:32 UTC

   This incident has been resolved.

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

Affected: APIs

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-12-08 19:15 UTC

   We are currently investigating this issue.

2. investigating 2025-12-08 19:34 UTC

   We are continuing to investigate this issue.

3. resolved 2025-12-08 19:57 UTC

   This incident has been resolved.

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

Affected: Web Application

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-11-28 19:56 UTC

   We are currently investigating why app.vellum.ai is hitting a Server Error and is unable to load. We expect all APIs to be functioning as usual.

2. monitoring 2025-11-28 19:58 UTC

   The Vellum web app is back up and we're monitoring the situation now.

3. resolved 2025-11-28 20:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vellum'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. resolved 2025-11-26 22:00 UTC

   The Vellum Frontend failed to load for 4 minutes from 5:11pm EST to 5:15pm EST. No backend services or APIs were affected

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

Affected: APIs, Web Application, Documents Endpoint, Predict Endpoint

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-11-21 13:45 UTC

   We are currently investigating this issue.

2. investigating 2025-11-21 14:00 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-11-21 14:03 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-11-21 14:15 UTC

   This incident has been resolved.

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

Affected: APIs, Web Application, Documents Endpoint, Predict Endpoint

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: Cloudflare.

1. identified 2025-11-18 12:00 UTC

   Due to global Cloudflare outage. All other features are operational.

2. identified 2025-11-18 14:43 UTC

   We are continuing to work on a fix for this issue.

3. identified 2025-11-18 14:52 UTC

   Degraded login flow due to Cloudflare outage.

4. identified 2025-11-18 16:01 UTC

   Outage resolved

5. identified 2025-11-18 16:05 UTC

   Cloudfare downstream issues were detected on Documents Endpoint and Login Authentication

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

   This incident has been resolved.

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

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-11-12 23:30 UTC

   For a brief period, some requests to a subset of Claude models failed due to the addition of a new feature which has been reverted

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

Affected: APIs, Web Application, Documents Endpoint, Predict Endpoint

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-11-05 20:43 UTC

   We are investigating this issue.

2. investigating 2025-11-05 20:49 UTC

   We are continuing to investigate this issue.

3. investigating 2025-11-05 20:50 UTC

   We are continuing to investigate this issue.

4. identified 2025-11-05 20:50 UTC

   We have identified the issue and are working on a fix.

5. monitoring 2025-11-05 21:05 UTC

   A fix has been implemented and we are monitoring the results.

6. monitoring 2025-11-05 21:12 UTC

   We are continuing to monitor for any further issues.

7. resolved 2025-11-05 21:27 UTC

   This incident has been resolved.

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

Affected: APIs

Failure mode: A code release introduced the failure. 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-10-24 13:21 UTC

   We are investigating an issue with saving both prompts and workflows

2. investigating 2025-10-24 15:44 UTC

   The issue was identified and a fix was deployed

3. resolved 2025-10-24 15:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vellum'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. resolved 2025-10-22 17:00 UTC

   Users were unable to access app.vellum.ai for a period of approximately 3 minutes starting at 17:15 UTC. The issue was isolated to the webapp, APIs and deployment traffic were unaffected.

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

Affected: Predict Endpoint

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-07-31 06:45 UTC

   We are currently investigating the issues

2. monitoring 2025-07-31 17:03 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-07-31 17:13 UTC

   This incident has been resolved.

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

Affected: APIs, Predict Endpoint

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-07-24 19:25 UTC

   We are currently investigating an issue with workflow execution errors

2. identified 2025-07-24 19:38 UTC

   We have identified the root cause of this issue and are implementing a fix

3. monitoring 2025-07-24 20:29 UTC

   We have implemented the fix and are monitoring workflow executions

4. resolved 2025-07-24 21:31 UTC

   We have confirmed this incident is resolved

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

Affected: APIs, Predict Endpoint

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-07-24 18:29 UTC

   We are investigating an issue with workflow sandbox executions. As of now this is not effecting deployments

2. monitoring 2025-07-24 18:48 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-07-24 20:29 UTC

   This incident has been resolved.

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

Affected: Predict Endpoint

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-07-22 19:40 UTC

   We are currently investigating this issue.

2. monitoring 2025-07-22 20:03 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-07-22 20:31 UTC

   This incident has been resolved.

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

Affected: APIs, Predict Endpoint

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-07-10 19:40 UTC

   We are currently investigating this issue.

2. monitoring 2025-07-10 19:44 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-07-10 19:47 UTC

   This incident has been resolved.

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

Affected: Predict Endpoint

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-06-24 20:10 UTC

   We are currently investigating this issue.

2. monitoring 2025-06-24 20:16 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-06-24 20:21 UTC

   This incident has been resolved.

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

Affected: APIs, Documents Endpoint, Predict Endpoint

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: Google Cloud.

1. investigating 2025-06-12 18:48 UTC

   We are currently investigating this issue.

2. monitoring 2025-06-12 22:43 UTC

   GCP has started to recover its services. We expect most of our services to be back online but are monitoring stability

3. resolved 2025-06-13 01:35 UTC

   This incident has been resolved.

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

Affected: APIs, Documents Endpoint, Predict Endpoint

Failure mode: Orchestration, control plane, service discovery or load balancing failed. 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-06-11 15:29 UTC

   The issue has been identified and a fix is being implemented.

2. investigating 2025-06-11 15:51 UTC

   We are currently investigating this issue.

3. investigating 2025-06-11 16:20 UTC

   We are aware of reports of application failing to load as we implement infrastructure level changes

4. investigating 2025-06-11 17:02 UTC

   App should be back online, but with degraded load times as we migrate traffic over to the new infra

5. investigating 2025-06-11 17:04 UTC

   The new fix is rolled out, we are continuing to monitor the situation

6. monitoring 2025-06-11 17:18 UTC

   API requests to the predict endpoint is experiencing increased latency as we roll out the remaining fixes

7. monitoring 2025-06-11 17:53 UTC

   We are continuing to monitor for any further issues.

8. resolved 2025-06-11 17:54 UTC

   This incident has been resolved.

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

Affected: APIs, Documents Endpoint, Predict Endpoint

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-06-11 10:45 UTC

   We are currently investigating this issue.

2. identified 2025-06-11 10:58 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-06-11 11:15 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-06-11 11:24 UTC

   This incident has been resolved.

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

Affected: Predict Endpoint

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-06-10 20:44 UTC

   We are currently investigating this issue.

2. monitoring 2025-06-10 21:24 UTC

   We've rolled out a fix to reduce latency to normal levels

3. resolved 2025-06-11 00:31 UTC

   This incident has been resolved.

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

Affected: Predict Endpoint

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-06-10 14:59 UTC

   We are currently investigating this issue.

2. investigating 2025-06-10 16:20 UTC

   We're continuing to investigate and actively work on resolving this incident.

3. monitoring 2025-06-10 16:41 UTC

   A fix has been implemented and we're closely monitoring.

4. monitoring 2025-06-10 17:20 UTC

   We have stabilized all requests made to https://predict.vellum.ai

5. resolved 2025-06-10 17:23 UTC

   This incident has been resolved.

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

Affected: APIs, Predict Endpoint

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. identified 2025-06-06 20:13 UTC

   We're seeing widespread issues with Workflows failing to run with an "Invalid API Key" error. The problem has identified and a fix is being worked on now.

2. resolved 2025-06-06 20:24 UTC

   This incident has been resolved.

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

Affected: Predict Endpoint

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. monitoring 2025-05-22 23:07 UTC

   Users are experiencing 403 errors on calls to predict.vellum.ai. [7:07pm ET] We expect this issue to be resolved and are monitoring

2. resolved 2025-05-22 23:13 UTC

   This incident has been resolved.

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

Affected: APIs

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 2025-05-22 22:13 UTC

   We've gotten reports of an elevated rate of 403 responses in Vellum APIs. We're investigating now.

2. monitoring 2025-05-22 22:28 UTC

   A fix has been identified, rolled out, and is being closely monitored.

3. resolved 2025-05-22 22:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vellum'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. resolved 2025-05-13 00:30 UTC

   The incident has been resolved

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

Affected: Predict Endpoint

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-04-27 06:38 UTC

   We are currently investigating this issue.

2. resolved 2025-04-27 07:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vellum'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. resolved 2025-04-23 13:30 UTC

   From 9:39-9:55AM ET API calls to Vellum using API key authentication raised 403 errors.

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

Affected: APIs, Documents Endpoint, Predict Endpoint

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-04-16 18:17 UTC

   We are actively investigating reports of the Vellum web application not loading and inference endpoints hanging. We will be posting updates as we have them available here.

2. monitoring 2025-04-16 18:33 UTC

   We believe this to be resolved, but are closely monitoring the situation to ensure services remain healthy.

3. resolved 2025-04-16 21:25 UTC

   This incident has been resolved.

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

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-04-04 16:00 UTC

   Users experienced elevated error rates on the predict endpoint for 5 minutes (16:17-16:22 UTC) due to a database connectivity issue.

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

Affected: APIs, Documents Endpoint, Predict Endpoint

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. 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-04-02 18:18 UTC

   We're seeing an increase in error rates for inference endpoints, resulting in unexpected 500 responses. We're actively investigating this issue and will provide updates here.

2. resolved 2025-04-02 18:24 UTC

   This issue was resolved a few minutes later. There was an issue in our queueing service.

Excerpts are shortened. Read the full incident on Vellum'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. resolved 2025-04-01 19:40 UTC

   Elevated latencies and error rates on the predict and documents endpoints from 19:05-19:17 UTC

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

Affected: APIs

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 2025-03-25 18:06 UTC

   We are currently investigating this issue.

2. investigating 2025-03-25 18:50 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-03-25 18:50 UTC

   Users are able to log in again

4. resolved 2025-03-25 18:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vellum'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. resolved 2025-03-05 15:00 UTC

   From 10:09am EST - 10:23am EST, users were unable to log into the main Vellum platform. Requests to the API endpoints were unaffected.

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

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-02-16 19:00 UTC

   There were about 15 minutes beginning at 1:30pm EST in which we failed to make Prompt requests to model providers. The root cause was resolved and executions are behaving as they should once more.

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

Affected: APIs, Predict Endpoint

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-01-06 21:33 UTC

   Event processing is currently delayed, resulting in recent monitoring data not appearing in monitoring UIs. We have identified the root cause and are rolling out a fix. Event processing should catch up and we'll provide updates here as they do.

2. resolved 2025-01-06 21:36 UTC

   The fix is live and all backed up events have been successfully processed.

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

Affected: APIs, Documents Endpoint, Predict Endpoint

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. resolved 2024-12-23 17:35 UTC

   There were about 3 minutes of downtime of Vellum services beginning around 12:24pm EST December 23rd, 2024.

Excerpts are shortened. Read the full incident on Vellum'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. resolved 2024-11-26 16:00 UTC

   For about 15 minutes beginning 11:16am EST, API called to Workflow Deployments (i.e. `execute-workflow` and `execute-workflow-stream`) began incorrectly responding with 400 status codes. This issue has since been resolved and preventative measures are being put into place for...

Excerpts are shortened. Read the full incident on Vellum'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. resolved 2024-11-16 16:30 UTC

   Document search and indexing were unavailable from 10:36AM-11:42AM CST

Excerpts are shortened. Read the full incident on Vellum'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. resolved 2024-11-15 02:52 UTC

   From 2:20-2:38pm PST Vellum had a global outage affecting the web application and all API endpoints.

Excerpts are shortened. Read the full incident on Vellum'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. resolved 2024-11-07 23:00 UTC

   The Vellum web application was down for about 2 minutes from 6:18pm - 6:20pm EST.

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

Affected: Predict Endpoint

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).

Names an upstream provider: OpenAI.

1. identified 2024-08-28 22:35 UTC

   Vellums inference endpoints are experiencing an elevated rate of connection errors when making requests to OpenAI. A fix is going live now.

2. identified 2024-08-28 22:35 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2024-08-28 22:40 UTC

   This was resolved at 6:31pm EST.

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

Affected: Documents Endpoint

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 2024-07-19 21:43 UTC

   We are experiencing degraded stability for Document search and upload and for Document Index creation and deletion. We are actively working on a fix and should see lower error rates with time.

2. resolved 2024-07-21 12:15 UTC

   This incident has been resolved.

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