Monkey Exchange incident
[SUPPLY BANK] We are currently experiencing a performance degradation issue affecting platform.
Monkey Exchange experienced a minor incident on November 25, 2025 affecting PORTAL and REPORT and 1 more component, lasting 53m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Nov 25, 2025, 07:16 PM UTC
We are currently investigating this issue.
- identified Nov 25, 2025, 07:25 PM UTC
The issue has been identified and a fix is being implemented.
- identified Nov 25, 2025, 07:29 PM UTC
We have identified an unexpected disruption in one of our Kubernetes nodes, which impacted the performance of parts of our infrastructure. As a result, some applications are being reallocated to restore stability. Our team is actively working to normalize the environment.
- monitoring Nov 25, 2025, 07:36 PM UTC
All applications have been reallocated to new nodes and the environment has been normalized. Our team is continuing to monitor the system.
- resolved Nov 25, 2025, 08:10 PM UTC
To reinforce the resilience of our infrastructure, we implemented a preventive expansion of our Kubernetes node capacity. Our autoscaling mechanisms operated as expected during the recent event. However, by increasing the number of active nodes, we add an additional layer of redundancy that minimizes the impact of any potential node unavailability. This adjustment enhances the distribution of workloads, reduces the likelihood of performance fluctuations, and ensures that services remain fully operational even in scenarios where individual nodes experience unexpected interruptions. The change aligns with our commitment to maintaining a highly stable and robust platform for all clients.