Is R2Capital down?

We are investigating slower than usual response times.

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.

We are investigating elevated error rates affecting some API requests.

We are investigating reports of errors on payment requests. We will provide an update as soon as we have more information.

Payment requests have been working normally since 23:48 UTC. We are monitoring to make sure the issue does not happen again.

This incident has been resolved. A brief disruption in our API gateway at 23:48 UTC caused a small number of payment requests to fail for about one second. No payments were processed incorrectly, and any affected request can be safely retried. We have seen no further errors since.

We are investigating slower than usual response times.

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.

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.

We are investigating slower than usual response times.

The cause of the slower than usual response times has been identified: a temporary spike in processing volume. Requests are completing successfully, but some are taking longer than normal. We are working on restoring normal response times.

Response times returned to normal levels. We are monitoring to confirm the service remains stable before closing this incident.

This incident has been resolved. Response times returned to normal and the service has been operating normally since. The slowdown was caused by a temporary spike in processing volume, and requests continued to be processed throughout.