Salt Edge Outage History

Started Oct 20, 2026, 07:30 AM UTC· resolved Oct 20, 2026, 05:31 PM UTC

1. identified Oct 20, 2026, 08:34 AM UTC

   Revolut is currently experiencing an incident on their side, which started on October 20, 2026, at 08:30 UTC. Clients can experience issues when initiating payments and establishing connections with Revolut providers. We are monitoring the situation and will update this status page once the incident has been resolved. For the latest updates, please refer to Revolut's System Status page: https://www.revolut.com/system-status/.

2. identified Oct 20, 2026, 08:45 AM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Oct 20, 2026, 04:20 PM UTC

   We observe successful attempts for both payments and connections initiated with Revolut, however, Revolut's System Status page has not yet been updated to reflect these improvements. We will continue monitoring the situation and provide further updates as necessary, once the incident is confirmed to be fully resolved. For the latest updates, please refer to Revolut's System Status page: https://www.revolut.com/system-status/

4. monitoring Oct 20, 2026, 04:23 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Oct 20, 2026, 05:31 PM UTC

   The incident on the Revolut side has been fully resolved. For the latest updates, please refer to Revolut's System Status page: https://www.revolut.com/system-status/

Read the full incident report →

Started Sep 29, 2026, 11:36 AM UTC· resolved Sep 29, 2026, 11:36 AM UTC

1. resolved Sep 30, 2026, 10:37 AM UTC

   Some customers were unable to access Salt Edge services due to a routing issue affecting our upstream provider. During emergency maintenance, the provider restarted its BGP sessions, temporarily withdrawing and then re-announcing the affected IP routes. This caused a five-minute service interruption. Connectivity was restored, and all services are operating normally.

Read the full incident report →

Started Aug 21, 2026, 09:41 AM UTC· resolved Aug 21, 2026, 09:57 AM UTC

1. investigating Aug 21, 2026, 09:41 AM UTC

   We are currently investigating an issue affecting Open Banking Gateway and Open Banking Compliance. Customers may experience failed requests. The issue started at approximately August 21st 09:29 Our engineering team is actively investigating the cause and working to restore normal operation as quickly as possible. Next update will be provided as soon as more information becomes available.

2. identified Aug 21, 2026, 09:45 AM UTC

   We are currently experiencing service unavailability caused by a network infrastructure issue at our data center provider. The issue has been identified by the data center provider and their engineers are currently working on resolving it. Our team is monitoring the situation and we will provide an update as soon as more information becomes available. We apologize for the inconvenience.

3. monitoring Aug 21, 2026, 09:46 AM UTC

   Our affected services have been restored and are currently operational. We continue to monitor the situation, while the data center provider is still working on the underlying network incident.

4. resolved Aug 21, 2026, 09:57 AM UTC

   The incident has been fully resolved. Incident duration: From August 21st, 9:27 in UTC Until August 21st, 9:37 in UTC All services are now operating normally. Our team continues to monitor the system to ensure stability. We appreciate your patience and understanding.

Read the full incident report →

Started Jul 28, 2026, 12:35 PM UTC· resolved Jul 28, 2026, 12:47 PM UTC

1. investigating Jul 28, 2026, 12:35 PM UTC

   We are currently investigating an issue affecting Open Banking Gateway. Customers may experience failed requests. The issue started at approximately July 28th, 12:09 in UTC. Our engineering team is actively investigating the cause and working to restore normal operation as quickly as possible. Next update will be provided as soon as more information becomes available.

2. identified Jul 28, 2026, 12:43 PM UTC

   We have identified the cause of the issue affecting the Open Banking Gateway. At this time, customers may still experience failed requests. Our team is implementing mitigation measures to restore full functionality. We will continue to provide updates as progress is made.

3. monitoring Jul 28, 2026, 12:43 PM UTC

   A fix has been implemented and services are recovering. We are currently monitoring the system to ensure that the Open Banking Gateway is operating normally. Customers may experience minor delays while the system fully stabilizes.

4. resolved Jul 28, 2026, 12:47 PM UTC

   The incident has been fully resolved. Incident duration: From July 28th, 12:09 in UTC Until July 28th, 12:40 in UTC All services are now operating normally. Our team continues to monitor the system to ensure stability. We appreciate your patience and understanding. A detailed postmortem will be published shortly.

Read the full incident report →

Started May 19, 2026, 12:03 PM UTC· resolved May 19, 2026, 12:11 PM UTC

1. investigating May 19, 2026, 12:03 PM UTC

   We are currently investigating an issue affecting Open Banking Gateway. Customers may experience failed requests. The issue started at approximately May 19th, 11:51 in UTC. Our engineering team is actively investigating the cause and working to restore normal operation as quickly as possible. Next update will be provided as soon as more information becomes available.

2. identified May 19, 2026, 12:08 PM UTC

   We have identified the cause of the issue affecting the Open Banking Gateway. At this time, customers may still experience increased latency. Our team is implementing mitigation measures to restore full functionality. We will continue to provide updates as progress is made.

3. resolved May 19, 2026, 12:11 PM UTC

   The incident has been fully resolved. Incident duration: From May 19th, 11:51 in UTC Until May 19th, 11:57 in UTC All services are now operating normally. Our team continues to monitor the system to ensure stability. We appreciate your patience and understanding. A detailed postmortem will be published shortly.

Read the full incident report →

Started Mar 26, 2026, 12:09 PM UTC· resolved Mar 26, 2026, 02:14 PM UTC

1. investigating Mar 26, 2026, 12:09 PM UTC

   We are currently investigating an issue affecting Payments API for Partners. Customers may experience failed requests. The issue started at approximately 11:28 UTC, March 26th. Our engineering team is actively investigating the cause and working to restore normal operation as quickly as possible. Next update will be provided as soon as more information becomes available.

2. identified Mar 26, 2026, 01:42 PM UTC

   We have identified the cause of the issue affecting Payments API for Partners. At this time, customers may still experience failed requests. Our team is implementing mitigation measures to restore full functionality. We will continue to provide updates as progress is made.

3. resolved Mar 26, 2026, 02:14 PM UTC

   The incident has been fully resolved. Incident duration: From March 26th, 11:28 UTC Until March 26th, 14:09 in UTC All services are now operating normally. Our team continues to monitor the platform to ensure stability. We appreciate your patience and understanding. A detailed postmortem will be published shortly.

4. postmortem Mar 30, 2026, 01:09 PM UTC

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

Read the full incident report →

Started Mar 10, 2026, 01:04 PM UTC· resolved Mar 10, 2026, 01:29 PM UTC

1. investigating Mar 10, 2026, 01:04 PM UTC

   We are currently investigating an issue affecting Payments API. Customers may experience delays in processing payments. The issue started at approximately March 10th, 12:33 in UTC. Our engineering team is actively investigating the cause and working to restore normal operation as quickly as possible. Next update will be provided as soon as more information becomes available.

2. identified Mar 10, 2026, 01:07 PM UTC

   We have identified the cause of the issue affecting Payments API. At this time, customers may still experience delay in processing payments. Our team is implementing mitigation measures to restore full functionality. We will continue to provide updates as progress is made.

3. resolved Mar 10, 2026, 01:29 PM UTC

   The incident has been fully resolved. Incident duration: From March 10th, 12:33 in UTC Until March 10th, 13:00 in UTC All services are now operating normally. Our team continues to monitor the platform to ensure stability. We appreciate your patience and understanding. A detailed postmortem will be published shortly.

4. postmortem Mar 12, 2026, 02:12 PM UTC

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

Read the full incident report →

Started Feb 23, 2026, 12:31 PM UTC· resolved Feb 23, 2026, 01:01 PM UTC

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

Read the full incident report →

Started Jan 11, 2026, 06:01 PM UTC· resolved Jan 11, 2026, 09:10 PM UTC

1. identified Jan 11, 2026, 06:01 PM UTC

   We have received reports from some clients regarding issues with payment notifications. Payments are being processed, but confirmations may be delayed or not delivered. Our team is already investigating the issue and working to resolve it. Further updates will be provided as they become available.

2. identified Jan 11, 2026, 07:25 PM UTC

   The problem with notifications has been resolved. However, the issue now lies with slow payment processing. Our team is still investigating this.

3. resolved Jan 11, 2026, 09:10 PM UTC

   Incident was resolved. All the details and post-mortem will be provided on business hours.

4. postmortem Jan 13, 2026, 03:09 PM UTC

   **Date:** January 11, 2026 **Document Type:** External Client Communication ## Executive Summary On January 11, 2026, our payment processing service experienced a partial degradation affecting some payment transactions. The incident lasted 3 hours and 45 minutes, during which 3,012 payment attempts were impacted. **We sincerely apologize for any inconvenience this may have caused to your business operations.** ## Incident Overview | | | | --- | --- | | **Incident Date** | January 11, 2026 | | **Duration** | 17:11 – 20:56 UTC \(3h 45m\) | | **Impact** | Partial payment processing delays and failures | | **Affected Transactions** | 3,012 payment attempts | | **Current Status** | ✅ Fully Resolved | ## What Happened During a period of increased transaction volume, our payment processing queue experienced elevated load. This resulted in: * Delayed processing of some payment requests * A portion of payment attempts failing due to processing timeouts ## Timeline \(UTC\) | Time | Event | | --- | --- | | 17:11 | Elevated queue times detected; incident declared following partner impact reports | | 17:28 | First mitigation actions deployed | | 18:12 | System services restarted across servers | | 19:08 | Processing capacity increased | | 19:15 | Queue processing times began returning to normal | | 20:56 | Service fully restored; incident resolved | ## Root Cause A gradual degradation in processing performance escalated into delayed payment execution, caused by: Payment processing was impacted as a downstream effect of reduced throughput in a supporting internal service. 1. **An increase in transaction volumes** surpassed the initially provisioned processing capacity 2. **Internal system dependency** experienced performance degradation under load 3. **Processing queue depth** grew faster than the system could recover ## Resolution To restore service, our engineering team: * Increased payment processing capacity by 50% * Scaled up worker processes to handle higher throughput * Increased payment processing capacity to deal with the load, as well as increasing overall excess thresholds * Performed maintenance on internal system dependencies * Monitored queue recovery until processing returned to normal Resolution required a phased mitigation approach: first stabilizing the supporting internal service, then increasing processing concurrency, and finally allowing the backlog to drain. Because the incident manifested as gradual degradation with queue build-up, recovery time included both mitigation and queue catch-up. ## Preventive Measures We are implementing the following improvements to prevent similar incidents: * ✅ **Completed:** Increased processing across all services, including internal dependencies. * 🔄 **In Progress:** Implementing proactive queue monitoring and alerting * 🔄 **In Progress:** Optimizing internal systems to improve performance under high load * 📋 **Planned:** Establishing traffic notification process with partners for capacity planning ## 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._

Read the full incident report →

Started Dec 30, 2025, 08:30 AM UTC· resolved Dec 30, 2025, 10:30 AM UTC

1. resolved Dec 30, 2025, 10:25 AM UTC

   Resolved: 30 December 2025, 10:11 UTC The issue has been fully resolved as of 10:11 UTC. All affected services are operating normally. The platform continues to be closely monitored to ensure stability. Identified: 30 December 2025, 10:02 UTC We identified an issue impacting the Account Information API, Payments API, Partners API and Dashboards. Some customers may have experienced server error responses. Our engineering team investigated the issue and implemented a fix.

Read the full incident report →

Started Jun 23, 2025, 02:52 PM UTC· resolved Jun 23, 2025, 06:01 PM UTC

1. investigating Jun 23, 2025, 02:52 PM UTC

   Some customers may be experiencing errors such as “Socket timeout, unable to connect to server” starting from 14:08 UTC. Our team is actively investigating a potential performance degradation and will provide updates as soon as more information becomes available.

2. identified Jun 23, 2025, 04:13 PM UTC

   The issue has been identified. Our team is currently working on implementing a fix.

3. monitoring Jun 23, 2025, 05:58 PM UTC

   A fix has been implemented, and we are currently monitoring the system to ensure everything is functioning as expected.

4. resolved Jun 23, 2025, 06:01 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 15, 2025, 12:55 PM UTC· resolved May 15, 2025, 01:17 PM UTC

1. 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

2. identified May 15, 2025, 01:03 PM UTC

   Issue identified. We are working on restoring the service.

3. 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

4. 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.

5. 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.

Read the full incident report →

Started Mar 31, 2025, 02:43 PM UTC· resolved Apr 01, 2025, 05:52 PM UTC

1. identified Mar 31, 2025, 02:43 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 09:30 UTC. The team is working on investigating the problem. We apologize for any inconvenience this may have caused and appreciate your understanding.

2. identified Mar 31, 2025, 08:49 PM UTC

   Update. Work in progress - The team is actively working on fixing the issue. At this time, the unavailability of the API is affecting less than 0.01% of the traffic. We apologize for any inconvenience this may have caused and appreciate your understanding.

3. resolved Apr 01, 2025, 05:52 PM UTC

   We want to inform you that the issue affecting the availability of the API service was identified and resolved at 13:00 UTC on April 1st. 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 Apr 08, 2025, 12:08 PM UTC

   **Incident summary**: between March 31, 2025, 09:30 UTC and April 1, 2025, 13:00 UTC, Salt Edge experienced a partial outage affecting the Account Information API and Payments Initiation API. **Root cause**: due to high I/O load on the source database server, the AIS & PIS APIs experienced performance degradation. This led to slower operations and delayed responses for Users. **Resolution**: the server role was switched to a healthy replica, and the problematic server was removed from Production and replaced with new hardware. **Action Points**: * Implement I/O performance alerting * Plan and gradually implement high availability for the PostgreSQL cluster

Read the full incident report →

Started Jan 31, 2025, 03:42 PM UTC· resolved Jan 31, 2025, 04:01 PM UTC

1. resolved Jan 31, 2025, 04:15 PM UTC

   During 15:42 - 15:44 UTC and 15:53 - 16:01 UTC our servers encountered an error, resulting in partial unavailability of our API. We are pleased to inform you that the partial outage has already been resolved. Thank you for your patience and understanding. We apologize for the inconvenience.

Read the full incident report →