Störungsverlauf von Multisafepay

1. 20. Oktober 2026 um 10:26 UTCinvestigating

   Wir sind uns eines Ausfalls auf der Seite von Revolut bewusst, der sich auf Kartentransaktionen mit von Revolut ausgegebenen Karten auswirkt. Dieses Problem liegt außerhalb der MultiSafepay-Plattform; alle anderen Zahlungsmethoden bleiben funktionsfähig. Wir überwachen die Situation und werden ein Update bereitstellen, sobald der Service wiederhergestellt ist.

2. 21. Oktober 2026 um 10:40 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 12. September 2026 um 15:26 UTCinvestigating

   Ein Fix wurde bereitgestellt. Zuvor in die Warteschlange gestellte Benachrichtigungen werden automatisch erneut gesendet.

2. 12. September 2026 um 16:42 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 12. September 2026 um 16:45 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 15. Juli 2026 um 07:39 UTCinvestigating

   Die 3DS-Performance der Mastercard-Transaktion erlebt einen signifikanten Performance-Rückgang. Wir untersuchen das Problem, es scheint außerhalb der MultiSafepay-Plattform zu sein.

2. 15. Juli 2026 um 07:53 UTCidentified

   Mastercard hat das Problem an ihrem Ende identifiziert, auf das wir warten.

3. 15. Juli 2026 um 09:58 UTCresolved

   Der Vorfall wurde von Mastercard gegen 11:00 Uhr MESZ gelöst.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 13. Juli 2026 um 13:26 UTCidentified

   We have identified an issue that our Documentation Center is currently working properly and are working on a resolution.

2. 13. Juli 2026 um 16:46 UTCresolved

   This incident has been resolved.

1. 6. Juli 2026 um 14:43 UTCinvestigating

   iDEAL performance issues have reoccurred at ABN AMRO. For more details: https://availability.ideal.nl/

2. 6. Juli 2026 um 15:00 UTCresolved

   The incident has been resolved, we're keeping track of any flare ups For more details: https://availability.ideal.nl/

1. 5. Juli 2026 um 08:48 UTCidentified

   An decrease in delivery success has been spotted on our platform. Our team is investigating the root cause.

2. 5. Juli 2026 um 09:16 UTCmonitoring

   A fix has been implemented and we are monitoring at this point

3. 5. Juli 2026 um 10:15 UTCresolved

   The incident has been resolved and previously failed notifications have been resent.

1. 2. Juli 2026 um 09:03 UTCidentified

   An partial outage on the iDEAL platform has been identified. For more details: https://availability.ideal.nl/

2. 2. Juli 2026 um 09:56 UTCresolved

   The incident has been resolved at 11:35 CEST

1. 17. Juni 2026 um 07:23 UTCresolved

   We identified an incident affecting report delivery over sFTP between 18:00 CEST on 16 June and 08:30 CEST on 17 June. The issue has now been resolved. Any report subscriptions that were impacted during this period can be re-executed.

1. 4. Juni 2026 um 14:21 UTCinvestigating

   We are currently investigating a drop in payment performance

2. 4. Juni 2026 um 14:24 UTCresolved

   The incident has been resolved

1. 1. Juni 2026 um 07:28 UTCidentified

   There are identified performance issues with iDEAL payments at Rabobank, we are awaiting resolution by the issuer. For more details: https://availability.ideal.nl/

2. 1. Juni 2026 um 07:49 UTCresolved

   The incident has been resolved. For more details https://availability.ideal.nl/

1. 27. Mai 2026 um 13:49 UTCidentified

   Our platform is experiencing degraded performance. We are aware of the issue(s) and our team is investigating, we will update as soon as possible.

2. 27. Mai 2026 um 13:56 UTCidentified

   Our team has identified the root cause and is working on the resolution.

3. 27. Mai 2026 um 14:30 UTCmonitoring

   The incident has been resolved and performance has returned to normal levels. We are continuing to monitor the situation closely.

4. 27. Mai 2026 um 14:37 UTCresolved

   The incident has been resolved, and all services are operating normally.

5. 28. Mai 2026 um 16:29 UTCpostmortem

   **Incident Post-Mortem: Transaction Processing Disruption — 27 May 2026** **Post-incident update** On 27 May 2026, MultiSafepay experienced a service disruption that significantly affected transaction processing. The first alerts were triggered at approximately 15:28 CEST, when our monitoring detected an increase in system errors. Our engineering team started investigating immediately and identified the issue in a database table used for asynchronous transaction actions. **15:28–16:07 — Partial impact**   An internal capacity limit was reached, preventing certain transaction flows from being completed successfully. As a result, a large number of online transactions failed. POS transactions continued to process normally throughout this period. **16:07–16:23 — Processing outage**   The work needed to resolve the underlying issue caused a processing outage. No transactions were processed during this window. Transaction processing resumed at 16:23 CEST. After the main service was restored, our team continued recovery work on the affected follow-up processes. Key recovery steps were completed during the evening, with additional validation continuing afterwards to confirm completeness. **Root cause** The root cause was a database issue that occurred during a capacity expansion operation on a long-standing database table supporting offline and asynchronous transaction actions. The integer identifier range on this table was approaching its upper limit due to sustained growth in processing volumes. During the expansion activity to extend this range, the database issue prevented new records from being inserted where this table was required, disrupting affected transaction processing. **What we’re doing** We are taking the following actions to reduce the risk of this happening again: * reviewing any similar configuration limits and increasing capacity thresholds where needed, to ensure our platform can accommodate peak loads without disruption. * Improving monitoring and increasing internal alerts so we can act well before any limit is reached. * Using these findings to further strengthen the reliability of our platform. We are sorry for the disruption this caused to our merchants and their customers. We take the trust our merchants place in us seriously. If you have questions, please reach out to our team.

1. 20. Mai 2026 um 13:36 UTCinvestigating

   We are currently investigating a major performance degradation of Bancontact payments. Once more information is available we will update

2. 20. Mai 2026 um 13:41 UTCmonitoring

   Traffic has returned to regular performance levels, the incident appears outside of our infrastructure. We’ll be monitoring for now.

3. 20. Mai 2026 um 13:44 UTCresolved

   The incident has been resolved outside of our infrastructure.

1. 1. Mai 2026 um 11:21 UTCresolved

   An incident occured in the payment performance between 12:58 and 13:15 the team has resolved the incident.

1. 30. April 2026 um 21:05 UTCinvestigating

   Our Payment Pages are experiencing degraded performance. We are aware of the issue(s) and our team is investigating, we will update as soon as possible.

2. 30. April 2026 um 21:12 UTCresolved

   This incident has been resolved.

1. 15. April 2026 um 06:43 UTCinvestigating

   We are currently investigating a partial outage of payment processing across our channels. We will update as soon as there is more information available

2. 15. April 2026 um 06:53 UTCmonitoring

   The incident has been resolved and our team is currently monitoring the situation.

3. 15. April 2026 um 06:54 UTCmonitoring

   The incident has been resolved and our team is currently monitoring the situation before closing the incident.

4. 15. April 2026 um 06:57 UTCresolved

   The incident is resolved and closed. A review will follow to address root cause and prevention.

1. 30. März 2026 um 10:17 UTCidentified

   We have identified a significant decline in Bancontact transaction performance and are actively investigating the issue to resolve it as quickly as possible.

2. 30. März 2026 um 10:21 UTCidentified

   The root cause of the incident has been identified and is external to MultiSafepay’s infrastructure. We are currently awaiting resolution from the relevant party.

3. 30. März 2026 um 10:48 UTCmonitoring

   Transaction performance is returning to near normal levels. We will continue to monitor the situation closely before closing the incident.

4. 30. März 2026 um 10:57 UTCresolved

   The incident has been resolved.

1. 25. März 2026 um 14:40 UTCidentified

   A full outage of iDEAL has been identified. We are awaiting resolution by the scheme. For more details https://availability.ideal.nl/

2. 25. März 2026 um 14:43 UTCidentified

   The issue now looks contain to issuer Rabobank

3. 25. März 2026 um 14:47 UTCresolved

   The incident has been resolved by the scheme. Our team will monitor the situation but resolve the incident. For more details: https://availability.ideal.nl/

1. 14. Februar 2026 um 10:25 UTCresolved

   Bancontact transaction creation and capture experienced an outage between 10:00 and 10:30 CET. Transaction volumes and conversion rates have since returned to normal levels. Our team is currently analyzing the root cause.

1. 9. Februar 2026 um 18:47 UTCidentified

   There are identified performance issues with iDEAL payments at ABN AMRO, we are awaiting resolution by the issuer. For more details: https://availability.ideal.nl/

2. 9. Februar 2026 um 18:56 UTCresolved

   The incident has been resolved by the issuer and we're closing the incident. For more details: https://availability.ideal.nl/

1. 3. Februar 2026 um 09:02 UTCidentified

   Our processing bank has encountered a disruption in processing settlement batches, which has resulted in a delay in payouts. The incident has been flagged with the bank, and they are actively working to resolve it. The affected batches have been re-executed, and payouts are expected to be received between today and tomorrow depending on the bank.

2. 3. Februar 2026 um 13:21 UTCresolved

   Our processing bank has now successfully re-executed the affected settlement batches, and the funds have been settled. Payouts are expected to be received as normal.