Statusfield LogoStatusfield
R2Capital status
R2Capital logo and current status indicator

R2Capital Incident History

Operational

r2capital.co ↗1 top-level component

checked Oct 25, 2026 1:48 AM UTC · R2Capital's official status page

R2Capital is up and running.

R2Capital is currently operational with all systems functioning normally.

All components operational

Be the first to know

Statusfield watches R2Capital alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.

30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.

R2Capital incident history

4 reports published by R2Capital in the last 30 days

When R2Capital breaks, it is typically resolved in 1h 8m — median across 3 resolved incidents over 30 days.

October 14, 2026

Degraded response times

Last update

  1. resolvedOct 14 · 13:37 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.

Reported by R2Capital on their status page.

October 10, 2026

Elevated error rate

Last update

  1. resolvedOct 11 · 00:04 UTC

    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.

Reported by R2Capital on their status page.

October 9, 2026

Degraded response times

Last update

  1. resolvedOct 10 · 00:06 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.

Reported by R2Capital on their status page.

September 30, 2026

Degraded response times

Last update

  1. resolvedSep 30 · 14:05 UTC

    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.

Reported by R2Capital on their status page.