Resolved after 1 hour 10 minutes, on October 9, 2026.
This incident has been resolved. Root cause: database capacity saturation, compounded by a cluster node with intermittent network errors. Database capacity has been increased and the affected node was removed from service. Total impact between 22:45 and 23:55 UTC: 1,157 API requests timed out before receiving a response, and 117 additional requests completed successfully with degraded response times. No server errors occurred and no data was lost on our side. Response times and error rates have returned to normal, and we will continue monitoring. We are preparing a full root cause analysis (RCA) and will share it soon.
Update timeline
- investigating Oct 09, 2026, 10:55 PM UTC
We are investigating slower than usual response times.
- monitoring Oct 09, 2026, 11:43 PM UTC
We identified the root cause: database capacity saturation that degraded response times for approximately 90 API requests between 22:48 and 23:20 UTC. All affected requests completed successfully and no data was lost. Database capacity has been increased and response times have returned to normal. We are monitoring the platform before marking this incident as resolved.
- resolved Oct 10, 2026, 12:06 AM UTC
This incident has been resolved. Root cause: database capacity saturation, compounded by a cluster node with intermittent network errors. Database capacity has been increased and the affected node was removed from service. Total impact between 22:45 and 23:55 UTC: 1,157 API requests timed out before receiving a response, and 117 additional requests completed successfully with degraded response times. No server errors occurred and no data was lost on our side. Response times and error rates have returned to normal, and we will continue monitoring. We are preparing a full root cause analysis (RCA) and will share it soon.
Your product runs on more than R2Capital
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services