Vectara

Affected: Admin, Index, Query, Chat, Document

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 2026-09-02 18:08 UTC

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

2. resolved 2026-09-02 18:42 UTC

   This incident has been resolved.

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

Affected: Console

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-15 17:54 UTC

   DNS for console.vectara.com is configured, we are currently in the process of doing a rollback.

2. resolved 2026-07-15 17:57 UTC

   This incident has been resolved.

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

Affected: Index

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

1. monitoring 2026-07-02 11:07 UTC

   We have a maintenance window going on which has affected the document indexing performance.

2. monitoring 2026-07-02 11:08 UTC

   We are continuing to monitor for any further issues.

3. monitoring 2026-07-02 11:09 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-07-02 12:29 UTC

   This incident has been resolved.

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

Affected: Admin, Chat

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-06-30 14:50 UTC

   We are noticing get agent events timing out, we are investigating the issue

2. investigating 2026-06-30 19:52 UTC

   We are continuing to investigate this issue.

3. resolved 2026-06-30 19:54 UTC

   This incident has been resolved.

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

Affected: Index

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

1. identified 2026-05-02 11:09 UTC

   An AWS Kafka upgrade is causing issues in writing documents; some requests are failing, and we are monitoring the situation.

2. resolved 2026-05-02 13:24 UTC

   This incident has been resolved.

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

Affected: Console, Query

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. monitoring 2026-02-26 20:52 UTC

   Some queries may be affected and take longer than usual

2. resolved 2026-02-27 00:01 UTC

   This incident has been resolved.

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

Affected: Query

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-12-01 11:05 UTC

   Newly Indexed Data is not currently query able we have identified the cause of the issue and are working to remediate it.

2. identified 2025-12-01 11:25 UTC

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

3. monitoring 2025-12-01 11:25 UTC

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

4. resolved 2025-12-01 12:14 UTC

   This incident has been resolved.

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

Affected: Console

Failure mode: Login, tokens, certificates or credentials 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. investigating 2025-11-18 13:06 UTC

   Some users are unable to login. We are investigating the cause of this issue.

2. investigating 2025-11-18 13:10 UTC

   Our authentication provider is experiencing impact from the Cloudflare outage.

3. investigating 2025-11-18 14:06 UTC

   The Cloudflare issue impacting our authentication provider has been resolved.

4. resolved 2025-11-18 14:07 UTC

   This incident has been resolved.

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

Affected: Query, Chat

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. monitoring 2025-09-14 10:38 UTC

   APIs involving OpenAI are having an elevated error rate.

2. monitoring 2025-09-14 19:18 UTC

   Error rates have dropped to normal levels for calls to OpenAI. We are continuing to monitor our API performance.

3. resolved 2025-09-14 22:42 UTC

   Resolved. All Systems Back to Normal.

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

Affected: Query

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-08-17 00:16 UTC

   We are currently investigating this issue.

2. monitoring 2025-08-17 02:14 UTC

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

3. resolved 2025-08-17 02:29 UTC

   This incident has been resolved.

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

Affected: Index, Query, Chat

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

1. identified 2025-07-10 17:17 UTC

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

2. resolved 2025-07-10 20:25 UTC

   OpenAI APIs are working fine now.

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

Affected: Admin, Index, Query, Chat, Document

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. identified 2025-07-02 12:41 UTC

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

2. monitoring 2025-07-02 13:21 UTC

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

3. resolved 2025-07-02 13:44 UTC

   This incident has been resolved.

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

Affected: Admin, Index, Query, Chat, Document

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-30 16:03 UTC

   The issue has been identified, we are doing a fix.

2. monitoring 2025-06-30 16:08 UTC

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

3. resolved 2025-06-30 16:11 UTC

   Connections to our database were broken; connectivity has been restored.

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

Affected: Index, Query, Chat

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

1. monitoring 2025-06-24 20:57 UTC

   We are monitoring the status. The issue is intermittent.

2. resolved 2025-06-24 22:03 UTC

   This incident has been resolved.

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

Affected: Index, Query

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-18 09:53 UTC

   Neural search queries are not working on the new corpora and any new document uploaded on the existing corpora. Queries on the existing corpora and uploaded document are working fine.

2. identified 2025-06-19 00:25 UTC

   Neural search indexing is still down. We are currently rebuilding those indexes. You can workaround this by using lexical search.

3. monitoring 2025-06-20 01:04 UTC

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

4. resolved 2025-06-20 02:04 UTC

   This incident has been resolved.

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

Affected: Console, Index

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-06-12 17:42 UTC

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

2. resolved 2025-06-12 19:16 UTC

   This incident has been resolved.

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

Affected: Admin, Console

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 05:24 UTC

   We are currently investigating this issue.

2. resolved 2025-06-11 06:55 UTC

   This incident has been resolved.

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

Affected: Index

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-06-06 23:21 UTC

   Document indexing is not working due to an issue in our system. We are investigating the issue to resolve it as soon as possible. System will work properly for already uploaded documents, only new documents will not be indexed.

2. resolved 2025-06-07 00:04 UTC

   This incident has been resolved.

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

Affected: Console, Index, Query, Chat, Document

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

   The usage of a number of our endpoints is resulting in degraded functionality seen as 5xx errors, we are investigating

2. monitoring 2025-06-06 14:34 UTC

   We are monitoring a fix, our services should be recovering now.

3. resolved 2025-06-06 16:01 UTC

   This incident has been resolved.

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

Affected: Index

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-06-05 21:01 UTC

   Document indexing is not working due to an issue in our system. We are investigating the issue to resolve it as soon as possible. System will work properly for already uploaded documents, only new documents will not be indexed.

2. resolved 2025-06-05 22:14 UTC

   This incident has been resolved.

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

Affected: Console, Document

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

1. monitoring 2025-05-31 05:53 UTC

   We are seeing a service degradation for features that use OpenAI models since we can't seem to reach OpenAI's API's intermittently. We are monitoring and working to resolve the issue.

2. resolved 2025-05-31 22:20 UTC

   This incident has been resolved.

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

Affected: Console, Query, Chat, Document

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

1. monitoring 2025-05-30 22:54 UTC

   We are seeing a service degradation for features that use OpenAI models since the OpenAI API is experiencing problems. We will continue to monitor the status of the OpenAI API services and update this incident once this issue has been resolved.

2. monitoring 2025-05-30 22:59 UTC

   We are continuing to monitor for any further issues.

3. resolved 2025-05-31 05:18 UTC

   This incident has been resolved.

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

Affected: Index, Query

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-05-16 02:30 UTC

   Some corpora have elevated error rate and/or high latency. During an upgrade process some corpora are reloading at slower than expected speeds; we are currently investigating. No data has been lost if an index has already been completed.

2. resolved 2025-05-17 16:47 UTC

   This incident has been resolved.

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

Affected: Query

Failure mode: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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

   We are currently upgrading our servers due to which the running queries are getting affected.

2. investigating 2025-05-15 12:29 UTC

   We are continuing to investigate this issue.

3. resolved 2025-05-15 12:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vectara'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 medium confidence (taxonomy v0.2).

1. resolved 2025-04-30 05:30 UTC

   One of the worker nodes in the production deployment entered a faulty state around 5:19 AM (UTC), resulting in parsing errors. As a consequence, approximately 25% of file uploads failed. The issue was resolved at 4:30 PM (UTC).

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

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. resolved 2025-04-30 02:30 UTC

   An outage occurred during the promotion of new services to production, lasting approximately 20 minutes. The issue has been resolved.

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

Affected: Query, Chat

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 low confidence (taxonomy v0.2).

1. monitoring 2025-04-19 04:01 UTC

   Queries for some customers are failing due to issues with one of our vector database. We've fixed the issue and are monitoring resolution for all customers. Only a few customers assigned to that particular shard are impacted.

2. resolved 2025-04-19 04:57 UTC

   All systems are now up and queries for all customers are operational.

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

Affected: Index, Query, Chat, Document

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-02 22:44 UTC

   We are currently investigating this issue.

2. monitoring 2025-04-02 23:48 UTC

   Most corpora should be indexing and querying again

3. resolved 2025-04-03 06:32 UTC

   This incident has been resolved.

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

Affected: Admin, Console, Index, Query, Chat, Document

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-03-28 17:34 UTC

   We are seeing many API requests fail, and are actively seeking a fix.

2. monitoring 2025-03-28 17:43 UTC

   We have identified the issue; a bad routing configuration got rolled out. The issue should be resolved, and we are monitoring the situation. We will be doing and publishing a post mortem.

3. resolved 2025-03-28 18:28 UTC

   Services should be back to normal now, we will conduct a postmortem.

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

Affected: Admin, Console, Index, Query, Chat, Document

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-03-28 16:30 UTC

   Vectara is expecting query timeout at a higher than expected rate, we are investigating now.

2. resolved 2025-03-28 19:41 UTC

   This incident has been resolved.

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

Affected: Index

Failure mode: Hardware, power, cooling or another physical failure. 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-03-07 12:49 UTC

   Indexing operations were impacted due to one of the components' storage being affected, and the issue has been resolved.

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

Affected: Console

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. monitoring 2025-02-07 16:43 UTC

   Due to an incorrectly sequenced migration, web console logins were impacted. A fix has now been deployed, and logins should be working as expected. We will continue to monitor to ensure the issue is fully resolved.

2. resolved 2025-02-07 18:44 UTC

   This incident has been resolved.

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

Affected: Admin

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-02-06 17:47 UTC

   We are currently investigating this issue.

2. resolved 2025-02-06 17:54 UTC

   This incident has been resolved.

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

Affected: Console

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-01-25 04:10 UTC

   Some users experienced errors between Jan 23, 2025 9:54 PM CST and Jan 24, 2025 6:21 PM CST, while attempting to upload documents from the console for indexing. The issue appears to affect a subset of users and might result in failed uploads. The issue has been already resolved.

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

Affected: Console, Document

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 2024-12-19 19:20 UTC

   For some customers, newly uploaded documents appear late in the console. No document is lost, they are being processed. The problem has been identified, and a fix is in progress.

2. resolved 2024-12-19 19:37 UTC

   This incident has been resolved.

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

Affected: Query

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

1. monitoring 2024-12-12 02:36 UTC

   Queries that depend on generation from OpenAI are experiencing elevated error rates. See https://status.openai.com/

2. resolved 2024-12-12 04:17 UTC

   This incident has been resolved.

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

Affected: Query

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 2024-12-11 15:36 UTC

   Some customer's queries are impacted. The problem has been identified, and a fix is in progress.

2. identified 2024-12-11 15:37 UTC

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

3. resolved 2024-12-11 15:54 UTC

   This incident has been resolved.

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

Affected: Query, Chat

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-12-05 20:43 UTC

   A few generation requests are failing due to an issue with prompts. We have identified the issue and are in the process of fixing it.

2. identified 2024-12-05 23:16 UTC

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

3. resolved 2024-12-05 23:17 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Vectara'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-28 18:30 UTC

   Some customers experienced service degradation issues.

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

Affected: Query, Chat

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

   Some of the LLM calls to Mockingbird are failing. We are investigating.

2. resolved 2024-10-24 21:07 UTC

   The issue has been resolved. A new version of the AMI from the cloud provider resulted in system call issues. We've fixed and verified now.

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

Affected: Console

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 high confidence (taxonomy v0.2).

1. investigating 2024-10-23 05:04 UTC

   This is a test only to see our integration with the website. There is no system impact. Please ignore.

2. resolved 2024-10-23 05:06 UTC

   Testing complete. All good.

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

Affected: Query

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 2024-09-09 16:07 UTC

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

2. resolved 2024-09-09 16:59 UTC

   The issue has been resolved.

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

Affected: Query, Chat

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2024-09-01 17:51 UTC

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

2. resolved 2024-09-01 18:56 UTC

   While upgrading infrastructure, wrong configuration that was misaligned between production and infrastructure caused an outage. We aligned the configuration, and will be conducting a post mortem review.

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

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2024-08-15 03:30 UTC

   Services had trouble connecting to other components due to a intermittent network errors. The network error is resolved.

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

Affected: Query

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-07-15 21:17 UTC

   Querying corpora for some customers is currently down. No impact to indexing and all documents have been retained. We're working on quickly resolving the issue.

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

   The outage has been resolved and we are implementing a fix for the bug which caused some corpora servers to go down.

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

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 medium confidence (taxonomy v0.2).

1. resolved 2024-06-25 07:00 UTC

   On of the indexing servers OOMed, due to which indexing requests going to that server failed. The OOM resulted in the server to be in a limbo state, which the liveness prober did not detect as FAILURE and hence, did not restart the server in time. This resulted in a long partial...

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

Affected: Admin, Index

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 2024-05-09 18:07 UTC

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

2. resolved 2024-05-09 18:11 UTC

   This incident has been resolved.

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

Affected: Admin, Index

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. identified 2024-05-08 13:34 UTC

   Some customers may see slow corpus creation times and slow indexing times.

2. resolved 2024-05-08 13:39 UTC

   This incident has been resolved.

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

Affected: Index

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. investigating 2024-05-06 00:26 UTC

   We are currently investigating this issue.

2. resolved 2024-05-06 00:33 UTC

   This incident has been resolved.

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

Affected: Index

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. investigating 2024-05-04 00:11 UTC

   Indexing is currently experiencing delays for some customers and corpora.

2. identified 2024-05-04 00:31 UTC

   Working on rolling out a fix and should be resolved within the next 20 minutes.

3. resolved 2024-05-04 02:05 UTC

   This incident has been resolved.

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