Solaris Outage History

Started Aug 15, 2026, 05:26 AM UTC· resolved Aug 18, 2026, 08:15 AM UTC

1. investigating Aug 15, 2026, 05:26 AM UTC

   We are currently observing an increased internal rejections in outgoing and incoming SEPA Instant transactions. The issue is linked to one of our service providers. Partner Impact/Customer Impact: For Outgoing SEPA Instant transfers -> Partners would notice a delay in the settlement of the impacted Outgoing SEPA instant 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 Solaris SE API services. Impacted Endpoints: POST /v1/accounts/{account_id}/transactions/sepa_instant_credit_transfers API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: SEPA Instant Credit Transfers (POST): https://docs.solarisgroup.com/api-reference/digital-banking/sepa-transfers/#tag/SEPA-Instant-Credit-Transfers/paths/~1v1~1accounts~1%7Baccount_id%7D~1transactions~1sepa_instant_credit_transfers/post 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.

2. investigating Aug 15, 2026, 05:52 AM UTC

   We are continuing to investigate this issue.

3. investigating Aug 15, 2026, 07:03 AM UTC

   We are continuing to investigate this issue.

4. identified Aug 15, 2026, 09:43 AM UTC

   The issue has been identified and a fix is being implemented.

5. identified Aug 15, 2026, 10:38 AM UTC

   We are continuing to work on this issue.

6. identified Aug 15, 2026, 10:47 AM UTC

   The provider issue linked to a data-center outage impacting connectivity to the site. https://status.core-backbone.com/

7. identified Aug 15, 2026, 11:09 AM UTC

   In order to prevent any further transactions from being delayed, SEPA Instant transactions have been stopped. Partners are advised to inform customers of the change to a normal SEPA Credit Transfer.

8. identified Aug 15, 2026, 02:34 PM UTC

   The fix is in place, and the outgoing SEPA Instant transactions service has been restored.

9. monitoring Aug 15, 2026, 02:53 PM UTC

   The incoming and outgoing SEPA Instant transactions service has been restored. We are currently monitoring all incoming and outgoing transactions to ensure full service stability. 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.

10. resolved Aug 18, 2026, 08:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Started Aug 05, 2026, 05:35 PM UTC· resolved Aug 05, 2026, 07:37 PM UTC

1. monitoring Aug 05, 2026, 05:35 PM UTC

   We would like to inform you that we have experienced 5XXs API error messages to be returned on multiple API endpoints to our Partners between 18:38 CEST - 19:12 CEST 05.08.2026. In the mean time we are monitoring relevant service to ensure that it's operating within normal levels. Partner Impact: • Partners who initiated calls to Solaris endpoints during outage time would have experienced errors. Customer Impact: • Customers might experienced error messages while attempting different actions on partners side which dependancy on Solaris end-points. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris SE API services. API Reference Documentation: Partners/Customers attempting to use the services associated to the endpoints would have been presented with either generic error messages or specific to each Partner's implementation of the endpoint/s. We will share more details on the error after further investigation is performed. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

2. resolved Aug 05, 2026, 07:37 PM UTC

   The issue was fully resolved. We would like to inform you that we have experienced 5XXs API error messages to be returned on multiple API endpoints to our Partners between 18:38 CEST - 19:12 CEST 05.08.2026. In the mean time we are monitoring relevant service to ensure that it's operating within normal levels. Partner Impact: • Partners who initiated calls to Solaris endpoints during outage time would have experienced errors. Customer Impact: • Customers might experienced error messages while attempting different actions on partners side which dependancy on Solaris end-points. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris SE API services. API Reference Documentation: Partners/Customers attempting to use the services associated to the endpoints would have been presented with either generic error messages or specific to each Partner's implementation of the endpoint/s. We will share more details on the error after further investigation is performed. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

Read the full incident report →

Started Jul 26, 2026, 01:23 PM UTC· resolved Jul 26, 2026, 05:57 PM UTC

1. investigating Jul 26, 2026, 01:23 PM UTC

   We are currently observing an increased rejections in outgoing and incoming SEPA Instant transactions. The issue is linked to our provider and they have been engaged to fix the issue. Partner Impact/Customer Impact: For Outgoing SEPA Instant transfers -> Partners would notice a delay in the settlement of the impacted Outgoing SEPA instant 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 Solaris SE API services. Impacted Endpoints: POST /v1/accounts/{account_id}/transactions/sepa_instant_credit_transfers API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: SEPA Instant Credit Transfers (POST): https://docs.solarisgroup.com/api-reference/digital-banking/sepa-transfers/#tag/SEPA-Instant-Credit-Transfers/paths/~1v1~1accounts~1%7Baccount_id%7D~1transactions~1sepa_instant_credit_transfers/post 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.

2. resolved Jul 26, 2026, 05:57 PM UTC

   The issue with outgoing & incoming SEPA Instant transactions was fully resolved. Partner / Customer Impact: Outgoing SEPA Instant Transfers: During the incident, Partners may have experienced delays in the settlement of impacted outgoing SEPA Instant transactions. Disclaimer: Actual customer impact may vary depending on each Partner's specific implementation of Solaris API services. Impacted Endpoints: POST /v1/accounts/{account_id}/transactions/sepa_instant_credit_transfers API Reference Documentation: To understand more about the impacted endpoints, please review the following public documentation: SEPA Instant Credit Transfers (POST): https://docs.solarisgroup.com/api-reference/digital-banking/sepa-transfers/#tag/SEPA-Instant-Credit-Transfers/paths/~1v1~1accounts~1%7Baccount_id%7D~1transactions~1sepa_instant_credit_transfers/post 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.

Read the full incident report →

Started Jun 18, 2026, 03:41 PM UTC· resolved Jun 24, 2026, 09:26 AM UTC

1. identified Jun 18, 2026, 03:41 PM UTC

   Dear Partners, We are experiencing a delay in card delivery. Partner & Customer Impact: • Customers might experience 2-3 days delays with physical Visa cards deliveries. Impacted Services: • Physical Visa Card Production In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

2. monitoring Jun 19, 2026, 03:34 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Jun 24, 2026, 09:26 AM UTC

   All impact phyiscal cards were produced and shipped to couriers. We apologize for any inconveniences this delay 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.

Read the full incident report →

Started May 24, 2026, 09:22 PM UTC· resolved May 24, 2026, 10:41 PM UTC

1. identified May 24, 2026, 09:22 PM UTC

   We are experiencing 5XXs API error messages to be returned on multiple API endpoints to our Partners starting 23:00 CEST. The issue has been mitigated as of 23:17 CEST. Partner Impact: • Partners/Customers attempting to process transactions would have experienced delays 5XXs errors while calling the below API Endpoints: • GET /v1/persons/{person_id)/accounts/{account_id} • GET /v1/accounts/{account_id)/balance • GET /v1/persons/{person_id)/accounts Customer Impact: Customers might experienced error messages while attempting to retrieve transaction information and while fetching account balance Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris SE API services. API Reference Documentation: Partners/Customers attempting to use the services associated to the endpoints would have been presented with either generic error messages or specific to each Partner's implementation of the endpoint/s. We will share more details on the error after further investigation is performed. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

2. resolved May 24, 2026, 10:41 PM UTC

   The incident identified to be impacting multiple API endpoints intermittently between 23:00 CEST and 23:17 CEST on 24.05.2026, resulting in elevated API error rates has been resolved. Services have been monitored in order to ensure that all operations are running within normal service levels. Partner/Customer Impact Resolution: 5XX API error messages are no longer returned from multiple API endpoints across all services and customers will no longer receive error messages in the partner mobile or web applications. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris SE API services. The incident has been resolved. No further updates would be provided 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.

Read the full incident report →

Started May 19, 2026, 08:00 AM UTC· resolved May 19, 2026, 12:54 PM UTC

1. investigating May 19, 2026, 08:00 AM UTC

   A partial outage for Multiple Cards services have been identified for creating Cards and associated Card Lifecycle Status changes. Partner Impact: • POST /v1/cards/{id}/virtual_card_requests is returning increased 5xx errors • POST /v1/cards/{card_id}/block returning increased 5xx errors • POST /v1/cards/{card_id}/unblock returning increased 5xx errors (not an exhaustive list) Customer Impact: • Customers attempting to perform card lifecycle operations or obtaining card CVC details may be presented with a generic error message intermittently, in the mobile or web applications • Customers attempting to create cards will be presented with 5XXs errors • Customers will be unable to Block and Unblock cards Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris SE API services. Impacted endpoints: • POST /v1/cards/{id}/virtual_card_requests • POST /v1/cards/{card_id}/block • POST /v1/cards/{card_id}/unblock (not an exhaustive list) API Reference Documentation: To understand more about the impacted endpoints please read the following public documentation: • https://docs.solarisgroup.com/api-reference/digital-banking/cards/#tag/Cards-servicing/paths/~1v1~1cards~1{id}~1virtual_card_requests/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.

2. identified May 19, 2026, 08:53 AM UTC

   A partial outage for Multiple Cards services have been identified for creating Cards and associated card lifecycle status changes related to cards processing provider. Partner Impact: Anticipated failures related to all card creation & servicing end-points. Customer Impact: Anticipated failures related to all cards servcing operations. API Reference Documentation: To understand more about the impacted endpoints please read the following public documentation: • https://docs.solarisgroup.com/api-reference/digital-banking/cards 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.

3. monitoring May 19, 2026, 09:01 AM UTC

   All affected cards services should be fully recovered and operational within normal levels by 10:20 CEST.

4. resolved May 19, 2026, 12:54 PM UTC

   We would like to confirm that, following extensive monitoring, the outage has been fully resolved. A partial outage for Multiple cards services have been identified for creating cards and associated card lifecycle status changes related to cards processing provider. Partner Impact: Anticipated failures related to all cards creation & servicing end-points. Customer Impact: Anticipated failures related to all cards servcing operations. API Reference Documentation: To understand more about the impacted endpoints please read the following public documentation: • https://docs.solarisgroup.com/api-reference/digital-banking/cards 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.

Read the full incident report →

Started May 05, 2026, 09:45 PM UTC· resolved May 06, 2026, 07:28 AM UTC

1. investigating May 05, 2026, 09:45 PM UTC

   Due to an active outage on the Top Level Domain (.de) provider Denic, it is anticipated that partners may experience service disruption related to the reachability of Solaris API endpoints in the production environment (api.solarisbank.de). We will keep you informed as we continue to monitor the provider updates. API Reference Documentation: To understand more about the impacted endpoints please read the following public documentation: • https://docs.solarisgroup.com/api-reference/ We apologize for any inconveniences this planned maintenance may cause. Regular scheduled maintenance activities are required in order to maintain a high standard for the quality of services offered by Solaris. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

2. resolved May 06, 2026, 07:28 AM UTC

   We are pleased to confirm that provider issue was resolved by 12:20; Service operating within normal levels.

Read the full incident report →

Started Apr 18, 2026, 08:42 PM UTC· resolved Apr 19, 2026, 08:36 AM UTC

1. investigating Apr 18, 2026, 08:42 PM UTC

   We encountered an ongoing issue with Incoming & Outgoing SEPA Instant transactions, resulting in unsuccessful transactions. Partner / Customer Impact: Incoming & Outgoing SEPA Instant Transfers: During the incident, Partners may have experienced delays in the settlement of impacted Incoming & Outgoing SEPA Instant transactions. Alternative Actions: In the event of lingering external error messages, Partners are advised to inform customers of the possibility of initiating a standard SEPA Credit Transfer as an alternative. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. Impacted Endpoints: • POST /v1/accounts/{account_id}/transactions/sepa_instant_credit_transfers API Reference Documentation: To understand more about the impacted endpoint(s), please read the following public documentation: • https://docs.solarisgroup.com/api-reference/digital-banking/sepa-transfers/#tag/SEPA-Instant-Credit-Transfers/paths/~1v1~1accounts~1%7Baccount_id%7D~1transactions~1sepa_instant_credit_transfers/post • https://docs.solarisgroup.com/api-reference/onboarding/webhooks/#tag/Webhook-events/paths/instant_sepa_credit_transfer_failed/post We apologize for any inconvenience this outage may have caused. Should you have any questions or concerns, please contact us by sending an email to [email protected] or through our dedicated ticketing platform.

2. monitoring Apr 18, 2026, 10:10 PM UTC

   The issue impacting Incoming & Outgoing SEPA Instant transactions has been mitigated. Service stability has returned to normal levels, and our engineering team is monitoring the system closely to ensure continued performance. Partner / Customer Impact: Incoming & Outgoing SEPA Instant Transfers: During the incident, Partners may have experienced delays in the settlement of impacted Incoming & Outgoing SEPA Instant transactions. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. Impacted Endpoints: • POST /v1/accounts/{account_id}/transactions/sepa_instant_credit_transfers API Reference Documentation: To understand more about the impacted endpoint(s), please read the following public documentation: • https://docs.solarisgroup.com/api-reference/digital-banking/sepa-transfers/#tag/SEPA-Instant-Credit-Transfers/paths/~1v1~1accounts~1%7Baccount_id%7D~1transactions~1sepa_instant_credit_transfers/post • https://docs.solarisgroup.com/api-reference/onboarding/webhooks/#tag/Webhook-events/paths/instant_sepa_credit_transfer_failed/post We apologize for any inconvenience this outage may have caused. Should you have any questions or concerns, please contact us by sending an email to [email protected] or through our dedicated ticketing platform.

3. resolved Apr 19, 2026, 08:36 AM UTC

   The issue impacting Incoming & Outgoing SEPA Instant transactions was fully resolved at 05:34 CEST, 19/04/2026 .

Read the full incident report →

Started Mar 09, 2026, 02:16 PM UTC· resolved Mar 09, 2026, 04:23 PM UTC

1. identified Mar 09, 2026, 02:16 PM UTC

   Issue Summary: We have identified an issue affecting Scheduled Transfers initiated with the debtor name exceeding the character limit supported by the underlying service. The failures are specifically related to debtor names exceeding the 70-character limit supported by the SEPA scheme. Resolution & Action Required: Customer Impact: Affected customers might notice that Standing orders weren't executed on time and to ensure successful processing, partners and customers are advised to manually re-submit or retry any affected transactions associated with unexecuted scheduled orders. Partner Impact - This issue specifically affects transactions involving sole proprietors or businesses with extended legal names (over 70 characters). By identifying this as a SEPA scheme limitation, partners can verify that customers with standard name lengths remain unaffected. Legacy endpoints are not impacted by this issue. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. Impacted endpoints: • https://docs.solarisgroup.com/guides/digital-banking/sepa-transfers/scheduled-transfer#api-reference-documentation API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/guides/digital-banking/sepa-transfers/scheduled-transfer In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

2. resolved Mar 09, 2026, 04:23 PM UTC

   We have successfully deployed a fix to resolve the issues affecting Scheduled Transfers initiated with the debtor name exceeding the character limit supported by the underlying service.The failures were specifically related to debtor names exceeding the 70-character limit supported by the SEPA scheme. Resolution & Action Required: Customer Impact: Affected customers might notice that Standing orders weren't executed on time and to ensure successful processing, partners and customers are advised to manually re-submit or retry any affected transactions associated with unexecuted scheduled orders. Partner Impact - This issue specifically affects transactions involving sole proprietors or businesses with extended legal names (over 70 characters). By identifying this as a SEPA scheme limitation, partners can verify that customers with standard name lengths remain unaffected. Legacy endpoints are not impacted by this issue. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. Impacted endpoints: • https://docs.solarisgroup.com/guides/digital-banking/sepa-transfers/scheduled-transfer#api-reference-documentation API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/guides/digital-banking/sepa-transfers/scheduled-transfer In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

Read the full incident report →

Started Dec 22, 2025, 03:58 PM UTC· resolved Dec 22, 2025, 03:58 PM UTC

1. resolved Dec 22, 2025, 03:58 PM UTC

   We would like to inform you of a recent issue affecting the VideoIdent flow via our service provider IDnow . This is not a service outage but requires a partner action to ensure optimal user experience. Our service provider, IDnow, has notified us of an issue regarding their Android SDK that causes reduced image quality, specifically a green tinge, on certain Android versions and devices. To address this, IDnow has released a fix for the issue and updated the VideoIdent app in the Google Play Store. Partner Action Required : It is strongly recommended that all partners using the Android SDK update to the latest version to ensure image clarity. https://github.com/idnow/de.idnow.android/releases End users connecting to these services via the standalone app must also ensure they are using the latest version of the VideoIdent app from the Google Play Store. Impact : End users on certain Android devices may experience degraded image quality (green tint) during the VideoIdent process. This may impact the visual verification steps required for a successful identification. Disclaimer: -This issue specifically affects the Android SDK on certain device configurations. -The iOS SDK is not affected. -VideoIdent and eSign Web flows are not affected. -AutoIdent and all other products from our service provider remain unaffected. If you have any questions or require support, please contact us at [email protected] or through our dedicated ticketing platform.

Read the full incident report →

Started Dec 05, 2025, 09:50 AM UTC· resolved Dec 05, 2025, 10:15 AM UTC

1. monitoring Dec 05, 2025, 09:50 AM UTC

   Due to an unplanned outage for one of our service providers, Solaris experienced increase response "VERIFICATION_NOT_POSSIBLE" of verification of Payee for Normal SEPA / SEPA instant transactions between 09:50 CET and 10:13 CET. The systems and services are currently stable and the impact is no longer visible, however we are working together with our Instant Payment provider and are closely monitoring the situation. Partner Impact/Customer Impact: • There was no direct impact or errors encountered during incident time however customers received response during above mentioned times that verification isn't possible yet customers were still able to confirm transactions and proceed with transfers. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. Impacted Endpoints: • POST/v1/verifications_of_payee API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/api-reference/digital-banking/sepa-transfers/verification-of-payee/paths/~1v1~1verifications_of_payee/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.

2. resolved Dec 05, 2025, 10:15 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 03, 2025, 02:57 PM UTC· resolved Dec 03, 2025, 05:08 PM UTC

1. identified Dec 03, 2025, 02:57 PM UTC

   An unplanned partial outage affecting person identification via IDnow services has been identified. We are working together with our vendor to restore the impacted services as soon as possible. Partner Impact: • IDnow identification attempts remain stuck in ‘Pending’ state as observed in WebUI and API Customer Impact: • Customers initiating new IDnow identifications may experience delays or interruptions in completing the process. API Reference Documentation: To understand more about the impacted services, please read the following public documentation: • https://docs.solarisgroup.com/guides/kyc/videoident/#video-identification-via-idnow We apologize for any inconvenience this outage may have caused. In case of any questions or concerns, please contact us by sending an email to [email protected] or through our dedicated ticketing platform.

2. resolved Dec 03, 2025, 05:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 02, 2025, 11:37 AM UTC· resolved Dec 02, 2025, 01:12 PM UTC

1. monitoring Dec 02, 2025, 11:37 AM UTC

   Summary: We identified an issue earlier today that caused all card transactions to fail between 11:07 CET - 11:58 CET. The service is restored within normal levels, and card transactions are processing normally. Our team is continuing to investigate the root cause to prevent similar issues in the future. All services are functioning normally. No further impact is expected. • Partner & Customer Impact: Partners may receive reports of issues related to failed Card Transactions Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/api-reference/digital-banking/cards/card-transactions In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

2. resolved Dec 02, 2025, 01:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 21, 2025, 09:11 AM UTC· resolved Nov 21, 2025, 09:11 AM UTC

1. resolved Nov 21, 2025, 09:11 AM UTC

   The unplanned service disruption affecting our Sandbox environment has been resolved. The systems and services are currently stable and the impact is no longer visible. Our engineering teams have corrected the infrastructure configuration issue and verified that all services are operating normally. Partner Impact/Customer Impact: • During the incident, Partners experienced a high rate of 5xx server errors and connection failures when accessing the Sandbox API. • Testing capabilities for Sandbox API services were temporarily blocked or experienced significant instability. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank Sandbox API services. We apologize for any inconveniences this outage may have caused to your testing and development activities. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

Read the full incident report →

Started Nov 19, 2025, 05:15 PM UTC· resolved Nov 19, 2025, 07:01 PM UTC

1. investigating Nov 19, 2025, 05:15 PM UTC

   Due to an unplanned partial outage at our service provider, a short latency spike has impacted a limited number of outgoing SEPA Instant transactions between 16:50 CET and 17:20 CET. The systems and services are currently stable and the impact is no longer visible, however we are working together with our Instant Payment provider and are closely monitoring the situation. Partner Impact/Customer Impact: • For Outgoing SEPA Instant transfers -> Partners would notice a delay in the settlement of the impacted Outgoing SEPA instant 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. Impacted Endpoints: • POST /v1/accounts/{account_id}/transactions/sepa_instant_credit_transfers API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/api-reference/digital-banking/sepa-transfers/#tag/SEPA-Instant-Credit-Transfers/paths/~1v1~1accounts~1%7Baccount_id%7D~1transactions~1sepa_instant_credit_transfers/post • 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.

2. resolved Nov 19, 2025, 07:01 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2025, 01:11 PM UTC· resolved Nov 18, 2025, 04:21 PM UTC

1. investigating Nov 18, 2025, 01:11 PM UTC

   We would like to inform you about an outage related to one of our a third-party providers due to the dependency on the provider. The following services which linked to business KYC service are affected. Expected Partner Impact: API calls for the following commercial registrations endpoints are expected to face failure and return 5xx error messages • GET /v1/commercial_registrations/search_by_name • GET /v1/commercial_registrations/find Expected Customer Impact: There may be minor delays in the business onboarding process. Our BKYC specialists might need to manually retrieve business information from the government’s commercial register during this time. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/api-reference/onboarding/businesses/#tag/Business-Registrations/paths/~1v1~1commercial_registrations~1find/get • https://docs.solarisgroup.com/api-reference/onboarding/businesses/#tag/Business-Registrations/paths/~1v1~1commercial_registrations~1search_by_name/get We apologize for any inconveniences this planned maintenance may cause. Regular scheduled maintenance activities are required in order to maintain a high standard for the quality of services offered by Solarisbank. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

2. resolved Nov 18, 2025, 04:21 PM UTC

   A fix has been implemented by provider for an outage related to one of our a third-party providers due to the dependency on the provider. The following services which linked to business KYC service are affected. Expected Partner Impact: API calls for the following commercial registrations endpoints are expected to face failure and return 5xx error messages • GET /v1/commercial_registrations/search_by_name • GET /v1/commercial_registrations/find Expected Customer Impact: There may be minor delays in the business onboarding process. Our BKYC specialists might need to manually retrieve business information from the government’s commercial register during this time. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/api-reference/onboarding/businesses/#tag/Business-Registrations/paths/~1v1~1commercial_registrations~1find/get • https://docs.solarisgroup.com/api-reference/onboarding/businesses/#tag/Business-Registrations/paths/~1v1~1commercial_registrations~1search_by_name/get We apologize for any inconveniences this planned maintenance may cause. Regular scheduled maintenance activities are required in order to maintain a high standard for the quality of services offered by Solarisbank. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

Read the full incident report →

Started Nov 10, 2025, 03:56 PM UTC· resolved Nov 10, 2025, 05:25 PM UTC

1. monitoring Nov 10, 2025, 03:56 PM UTC

   We would like to inform you that we were experiencing service disruption for IDnow Identification Service due to a provider outage where Identity API endpoint returned errors for limited number of customers. A fix was implemented and service should be working within normal levels. Partner Impact: • Partners will experience 5XX errors for Identity services. Customer Impact: • Customers would see errors while using services which is related to Identity services. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. Impacted endpoints: PATCH /v1/persons/:person_id/identifications/:id/request API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/guides/kyc/videoident/#video-identification-via-idnow In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

2. resolved Nov 10, 2025, 05:25 PM UTC

   Our monitoring for the provider fix shows that the identification service via IDnow should now be operating within normal levels. A limited number of users were affected, but the identification process should be successful upon their retrial. Partner Impact: • Partners will experience 5XX errors for Identity services. Customer Impact: • Customers might have observed errors while using services which is related to Identity services. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. Impacted endpoints: PATCH /v1/persons/:person_id/identifications/:id/request API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/guides/kyc/videoident/#video-identification-via-idnow In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

Read the full incident report →

Started Oct 29, 2025, 11:37 AM UTC· resolved Oct 29, 2025, 01:01 PM UTC

1. investigating Oct 29, 2025, 11:37 AM UTC

   An unplanned partial outage has been observed impacting the person creation resulting in elevated API error rates has been mitigated. Services have been restored and are being monitored in order to ensure all operations are running within normal service levels. Partner Impact: Partners may encounter increased 5XX error responses while calling the following API endpoint: POST /v1/persons Customer Impact: End users may experience error messages during the onboarding process, potentially affecting the creation of new person resources. Disclaimer: Actual customer impact may vary depending on each partner's implementation of Solaris SE API services. API Reference Documentation: For more information about the impacted endpoint, please refer to the following documentation: https://docs.solarisgroup.com/api-reference/onboarding/persons/persons/paths/~1v1~1persons/post We apologize for any inconvenience this outage may have caused. If you have any questions or concerns, please contact us via email at [email protected] or through our dedicated ticketing platform.

2. resolved Oct 29, 2025, 01:01 PM UTC

   An unplanned partial outage impacting person creation, which resulted in elevated API error rates, has been resolved, and services are now running within normal service levels. Partner Impact: The issue causing increased 5XX error responses for the following API endpoint has been resolved. POST /v1/persons Customer Impact: End users will not experience error messages during the onboarding process or while creating new person resources. Disclaimer: Actual customer impact may vary depending on each partner's implementation of Solaris SE API services. API Reference Documentation: For more information about the impacted endpoint, please refer to the following documentation: https://docs.solarisgroup.com/api-reference/onboarding/persons/persons/paths/~1v1~1persons/post We apologize for any inconvenience this outage may have caused. The incident has been resolved. No further updates will be provided. If you have any questions or concerns, please contact us via email at [email protected] or through our dedicated ticketing platform.

Read the full incident report →

Started Oct 20, 2025, 10:40 AM UTC· resolved Oct 20, 2025, 11:57 AM UTC

1. monitoring Oct 20, 2025, 10:40 AM UTC

   We have observed unplanned partial outage for Terms and Conditions Event endpoint starting 20/10/2025 between 11:26 CET and 12:21 CET. Service are running within normal service level and are under monitoring Partner Impact: 5XXs errors while calling the below API Endpoints • POST /v1/terms_and_conditions_events Customer Impact: Customers might experienced error messages and affected on-boarding flow. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris SE API services. API Reference Documentation: To understand more about the impacted endpoints please read the following public documentation: • https://docs.solarisgroup.com/api-reference/onboarding/compliance/terms-and-conditions-events 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.

2. resolved Oct 20, 2025, 11:57 AM UTC

   We have observed unplanned partial outage for Terms and Conditions Event endpoint starting 20/10/2025 between 11:26 CET and 12:21 CET. Service are running within normal service level and stands resolved. Partner Impact: 5XXs errors while calling the below API Endpoints • POST /v1/terms_and_conditions_events Customer Impact: Customers might experienced error messages and affected on-boarding flow. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris SE API services. API Reference Documentation: To understand more about the impacted endpoints please read the following public documentation: • https://docs.solarisgroup.com/api-reference/onboarding/compliance/terms-and-conditions-events 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.

Read the full incident report →

Started Sep 25, 2025, 01:28 PM UTC· resolved Sep 25, 2025, 01:28 PM UTC

1. resolved Sep 25, 2025, 01:28 PM UTC

   We would like to inform you of a recent issue affecting the VideoIdent flow via our service provider. This is not a service outage but requires a partner action to ensure optimal user experience. Our service provider, IDnow, has observed an increase in audio quality issues during VideoIdent and eSign calls originating from iOS mobile devices using the IDnow app or SDK, a problem stemming from the recent Apple iOS 26 release. To address these audio issues, IDnow has released a hotfix version of their SDK and updated the IDnow app in the Apple App Store. Partner Action Required: It is crucial that all partners using the VideoIdent SDK update to the latest version immediately. https://github.com/idnow/de.idnow.ios/releases End users connecting to these services must also ensure they are using the latest version of the IDnow app from the Apple App Store. Impact End users on devices running iOS 26 and newer may experience degraded audio quality during the VideoIdent and eSign processes, potentially leading to call difficulties or drop-offs. Disclaimer: This issue specifically affects iOS 26 and newer versions. Older iOS versions, Android devices, and the web-based VideoIdent/eSign flows are not impacted. AutoIdent and all other products from our service provider remain unaffected. If you have any questions or require support, please contact us at [email protected] or through our dedicated ticketing platform.

Read the full incident report →

Started Sep 15, 2025, 09:40 AM UTC· resolved Sep 15, 2025, 01:10 PM UTC

1. monitoring Sep 15, 2025, 09:40 AM UTC

   The unplanned partial outage for Multiple Cards services identified to be affecting Cards creation and associated Card Lifecycle Status changes has been restored. Services were recovered and are currently being monitored to ensure operations are running within normal service levels. Partner Impact: 5XXs errors while calling the below API Endpoints • GET /v1/cards • GET /v1/cards/{id}/ • POST /v1/cards/{id}/virtual_card_requests is returning increased 5xx errors • POST /v1/cards/{card_id}/block returning increased 5xx errors • POST /v1/cards/{card_id}/unblock returning increased 5xx errors (not an exhaustive list) Customer Impact: • Customers attempting to perform card lifecycle operations or obtaining card CVC details may be presented with a generic error message intermittently, in the mobile or web applications • Customers attempting to create cards will be presented with 5XXs errors • Customers will be unable to Block and Unblock cards Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris SE API services. API Reference Documentation: To understand more about the impacted endpoints please read the following public documentation: • https://docs.solarisgroup.com/api-reference/digital-banking/cards/#tag/Cards-servicing/paths/~1v1~1persons~1{person_id}~1cards/get • https://docs.solarisgroup.com/api-reference/digital-banking/cards/#tag/Cards-servicing/paths/~1v1~1cards~1{id}~1virtual_card_requests/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.

2. resolved Sep 15, 2025, 01:10 PM UTC

   The unplanned partial outage for Multiple Cards services identified to be affecting Cards creation and associated Card Lifecycle Status changes has been resolved. Services are recovered and being monitored to ensure operations are running within normal service levels. Partner Impact: 5XXs errors while calling the below API Endpoints • GET /v1/cards • GET /v1/cards/{id}/ • POST /v1/cards/{id}/virtual_card_requests is returning increased 5xx errors • POST /v1/cards/{card_id}/block returning increased 5xx errors • POST /v1/cards/{card_id}/unblock returning increased 5xx errors (not an exhaustive list) Customer Impact: • Customers attempting to perform card lifecycle operations or obtaining card CVC details may be presented with a generic error message intermittently, in the mobile or web applications • Customers attempting to create cards will be presented with 5XXs errors • Customers will be unable to Block and Unblock cards Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris SE API services. API Reference Documentation: To understand more about the impacted endpoints please read the following public documentation: • https://docs.solarisgroup.com/api-reference/digital-banking/cards/#tag/Cards-servicing/paths/~1v1~1persons~1{person_id}~1cards/get • https://docs.solarisgroup.com/api-reference/digital-banking/cards/#tag/Cards-servicing/paths/~1v1~1cards~1{id}~1virtual_card_requests/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.

Read the full incident report →

Started Sep 02, 2025, 04:18 PM UTC· resolved Sep 03, 2025, 09:14 AM UTC

1. investigating Sep 02, 2025, 04:18 PM UTC

   An Unplanned outage has been identified for Identifications performed using Bank Identifications. The outage is linked to an issue with one of our identification provider. We are working to restore the impacted services with the provider as soon as possible. Partner Impact: • Partners will observe failures during the signing of documents within the Bank identification. Identifications either remain in status 'Authorization Required' or 'Failed' with reason 'Expired' Customer Impact: • Customers are prompted with an 'unexpected error' message during the onboarding process at the contract signing step Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris API services Impacted endpoints: • PATCH /v1/persons/{person_id}/identifications/{id}/confirm • PATCH /v1/persons/{person_id}/identifications/{id}/authorize API Reference Documentation: To understand more about the impacted endpoints please read the following public documentation: • https://docs.solarisgroup.com/api-reference/identity/identifications/#tag/Person-identifications/paths/~1v1~1persons~1{person_id}~1identifications~1{id}~1confirm/patch • https://docs.solarisgroup.com/api-reference/identity/identifications/#tag/Person-identifications/paths/~1v1~1persons~1{person_id}~1identifications~1{id}~1authorize/patch 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.

2. resolved Sep 03, 2025, 09:14 AM UTC

   An Unplanned outage that was identified for Identifications performed using Bank Identifications has been resolved. We monitored the services with our providers and found no further issues. Partner Impact: • Partners will no longer observe failures during the signing of documents within the Bank identification. Customer Impact: • Customers will no longer be prompted with an error message during the onboarding process at the contract signing step Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris API services Impacted endpoints: • PATCH /v1/persons/{person_id}/identifications/{id}/confirm • PATCH /v1/persons/{person_id}/identifications/{id}/authorize API Reference Documentation: To understand more about the impacted endpoints please read the following public documentation: • https://docs.solarisgroup.com/api-reference/identity/identifications/#tag/Person-identifications/paths/~1v1~1persons~1{person_id}~1identifications~1{id}~1confirm/patch • https://docs.solarisgroup.com/api-reference/identity/identifications/#tag/Person-identifications/paths/~1v1~1persons~1{person_id}~1identifications~1{id}~1authorize/patch The incident has been resolved. 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.

Read the full incident report →

Started Jun 23, 2025, 02:40 PM UTC· resolved Jun 24, 2025, 08:55 AM UTC

1. monitoring Jun 23, 2025, 02:40 PM UTC

   An unplanned Performance Degradation with our Device Monitoring provider has been identified. Partners that are required to collect device fingerprints from their customers' devices using the Seon SDK when calling certain API endpoints would experience issues affecting the cdn.seondf.com domain, which may cause intermittent failures when loading the Javascript SDKs. As a workaround, the recommended solution is to switch to the below verified alternate domains to ensure uninterrupted service cdn.dfsdk.com Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris' API services. Impacted endpoints: • https://docs.solarisgroup.com/guides/kyc/device-monitoring/#actions-that-require-device-monitoring API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/guides/kyc/device-monitoring/#actions-that-require-device-monitoring In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

2. monitoring Jun 23, 2025, 04:26 PM UTC

   We are continuing to monitor for any further issues.

3. monitoring Jun 23, 2025, 04:27 PM UTC

   An unplanned Performance Degradation with our Device Monitoring provider has been identified. Partners that are required to collect device fingerprints from their customers' devices using the Seon SDK when calling certain API endpoints would experience issues affecting the cdn.seondf.com domain, which may cause intermittent failures when loading the Javascript SDKs. As a workaround, the recommended solution is to switch to the below verified alternate domains to ensure uninterrupted service cdn.dfsdk.com Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris' API services. Impacted endpoints: • https://docs.solarisgroup.com/guides/kyc/device-monitoring/#actions-that-require-device-monitoring API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/guides/kyc/device-monitoring/#actions-that-require-device-monitoring In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

4. monitoring Jun 23, 2025, 04:29 PM UTC

   An unplanned Performance Degradation with our Device Monitoring provider has been identified. Partners that are required to collect device fingerprints from their customers' devices using the Seon SDK when calling certain API endpoints would experience issues affecting the cdn.seondf.com domain, which may cause intermittent failures when loading the Javascript SDKs. As a workaround, the recommended solution is to switch to the below verified alternate domains to ensure uninterrupted service cdn.dfsdk.com Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris' API services. Impacted endpoints: • https://docs.solarisgroup.com/guides/kyc/device-monitoring/#actions-that-require-device-monitoring API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/guides/kyc/device-monitoring/#actions-that-require-device-monitoring In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

5. resolved Jun 24, 2025, 08:55 AM UTC

   An unplanned Performance Degradation with our Device Monitoring provider has been resolved. Partners that are required to collect device fingerprints from their customers' devices using the Seon SDK when calling certain API endpoints would not experience any further issues. No further action is required even if you have already migrated to other domains. All following domains are operating normally. - cdn.seondf.com - cdn.seonintelligence.com - cdn.deviceinf.com - cdn.dfsdk.com The incident has been resolved. No further updates will be provided. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris' API services. Impacted endpoints: • https://docs.solarisgroup.com/guides/kyc/device-monitoring/#actions-that-require-device-monitoring API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/guides/kyc/device-monitoring/#actions-that-require-device-monitoring In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

Read the full incident report →

Started Jun 22, 2025, 11:47 PM UTC· resolved Jun 23, 2025, 01:07 AM UTC

1. investigating Jun 22, 2025, 11:47 PM UTC

   We would like to inform you of an ongoing service disruption affecting the identification flow via IDnow. Due to a provider-side outage, you may encounter an increased number of 5XX errors during identification attempts. Partner Impact: • Partners may receive 5XX errors when calling the following endpoint: PATCH /v1/persons/{person_id}/identifications/{id}/request Customer Impact: • End users may experience errors when accessing services dependent on identity verification. Disclaimer: The actual customer impact may vary depending on how each partner has integrated Solarisbank API services. Impacted Endpoint: • PATCH /v1/persons/{person_id}/identifications/{id}/request API Reference: For more details on the affected endpoint, please refer to our documentation: https://docs.solarisgroup.com/guides/kyc/autoident/#patch-request-person-identification If you have any questions or require support, please contact us at [email protected] or through our dedicated ticketing platform.

2. resolved Jun 23, 2025, 01:07 AM UTC

   We would like to inform you that the disruption affecting the IDnow identification service has been successfully resolved. Our systems continue to be closely monitored, and all services are operating within normal performance levels. Customers can now retry the identification process by simply using the original identification link. The process will resume as expected without requiring any additional action. If you have any questions or require support, please contact us at [email protected] or through our dedicated ticketing platform.

Read the full incident report →

Started Mar 30, 2025, 11:11 PM UTC· resolved Mar 31, 2025, 02:10 PM UTC

1. identified Mar 30, 2025, 11:11 PM UTC

   An unplanned outage with PostBox service has been identified, which may impact the ability to retrieve documents using our services. Our team is actively working to restore the impacted service as soon as possible. Partner Impact: • Partners may experience HTTP 500 status error code while retrieving documents Customer Impact • Customers may experience issues with accessing documents via Web or APP Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. Impacted endpoints: - API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: https://docs.solarisgroup.com/api-reference/onboarding/compliance/#tag/Postbox-Items 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.

2. monitoring Mar 31, 2025, 12:10 AM UTC

   An unplanned outage with PostBox service has been identified, which may impact the ability to retrieve documents using our services. Our team is actively working to restore the impacted service as soon as possible. A fix has been implemented & services are being monitored in order to ensure all operations are running within normal service levels. Partner Impact: • Partners may experience HTTP 500 status error code while retrieving documents Customer Impact • Customers may experience issues with accessing documents via Web or APP Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. Impacted endpoints: - API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: https://docs.solarisgroup.com/api-reference/onboarding/compliance/#tag/Postbox-Items 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.

3. resolved Mar 31, 2025, 02:10 PM UTC

   An unplanned outage with PostBox service has been identified, which may impact the ability to retrieve documents using our services. Our team is actively working to restore the impacted service as soon as possible. A fix has been implemented & services have been monitored to ensure everything is being processed within normal service levels. Partner Impact: • Partners may experience HTTP 500 status error code while retrieving documents Customer Impact • Customers may experience issues with accessing documents via Web or APP Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. Impacted endpoints: - API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: https://docs.solarisgroup.com/api-reference/onboarding/compliance/#tag/Postbox-Items 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.

Read the full incident report →