# This is an example incident

- Provider: [Cartesia](https://down.guide/cartesia)
- Level: confirmed
- Impact: Operational
- lasted 0m
- started 2026-07-10 17:15 UTC
- id: DWN-42ac395309
- Official page: https://status.cartesia.ai/incidents/01KX6GEBNJX862WX9TZYEXW8BF

## Updates from Cartesia
### 2024-07-17 17:33 UTC: monitoring
Let your users know once a fix is in place, and keep communication clear and precise.

### 2024-07-17 17:39 UTC: identified
As you continue to work through the incident, update your customers frequently.

### 2024-07-17 17:43 UTC: resolved
Empathize with those affected and let them know everything is operating as normal.

### 2024-07-17 18:09 UTC: investigating
When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.

From the builder: does your app depend on Cartesia? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=cartesia) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Cartesia.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-42ac395309), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
