API key issuing degraded

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 50m it lasted.

  Anything that failed between 2026-09-23 20:16 UTC and 2026-09-23 21:07 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. investigatingSep 23, 2026, 8:16 PM UTC

   We've identified an issue where new API keys result in an "Invalid API key" error.

   provider

2. identifiedSep 23, 2026, 8:26 PM UTC

   We've traced the issue to a bug in a change to our API key issuing logic that caused new keys to not be persisted correctly. The change is being reverted. Existing production traffic is not affected. We are exploring remediation options for API keys that were issued during the incident.

   provider

3. identifiedSep 23, 2026, 9:06 PM UTC

   Newly created API keys issued during this this period are invalid. Please create new API keys.

   provider

4. resolvedSep 23, 2026, 9:07 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

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