Elevated 503s on voyage-context-4
This incident has been resolved
The latest update from Voyage AI.
State
Resolved
Started
47 d ago
2026-09-15 12:52 UTC
Lasted
28 min
until 2026-09-15 13:20 UTC
Worst impact
Partial outage
Timeline
4 updatesInvestigating
18 min 63%
Monitoring
10 min 37%
Updates
Times in UTCAs posted by Voyage AI
This incident has been resolved
We are continuing to monitor for any further issues.
A fix has been implemented and we are monitoring the progress
We are currently investigating the issue
Affected components
1Voyage AI in the last 90 days
Full historyIncidents in 90 days
5
Days with an incident
4
Median duration
25 min
This incident
About the median
Other Voyage AI incidents
All incidentsVoyage AI·Elevated latencies for voyage-4-large document path
The incident has been resolved
Voyage AI·Elevated 5xx errors on rerank and voyage-context-4
The incident has been resolved
Voyage AI·Elevated 503s on rerank models and voyage-4-large
This incident has been resolved
Voyage AI·Elevated 503s on Voyage-4-large
The incident has been resolved.
Follow Voyage AI
Your coding agent knows when Voyage AI is down, and tells you when a failure is theirs, not yours. You can also get Voyage AI incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "voyage" and tell me if Voyage AI has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=voyage/feed subscribe https://outages.cc/feed.xml?providers=voyageFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane