Cause: A configuration dependency in our middleware environment prevented the service from restarting correctly after an infrastructure instance change.
Resolution: We switched to our redundant environment, and service has been stable since approx. [07:05] CEST.
Posted Oct 16, 2026 - 10:49 CEST
Update
Monitoring in progress.
All Tangany APIs remain fully operational and reachable following the fix applied at 07:05 CEST.
Our engineering team is continuing to actively monitor platform health and stability while completing the root cause investigation. We will provide another update once the monitoring period is concluded.
Activity start time: 16 October 2026, 02:20 CEST Activity end time (service restored): 16 October 2026, 07:05 CEST
Posted Oct 16, 2026 - 09:50 CEST
Monitoring
We would like to inform you that Tangany APIs experienced a service disruption, which has now been mitigated. All APIs are reachable and working normally again. We apologise for any inconvenience. Kindly find the summary below.
Incident summary: Tangany APIs, including the Settlement API, Custody API, and Customers API, were unavailable. API requests returned a "Middleware Error". All partners were affected.
Issue start time: 16 Oct 02:20 CEST
Issue resolution time: 16 Oct 07:05 CEST
Impacted Services: Settlement API, Custody API, Customers API Backend
Root cause: Under investigation. We will share further details once the analysis is complete.
Recovery: Switchover of traffic to a backup Middleware service instance
All affected services are operating normally again. We are continuing to monitor the platform closely and will post another update once root cause analysis is complete.
Posted Oct 16, 2026 - 08:44 CEST
This incident affected: Tangany Custody API (API backend), Tangany Customers API (API backend), and Tangany Settlement API (API backend).