Salt Edge Outage History

## Executive Summary On March 26, 2026, between **11:28 and 14:09 UTC**, our Payments API experienced a temporary disruption that prevented successful processing of payment initiation from Partners. The incident has been fully resolved. **We sincerely apologize for the interruption and any impact this may have caused to your operations.** ## **Incident Overview** | | | | --- | --- | | **Incident Date** | 26 Mar 2026 | | **Duration** | 151 minutes \(11:28-14:09 UTC\) | | **Impact** | Temporary inability to process payment initiation and account information requests. | | **Current Status** | ✅ **Resolved**. Infrastructure restored and operating normally | ## What Happened The disruption was caused by issues with transport certificates, which affected our payment initiation service for partners. This was not related to any client-side integration or API change. ## Timeline \(UTC\) | Time | Event | | --- | --- | | 11:28 | Service disruption detected via email alerts | | 11:30 | Engineering team engaged | | 12:22 | The root cause was detected | | 14:09 | Services fully restored | ## Root Cause The disruption was caused by issues with transport certificates. This was not related to any client-side integration or API change. ## Resolution The issue was resolved by reissuing new certificates. Normal payment processing resumed at **14:09 UTC**. ## Detection The incident was detected automatically via our service availability monitoring system \(emails\), which triggered alerts indicating degradation of services. The engineering team responded immediately upon alert notification. ## Contact If you have any questions about this incident or need assistance with affected transactions, please contact your account manager or reach out to our support team. We remain committed to providing reliable payment services and appreciate your continued partnership. _This report is intended for authorized partners only. Please do not distribute externally._

## Executive Summary On March 10, 2026, between **12:33 and 13:00 UTC**, our Payment Initiation Service and Account Information Service experienced a temporary disruption that prevented successful processing of payment initiation and account information requests from clients and partners. The incident has been fully resolved. **We sincerely apologize for the interruption and any impact this may have caused to your operations.** ## Incident Overview | | | | --- | --- | | **Incident Date** | 10 Mar 2026 | | **Duration** | ~27 minutes \(12:30-13:00 UTC\) | | **Impact** | Temporary inability to process payment initiation and account information requests. | | **Current Status** | ✅ **Resolved**. Infrastructure restored and operating normally | ## What Happened The disruption was caused by an infrastructure-level configuration change required due to hardware-related issues affecting one of our network components. As a result of this change, the application layer temporarily lost the ability to establish database connections. This was not related to any client-side integration or API change. ## Timeline \(UTC\) | Time | Event | | --- | --- | | 12:33 | Service disruption detected via monitoring alerts | | 12:34 | Engineering team engaged | | 12:45 | Corrective action applied | | 12:46 | First successful payment processed | | 13:00 | Services fully restored. | ## Root Cause The disruption was caused by an infrastructure-level configuration change required due to hardware-related issues affecting one of our network components. As a result of this change, the application layer temporarily lost the ability to establish database connections, leading to payment processing failures. This was not related to any client-side integration or API change. ## Resolution The issue was resolved by restarting affected application processes to ensure proper re-establishment of database connections following the infrastructure update. Normal payment processing resumed at **12:45 UTC**. The first successful payment after recovery was processed at **12:46 UTC**. ## Corrective & Preventive Measures We have initiated the following actions to prevent recurrence: 1. **Application-level resilience improvements** Enhancing database connection handling to better tolerate infrastructure changes. 2. **Additional validation checks** Implementing safeguards to ensure application awareness of infrastructure-level changes in real time. ## Contact If you have any questions about this incident or need assistance with affected transactions, please contact your account manager or reach out to our support team. We remain committed to providing reliable payment services and appreciate your continued partnership. _This report is intended for authorized partners only. Please do not distribute externally._

## Executive Summary On February 23, 2026, several OBG APIs experienced temporary unavailability due to infrastructure-level connection saturation. The incident lasted 24 minutes, during which API requests returned HTTP 500 errors. We sincerely apologize for any disruption this may have caused to your operations. The issue has been fully resolved, and preventive measures have been implemented. **We sincerely apologize for the interruption and any impact this may have caused to your operations.** ## Incident Overview | | | | --- | --- | | **Incident Date** | 23 Feb 2026 | | **Duration** | 24 minutes \(12:31-12:55 UTC\) | | **Impact** | Temporary API errors \(HTTP 500\) | | **Current Status** | ✅ Fully Resolved | ## What Happened Following a configuration change related to backend service connectivity, infrastructure connection limits were reached under production load. As a result: * New API requests could not establish required backend connections * Applications returned HTTP 500 responses * Service availability was temporarily degraded The issue was isolated to infrastructure connection handling and did not involve data corruption or data loss. ## Timeline \(UTC\) | Time | Event | | --- | --- | | 12:33 | Elevated API error rate detected | | 12:34 | Incident declared following monitoring alerts | | 12:50 | Root cause identified | | 12:54 | Immediate mitigation actions applied | | 12:55 | Services fully restored | ## Root Cause The incident was caused by connection saturation at the infrastructure layer following a backend configuration change. The existing connection handling limits were insufficient for the increased connection load introduced by the new architecture. This resulted in temporary rejection of new backend connections and API errors. ## Resolution To restore service, our engineering team: * Reverted the recent backend configuration change * Cleared saturated connection state * Increased infrastructure connection limits * Verified service stability under load Service was fully restored within 24 minutes. ## **Preventive Measures** We are implementing the following improvements: ✅ Increased infrastructure connection limits across relevant components 🔄 Implementing proactive monitoring and alerting for connection utilization 🔄 Reviewing connection handling configuration across services 📋 Introducing mandatory infrastructure capacity review prior to architectural changes ## Contact If you have any questions about this incident or need assistance with affected transactions, please contact your account manager or reach out to our support team. We remain committed to providing reliable payment services and appreciate your continued partnership. _This report is intended for authorized partners only. Please do not distribute externally._