Increased error rates for microsoft-multilingual-e5-large
Aug 13, 08:32 UTCAug 17, 11:40 UTC
Duration
4d 3h
Impact
Major
Root cause
Dependency
Elastic, 90 days
22 incidents
Affected
Not listed by the vendor.
Final update
The microsoft-multilingual-e5-large model has been retired from the Elastic Inference Service. Requests to this model now return an error. Customers who wish to use this model with Elastic cloud must create a custom inference endpoint using their own API key. See our inference documentation for further details: https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-inference
Timeline
- Resolved · Aug 17, 11:40 UTC
The microsoft-multilingual-e5-large model has been retired from the Elastic Inference Service. Requests to this model now return an error. Customers who wish to use this model with Elastic cloud must create a custom inference endpoint using their own API key. See our inference documentation for further details: https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-inference
- Monitoring · Aug 13, 18:26 UTC
Unfortunately, we can no longer support the E5 Multilingual Large model on the Elastic Inference Service due to continued upstream provider issues. Any customers requiring this model should set up custom inference endpoints using their own API keys.
- Investigating · Aug 13, 14:45 UTC
We're seeing some improvement in availability but are continuing to monitor the situation. We will follow up with more information in due course.
- Investigating · Aug 13, 08:32 UTC
We are seeing elevated error rates from the upstream provider for the microsoft-multilingual-e5-large embedding model. Search embedding requests to this model may fail. We are investigating
More from Elastic
Full historymOLTP PrivateLink connectivity issuelasted 13h 28mElastic Support Portal is unavailablelasted 2h 29m403 error when trying to access Autoops in newly created serverless projectslasted 9h 31mElastic Cloud scaling issues in Azurelasted 6h 57mDegraded availability for some Elastic Cloud Hosted and Serverless deployments in GCP europe-west2 (London)lasted 15h 3mDelayed or Unavailable project operation in GCP us-central1lasted 8h 12m