API Service Degradation

We are committed to providing a reliable and stable platform for our B2B partners. We sincerely apologize for the disruption experienced on December 1, 2025, which resulted in intermittent API service degradation. We have fully resolved the issue and restored all services to normal operation.

‌

What Happened

At approximately 10:37pm ET on December 1, 2025, our internal monitoring systems detected an elevated error rate in our primary production API services.

The disruption was triggered by the unexpected failure of several core internal compute resources (nodes) within our cloud infrastructure. This failure led to the abrupt restart of various underlying financial services and associated processing jobs, which in turn caused the elevated error rate and connectivity issues for our clients.

Our engineering teams immediately mobilised to isolate the failure and restore system health. We quickly identified the cause as a resource scheduling constraint preventing new nodes from scaling up to replace the failed ones.

Impact

The incident was mitigated within 17 minutes.

• API Connectivity: Clients experienced brief connection failures and elevated 5xx error responses when making API requests.
• Transaction and Data Impact: Approximately 56,400 API requests failed during the brief period of the incident.
• Crucially, we can confirm that no client data was lost, and all funds and transactions remain secure and properly accounted for. Any critical service components that experienced downtime were successfully restarted and recovered without data corruption.

Resolution

Our primary focus was on rapidly mitigating the service impact:

1. Stabilisation and Service Restoration: The affected systems automatically restarted after new compute resources became available.
2. Full Service Verification: We confirmed the complete resolution of the underlying node issues and verified the full functionality of our core API and trading systems.

Preventative Measures and Commitment

To prevent a recurrence of this issue and strengthen the resilience of our platform, our teams are prioritizing the following action items:

• System Resilience & Monitoring: We will conduct a thorough review of the replication and redundancy settings for affected systems and dependencies. We are increasing the number of instances for some services to reduce the impact of similar failures.
• Service Logging and Observability: We identified several logs that could be adjusted to accelerate diagnosing outages in the future and are making changes to them.
• Minor Bug Fixes: We identified a few minor improvements in the way our services handled the failure and are updating those services, which should accelerate recovery in the future.

We are committed to maintaining the highest standards of reliability and transparency. We appreciate your patience and understanding as we continue to invest in our platform's stability