Solaris experienced a major incident on May 19, 2026 affecting Digital Banking, lasting 3h 23m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 19, 2026, 10:42 AM UTC
We are currently observing an increase in outgoing rejected and decrease incoming SEPA Instant transactions volumes; Issues started since ~ 10:30 CEST. There is no technical issue detected on Solaris side yet it's suspected issue is related to external source. Partner Impact/Customer Impact: For Outgoing SEPA Instant transfers -> Partners would notice increase in declined for outgoing SEPA instant transactions with code AB08. Indicating offline creditors banks. For Incoming SEPA Instant tranfer -> Parnter would decrease in volume of incoming transactions. In case of persistent error messages, Partners are advised to inform Customers of possibility of doing a normal SEPA Credit Transfer as an alternative. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. Relevant Doc: Webhook Events (Instant SEPA Failed): https://docs.solarisgroup.com/api-reference/onboarding/webhooks/#tag/Webhook-events/paths/instant_sepa_credit_transfer_failed/post We apologize for any inconveniences this outage may have caused. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.
- identified May 19, 2026, 12:06 PM UTC
A number of other banks encountering delays in processing SEPA instants Payements, and we are closely monitoring this issue.
- resolved May 19, 2026, 02:06 PM UTC
The rejections involve participants Banks connected to RT1. We would like to confirm that, following monitoring, the outage has been resolved.