API key issuing degraded
none- Started
- Sep 23, 4:16 PM EDT
- Resolved
- Sep 23, 5:07 PM EDT
- Duration
- 50 min
Cartesia's updates (4)
- investigating · Sep 23, 4:16 PM EDT
We've identified an issue where new API keys result in an "Invalid API key" error.
- identified · Sep 23, 4:26 PM EDT
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.
- identified · Sep 23, 5:06 PM EDT
Newly created API keys issued during this this period are invalid. Please create new API keys.
- resolved · Sep 23, 5:07 PM EDT
This incident has been resolved.
What our checks recorded
We checked Cartesia 10 times from Cartesia's start time to its resolution, once every five minutes. Every one of them reached Cartesia's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 120 ms, against 129 ms over the 24 hours before. Cartesia posted the incident at Sep 23, 4:16 PM EDT.
Updates are Cartesia's own words from its status page (status: resolved); we never add an inferred cause.