Major Outage

Update timeline

1. investigating Feb 23, 2026, 12:53 PM UTC

   We are currently investigating this issue.

2. identified Feb 23, 2026, 12:56 PM UTC

   The issue has been found and fixed.

3. resolved Feb 23, 2026, 01:01 PM UTC

   We want to inform you that the issue affecting the availability of the API service was identified and resolved at 12:54:41 UTC on February 23rd. Our team took the necessary actions to mitigate the impact and restore full functionality. All systems are now operating normally, and we continue monitoring the platform closely to ensure stability. We appreciate your patience and understanding.

4. postmortem Feb 24, 2026, 01:01 PM UTC

   ## 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._