- Level
- confirmed
- Worst impact
- Major outage
- Components
- API
- Down Index
- 49of 100
What to do
Check whether you use Voyage AI API. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 58m it lasted.
Anything that failed between 2025-05-28 21:20 UTC and 2025-05-28 22:18 UTC may need a replay.Subscribe to Voyage AI's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=voyage works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Voyage AI 5
- investigating
The new config change made some of the gateway unable to connect to the database. Approximately 10% of the traffic got authentication error mistakenly.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- identified
We have identified the error and are working on a rollback
provider
- monitoring
A fix has been implemented and we are monitoring the results
provider
- resolved
This issue has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-85cc05ad63
Is Voyage AI still down?
No, this incident was resolved 2025-05-28 22:18 UTC. For Voyage AI's live state, see https://down.guide/voyage.
How long did it last?
58m, from 2025-05-28 21:20 UTC to 2025-05-28 22:18 UTC, by the times Voyage AI posted.
What was affected?
Voyage AI named API.
What caused it?
Voyage AI hasn't published a root cause. If it does, it shows here.
Where does this come from?
Voyage AI's official status page, https://voyageai-status.statuspage.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.