Monkey Exchange incident
[SUPPLY BANK] We are currently experiencing a performance degradation issue affecting platform.
Monkey Exchange experienced a major incident on December 8, 2025 affecting PORTAL and REPORT and 1 more component, lasting 1h 20m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Dec 08, 2025, 02:07 PM UTC
We are currently investigating this issue.
- identified Dec 08, 2025, 02:22 PM UTC
The issue has been identified and a fix is being implemented.
- identified Dec 08, 2025, 02:38 PM UTC
We have identified a communication failure between some of our servers and our workload manager, which affected the application distribution process.
- monitoring Dec 08, 2025, 02:59 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Dec 08, 2025, 03:05 PM UTC
Communication between our services and the workload manager has been restored, and the environment is stable. We continue to monitor the situation and will update this page soon with more information about the incident.
- resolved Dec 08, 2025, 03:27 PM UTC
We have experienced an instability in Kubernetes CoreDNS that caused our internal name resolution to fail, and as a consequence, our alerting pipeline was impacted, since alerts rely on webhooks that could not be delivered. As an improvement action, we will deploy CoreDNS as a DaemonSet to ensure resilience and consistent availability across all nodes. We will also add an internal DNS probe within the cluster to monitor DNS-related failures and provide early detection even when CoreDNS is degraded.