Database read timeouts
critical- Started
- Jul 17, 4:13 PM EDT
- Resolved
- Jul 17, 4:36 PM EDT
- Duration
- 23 min
Cartesia's updates (3)
- investigating · Jul 17, 4:13 PM EDT
We are investigating the issue and what components are affected.
- monitoring · Jul 17, 4:29 PM EDT
We have mitigated the issue on our end and are continuing to monitor the state of our service.
- resolved · Jul 17, 4:36 PM EDT
This incident has been resolved.
What our checks recorded
We checked Cartesia 5 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 137 ms, against 136 ms over the 24 hours before. Cartesia posted the incident at Jul 17, 4:13 PM EDT.
Updates are Cartesia's own words from its status page (status: resolved); we never add an inferred cause.