Root had 12 outages in the last 2 years totaling 8h 37m of downtime — averaging 0.5 incidents per month.
There were 12 Root outages since February 28, 2025 totaling 8h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
Dashboard is available. We are monitoring.
This incident has been resolved.
Database contention resulted in a short (~1 min) burst of API requests failures before self-resolving.
A fix has been implemented and we are monitoring the results.
No impact to clients.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and rollback. We are continuing investigations across all domains.
We are continuing to monitor for any further issues.
Degraded performance. We are continuing to monitor and resolve any further issues.
This incident has been resolved.
We are experiencing API timeouts and degraded performance due to database connection pool exhaustion. Impact: Users may experience: - Slow API responses - Timeout errors on policy issuance and other operations - Failed requests requiring retries
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
Unable to create or view policy notes
We are currently investigation the issue.
This incident has now been resolved. Customers may have experienced up to one hour's delay in receiving policy and terms documents.
Product module code functions timing out
We are continuing to investigate this issue.
We are continuing to investigate this issue.
This incident has been resolved.