Resolved after 32 minutes, on October 14, 2026.
This incident has been resolved. Root cause: a sporadic load spike on our database temporarily degraded API response times between 13:00 and 13:09 UTC. Total impact during this window: out of approximately 7,200 API requests, 121 (1.7%) exceeded 7 seconds or timed out, while the remaining 7,090 stayed within the expected response time range. No server errors occurred and no data was lost. Response times returned to normal at 13:09 UTC and have remained stable since. We have identified the internal process that caused the load spike and are taking measures to prevent it from recurring.
Update timeline
- investigating Oct 14, 2026, 01:05 PM UTC
We are investigating slower than usual response times.
- resolved Oct 14, 2026, 01:37 PM UTC
This incident has been resolved. Root cause: a sporadic load spike on our database temporarily degraded API response times between 13:00 and 13:09 UTC. Total impact during this window: out of approximately 7,200 API requests, 121 (1.7%) exceeded 7 seconds or timed out, while the remaining 7,090 stayed within the expected response time range. No server errors occurred and no data was lost. Response times returned to normal at 13:09 UTC and have remained stable since. We have identified the internal process that caused the load spike and are taking measures to prevent it from recurring.
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