Sep <var data-var='date'>29</var>, <var data-var='time'>11:36</var> UTC Resolved - 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.

Service disruption due to upstream provider routing issues

Aug <var data-var='date'>21</var>, <var data-var='time'>09:57</var> UTC Resolved - 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. Aug <var data-var='date'>21</var>, <var data-var='time'>09:46</var> UTC Monitoring - 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. Aug <var data-var='date'>21</var>, <var data-var='time'>09:45</var> UTC Identified - 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. Aug <var data-var='date'>21</var>, <var data-var='time'>09:41</var> UTC Investigating - 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:27 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.

Service Unavailability Due to Data Center Network Issue

Jul <var data-var='date'>28</var>, <var data-var='time'>12:47</var> UTC Resolved - 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. Jul <var data-var='date'>28</var>, <var data-var='time'>12:43</var> UTC Monitoring - 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. Jul <var data-var='date'>28</var>, <var data-var='time'>12:43</var> UTC Identified - 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. Jul <var data-var='date'>28</var>, <var data-var='time'>12:35</var> UTC Investigating - 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.

Open Banking Gateway - Major Outage

May <var data-var='date'>22</var>, <var data-var='time'>06:30</var> UTC Completed - The scheduled maintenance has been completed. May <var data-var='date'>22</var>, <var data-var='time'>05:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'>21</var>, <var data-var='time'>15:41</var> UTC Scheduled - We are performing maintenance to mitigate the root cause of the two recent incidents.

Open Banking Gateway Maintenance

May <var data-var='date'>21</var>, <var data-var='time'>15:23</var> UTC Resolved - The services are now operating normally. Our team continues to monitor the system to ensure stability. Incident duration: From May 21st, 12:23 in UTC Until May 21st, 13:32 in UTC Maintenance work will be scheduled to further mitigate the issue in about 12 hours, and an announcement about it will be published shortly. A detailed postmortem containing all relevant information will also be published. We appreciate your patience and understanding. May <var data-var='date'>21</var>, <var data-var='time'>13:38</var> UTC Monitoring - 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. We will confirm once the incident is fully resolved. May <var data-var='date'>21</var>, <var data-var='time'>13:02</var> UTC Identified - 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. May <var data-var='date'>21</var>, <var data-var='time'>13:00</var> UTC Update - We are continuing to investigate this issue. May <var data-var='date'>21</var>, <var data-var='time'>12:44</var> UTC Investigating - We are currently investigating an issue affecting Open Banking Gateway. Customers may experience failed requests. The issue started at approximately May 21st, 12:23 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.

May <var data-var='date'>19</var>, <var data-var='time'>12:11</var> UTC Resolved - 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. May <var data-var='date'>19</var>, <var data-var='time'>12:08</var> UTC Identified - 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. May <var data-var='date'>19</var>, <var data-var='time'>12:03</var> UTC Investigating - 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.

Open Banking Gateway - Partial Outage

Mar <var data-var='date'>26</var>, <var data-var='time'>14:14</var> UTC Resolved - 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. Mar <var data-var='date'>26</var>, <var data-var='time'>13:42</var> UTC Identified - 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. Mar <var data-var='date'>26</var>, <var data-var='time'>12:09</var> UTC Investigating - 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.

Unavailability of the Payments API for Partners

Mar <var data-var='date'>10</var>, <var data-var='time'>13:29</var> UTC Resolved - 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. Mar <var data-var='date'>10</var>, <var data-var='time'>13:07</var> UTC Identified - 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. Mar <var data-var='date'>10</var>, <var data-var='time'>13:04</var> UTC Investigating - 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.

Partial unavailability of the Payments API

Feb <var data-var='date'>23</var>, <var data-var='time'>13:01</var> UTC Resolved - 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. Feb <var data-var='date'>23</var>, <var data-var='time'>12:56</var> UTC Identified - The issue has been found and fixed. Feb <var data-var='date'>23</var>, <var data-var='time'>12:31</var> UTC Investigating - We are currently investigating this issue.

Major Outage

Jan <var data-var='date'>11</var>, <var data-var='time'>21:10</var> UTC Resolved - Incident was resolved. All the details and post-mortem will be provided on business hours. Jan <var data-var='date'>11</var>, <var data-var='time'>19:25</var> UTC Update - The problem with notifications has been resolved. However, the issue now lies with slow payment processing. Our team is still investigating this. Jan <var data-var='date'>11</var>, <var data-var='time'>18:01</var> UTC Identified - 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.

Malfunction in payment confirmation triggers.

Dec <var data-var='date'>30</var>, <var data-var='time'>10:30</var> UTC Resolved - 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.

Open Banking Gateway API intermittent errors

Jun <var data-var='date'>23</var>, <var data-var='time'>18:01</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>23</var>, <var data-var='time'>17:58</var> UTC Monitoring - A fix has been implemented, and we are currently monitoring the system to ensure everything is functioning as expected. Jun <var data-var='date'>23</var>, <var data-var='time'>16:13</var> UTC Identified - The issue has been identified. Our team is currently working on implementing a fix. Jun <var data-var='date'>23</var>, <var data-var='time'>14:52</var> UTC Investigating - 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.

Data Enrichment: elevated error rates / performance degradation

May <var data-var='date'>15</var>, <var data-var='time'>13:17</var> UTC Resolved - 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. May <var data-var='date'>15</var>, <var data-var='time'>13:12</var> UTC Update - The issue regarding Account Information API, Payments API and Partners API has been resolved at 16:12 GTM +3 May <var data-var='date'>15</var>, <var data-var='time'>13:03</var> UTC Identified - Issue identified. We are working on restoring the service. May <var data-var='date'>15</var>, <var data-var='time'>12:55</var> UTC Investigating - 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

Temporary service disruptions

Apr <var data-var='date'> 1</var>, <var data-var='time'>17:52</var> UTC Resolved - 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. Mar <var data-var='date'>31</var>, <var data-var='time'>20:49</var> UTC Update - 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. Mar <var data-var='date'>31</var>, <var data-var='time'>14:43</var> UTC Identified - 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.

Partial unavailability of the API

Jan <var data-var='date'>31</var>, <var data-var='time'>16:15</var> UTC Resolved - 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.

Partial unavailability of APIs

Jan <var data-var='date'>25</var>, <var data-var='time'>18:41</var> UTC Resolved - The issue has been resolved. Jan <var data-var='date'>25</var>, <var data-var='time'>18:05</var> UTC Identified - The affected service is Callbacks, the problem is identified, and we’re doing our best to start sending callbacks properly as soon as possible Jan <var data-var='date'>25</var>, <var data-var='time'>17:59</var> UTC Investigating - We experienced a temporary issue affecting the availability of our services, and some customers may have encountered HTTP 500 Internal Server Errors during the following timeframe: Downtime start: 25-01-2025 12:33:46 UTC Downtime end: 25-01-2025 12:37:46 UTC The problem has been identified and resolved, and all systems are now functioning normally. However, users may still be unable to proceed to the final stage. Please refresh the page to ensure the issue is fully resolved before continuing.

Jan <var data-var='date'>25</var>, <var data-var='time'>14:00</var> UTC Resolved - We experienced a temporary issue affecting the availability of our services, and some customers may have encountered HTTP 500 Internal Server Errors during the following timeframe: Downtime start: 25-01-2025 12:33:46 UTC Downtime end: 25-01-2025 12:37:46 UTC The problem has been identified and resolved, and all systems are now functioning normally.

Nov <var data-var='date'>11</var>, <var data-var='time'>05:30</var> UTC Completed - The scheduled maintenance has been completed. Nov <var data-var='date'>11</var>, <var data-var='time'>04:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct <var data-var='date'>30</var>, <var data-var='time'>13:40</var> UTC Update - We will be undergoing scheduled maintenance during this time. Oct <var data-var='date'>30</var>, <var data-var='time'>13:38</var> UTC Scheduled - Scheduled software updates will be performed on third-party network equipment. Reason: these updates are aimed at improving the reliability and security of our network connections. During this process, you may experience brief interruptions in access to our services, resulting in temporary unavailability notifications. We apologise for any inconvenience this may cause and appreciate your patience and understanding.

OBG, PSD2 Compliance & Data Enrichment services planned maintenance

Nov <var data-var='date'> 8</var>, <var data-var='time'>15:45</var> UTC Resolved - This incident has been resolved. Nov <var data-var='date'> 8</var>, <var data-var='time'>15:44</var> UTC Update - We are pleased to inform you that the partial outage has been resolved at 15:43 UTC, and all services are now back on track. Thank you for your patience and understanding. We apologize for the inconvenience. Nov <var data-var='date'> 8</var>, <var data-var='time'>15:40</var> UTC Investigating - At 15:26 UTC, one of our cache servers encountered an error, resulting in partial unavailability of our API. Our team is actively working to resolve the issue. We apologize for any inconvenience this may have caused and appreciate your understanding.

Sep <var data-var='date'> 3</var>, <var data-var='time'>10:46</var> UTC Resolved - We are pleased to inform you that the partial outage has been resolved at 10:42 UTC, and all services are now back on track. Thank you for your patience and understanding. We apologize for the inconvenience. Sep <var data-var='date'> 3</var>, <var data-var='time'>08:20</var> UTC Identified - The issue has been identified and our team is actively working on it. Sep <var data-var='date'> 3</var>, <var data-var='time'>02:20</var> UTC Investigating - At 02:20 UTC, one of our databases encountered an error, resulting in partial unavailability of our API. Our team is actively working to resolve the issue. We apologize for any inconvenience this may have caused and appreciate your understanding.

Partial unavailability of Partners API

Aug <var data-var='date'>26</var>, <var data-var='time'>06:30</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>26</var>, <var data-var='time'>06:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>19</var>, <var data-var='time'>12:13</var> UTC Scheduled - Salt Edge will be undergoing scheduled maintenance during this time and you may experience intermittent 500 errors. Reason: maintenance on application level We apologize for any inconvenience this may cause and appreciate your patience and understanding.

Open Banking Gateway scheduled maintenance

Aug <var data-var='date'> 8</var>, <var data-var='time'>11:30</var> UTC Resolved - Identified - The issue has been identified and our team is actively working on it. Investigating - At 11:29 UTC we started encountering partial unavailability of the SCA solution. Resolved - We are pleased to inform you that the partial outage has been resolved at 14:21 UTC, and all services are now back on track. Thank you for your patience and understanding. We apologize for the inconvenience. We apologize for any inconvenience this may have caused and appreciate your understanding.

SCA partial unavailability

Aug <var data-var='date'> 7</var>, <var data-var='time'>14:36</var> UTC Resolved - We are pleased to inform you that the partial outage has been resolved at 14:35 UTC, and all services are now back on track. Thank you for your patience and understanding. We apologize for the inconvenience. Aug <var data-var='date'> 7</var>, <var data-var='time'>14:30</var> UTC Identified - The issue has been identified and our team is actively working on it. Aug <var data-var='date'> 7</var>, <var data-var='time'>14:11</var> UTC Investigating - At 13:53 UTC we started encountering partial unavailability of the Client Dashboard and other services. Our team is actively working to resolve the issue. We apologize for any inconvenience this may have caused and appreciate your understanding.

Partial unavailability

Jul <var data-var='date'>31</var>, <var data-var='time'>20:11</var> UTC Resolved - We are pleased to inform you that the partial outage has been resolved at 19:57 UTC, and all services are now back on track. Thank you for your patience and understanding. We apologize for the inconvenience. Jul <var data-var='date'>31</var>, <var data-var='time'>19:48</var> UTC Update - We are continuing to work on the fix. The restoration has reached 51% Jul <var data-var='date'>31</var>, <var data-var='time'>13:11</var> UTC Identified - The issue has been identified and a fix is being implemented. Jul <var data-var='date'>31</var>, <var data-var='time'>12:35</var> UTC Update - We are continuing to investigate this issue. Jul <var data-var='date'>31</var>, <var data-var='time'>12:07</var> UTC Investigating - At 11:26:38 UTC, one of our databases encountered an error, resulting in partial unavailability of our API. Our team is actively working to resolve the issue. We apologize for any inconvenience this may have caused and appreciate your understanding.

Jul <var data-var='date'>14</var>, <var data-var='time'>08:53</var> UTC Resolved - Our services experienced a temporary outage on July 14th, from 08:53 UTC to 09:12 UTC, due to a bug in the system kernel. The total downtime was 19 minutes. We apologize for any inconvenience caused and appreciate your understanding.

Is Salt Edge down?

Salt Edge status is UP

Lastest published events

Service disruption due to upstream provider routing issues

Service Unavailability Due to Data Center Network Issue

Open Banking Gateway - Major Outage

Salt Edge Services, Components and Regions

Recent Salt Edge events

Service disruption due to upstream provider routing issues

Service Unavailability Due to Data Center Network Issue

Open Banking Gateway - Major Outage

Open Banking Gateway Maintenance

Open Banking Gateway - Major Outage

Open Banking Gateway - Partial Outage