This is an example incident

What to do

• Check whether your product depends on Cartesia. 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 0m it lasted.

  Anything that failed between 2026-07-10 17:15 UTC and 2024-07-17 17:43 UTC may need a replay.

• Subscribe to Cartesia's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=cartesia works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Cartesia 4

1. monitoringJul 17, 2024, 5:33 PM UTC

   Let your users know once a fix is in place, and keep communication clear and precise.

   provider

2. identifiedJul 17, 2024, 5:39 PM UTC

   As you continue to work through the incident, update your customers frequently.

   provider

3. resolvedJul 17, 2024, 5:43 PM UTC

   Empathize with those affected and let them know everything is operating as normal.

   provider

4. investigatingJul 17, 2024, 6:09 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.