Rime
AI. Source: Rime status page.
History starts 2026-09-03 01:52 UTC, the oldest incident this status page still shows. Figures for the last 90 days cover only the part since then.
- Incidents, last 90 days
- 2+
- Median to mitigation
- not reported
- Median to resolution
- 1h 5m
- p95 to resolution
- 1h 21m
- Naming an upstream provider
- 0%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| The text does not say enough to tell | 1 |
| Exhausted memory, disk, CPU, queues, connection pools or quotas | 1 |
Tagged by deepseek/deepseek-v4.1-flash from each incident's updates. See the methodology.
Incidents per month
Hatched months are before the recorded history starts.
All recorded incidents
Text-to-speech APIs are partially degraded
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).
-
investigating
A component of Rime's text-to-speech APIs is partially degraded. We are investigating the incident.
-
resolved
The incident has been resolved.
Excerpts are shortened. Read the full incident on Rime's status page.
Text-to-speech APIs are partially degraded
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
A component of Rime's text-to-speech APIs is partially degraded. We are investigating the incident.
-
resolved
We had an issue with our database connections which led to request failures. This is resolved now and we are closely monitoring the situation.
Excerpts are shortened. Read the full incident on Rime's status page.