Resolved after 11 minutes, affecting Text to Speech (EU), on November 10, 2025.
We had a scheduled node migration during this timeframe that was intended to be a no-op. The intermediary cluster to which the `api-eu` domain specifically was routed to was not expected to affect, but unfortunately the `api-eu` was not properly whitelisted. This was a gap in our health checks that we did not catch this immediately and rollback, we'll be updating that in our pipeline. The primary `api` route with geosteering was unaffected, even if called from the EU domain.
Affected components
Update timeline
- identified Nov 10, 2025, 07:53 AM UTC
As part of a scheduled node migration, the EU specific domain was routed to a new node. This appears to not be working as intended, we're deploying a fix shortly.
- monitoring Nov 10, 2025, 07:55 AM UTC
We've deployed a fix for the route.
- monitoring Nov 10, 2025, 07:58 AM UTC
We are continuing to monitor for any further issues.
- resolved Nov 10, 2025, 08:04 AM UTC
Users appear to confirm that this has been resolved since. Will update retroactively with a more thorough RCA.
- postmortem Nov 10, 2025, 08:34 AM UTC
We had a scheduled node migration during this timeframe that was intended to be a no-op. The intermediary cluster to which the `api-eu` domain specifically was routed to was not expected to affect, but unfortunately the `api-eu` was not properly whitelisted. This was a gap in our health checks that we did not catch this immediately and rollback, we'll be updating that in our pipeline. The primary `api` route with geosteering was unaffected, even if called from the EU domain.
Your product runs on more than Cartesia
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services