R2Capital incident

Degraded response times

Minor Resolved View vendor source →

R2Capital experienced a minor incident on September 30, 2026, lasting 55m. The incident has been resolved; the full update timeline is below.

Started
Sep 30, 2026, 01:10 PM UTC
Resolved
Sep 30, 2026, 02:05 PM UTC
Duration
55m
Detected by Pingoru
Sep 30, 2026, 01:10 PM UTC

Update timeline

  1. investigating Sep 30, 2026, 01:10 PM UTC

    We are investigating slower than usual response times.

  2. identified Sep 30, 2026, 01:58 PM UTC

    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.

  3. monitoring Sep 30, 2026, 02:00 PM UTC

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

  4. resolved Sep 30, 2026, 02:05 PM 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.