Salt Edge experienced a critical incident on May 15, 2025 affecting Account Information API and Payments API and 1 more component, lasting 22m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 15, 2025, 12:55 PM UTC
We experienced a temporary issue affecting the availability of our services, and some customers may have encountered HTTP 500 Internal Server Errors starting with 15-05-2025 15:46 GMT +3
- identified May 15, 2025, 01:03 PM UTC
Issue identified. We are working on restoring the service.
- identified May 15, 2025, 01:12 PM UTC
The issue regarding Account Information API, Payments API and Partners API has been resolved at 16:12 GTM +3
- resolved May 15, 2025, 01:17 PM UTC
The incident has been fully resolved at 16:16, GMT +3 All systems are now operating normally, and we continue monitoring the platform closely to ensure stability. We appreciate your patience and understanding.
- postmortem May 16, 2025, 02:30 PM UTC
**Incident summary:** On May 15, 2025, between 12:45 UTC and 13:03 UTC, Salt Edge experienced a partial outage affecting Open Banking Gateway endpoints, including Account Information API, Payments API, Partners API, Dashboards which led to unavailability of services and 500 errors returned to our clients. **Root cause:** The issue was caused by an internal configuration update that, due to a post-upgrade inconsistency in system behaviour, led to incorrect service settings being applied. As a result, certain backend components failed to start properly, making the API temporarily inaccessible. **Resolution:** Our Engineering team promptly identified the root cause, halted automated configuration updates to prevent further spread, and manually restored the correct service settings. The affected services were fully recovered by 13:03 UTC on May 15, 2025. **Action points:** * Implement high-availability setup for critical configuration management systems. * Introduce a safe mechanism to disable automated configuration runs when needed. * Deploy enhanced tools for monitoring and auditing configuration changes.