Vendor reports: partial outageResolved · vendor status “resolved”Official status API
VoyageAI elevated errors
Reported by MongoDB Atlas · Databases · source last read 4 min ago
- Vendor start
- Jul 27, 2026, 23:37 UTC
- Vendor's clock
- Resolved
- Jul 27, 2026, 23:48 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 11 min
- From vendor start and resolution
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
Affected products and regions
- Components: VoyageAI Embedding and Reranking Models.[E6]
What is unknown
- Which regions are affected: the vendor did not say.[E5]
- Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.
Last update in these facts: 2026-07-27 23:48 UTC · summary s1, evidence d77748f2deda3a1e
Evidence (7)
- E1MongoDB Atlas reports partial outage. (vendor) source (opens in a new tab)
- E2Vendor title: "VoyageAI elevated errors". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-07-27 23:37 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6Components the vendor attached: VoyageAI Embedding and Reranking Models. (vendor) source (opens in a new tab)
- E7Vendor-reported resolution: 2026-07-27 23:48 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: VoyageAI Embedding and Reranking Models
No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.
Potential relevance
MongoDB Atlas is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Jul 27, 2026, 23:37 UTCVendor-reported startVendor time
- Jul 27, 2026, 23:48 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.