54 Multisafepay incidents · juli 2024 — official updates, affected components, duration and resolution details.
Vi er klar over en afbrydelse på Revoluts side, der påvirker kort transaktioner med Revolut-udstedte kort. Dette spørgsmål er uden for MultiSafepay-platformen; alle andre betalingsmetoder forbliver operationelle. Vi overvåger situationen og vil levere en opdatering, når tjenesten er genoprettet.
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
Et fix er blevet udsendt. Tidligere meddelelser i kø vil automatisk blive sendt tilbage.
Vi fortsætter med at undersøge dette spørgsmål.
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
3DS performance af Mastercard transaktion oplever et betydeligt fald i performance. Vi undersøger sagen, det ser ud til at være uden for MultiSafepay-platformen.
Mastercard har identificeret spørgsmålet om deres afslutning, vi afventer en beslutning.
Hændelsen er blevet løst af Mastercard omkring kl. 11: 00 EST.
Automatisk oversat fra den officielle hændelsesopdatering.
We have identified an issue that our Documentation Center is currently working properly and are working on a resolution.
This incident has been resolved.
iDEAL performance issues have reoccurred at ABN AMRO. For more details: https://availability.ideal.nl/
The incident has been resolved, we're keeping track of any flare ups For more details: https://availability.ideal.nl/
An decrease in delivery success has been spotted on our platform. Our team is investigating the root cause.
A fix has been implemented and we are monitoring at this point
The incident has been resolved and previously failed notifications have been resent.
An partial outage on the iDEAL platform has been identified. For more details: https://availability.ideal.nl/
The incident has been resolved at 11:35 CEST
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.
We are currently investigating a drop in payment performance
The incident has been resolved
There are identified performance issues with iDEAL payments at Rabobank, we are awaiting resolution by the issuer. For more details: https://availability.ideal.nl/
The incident has been resolved. For more details https://availability.ideal.nl/
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.
Our team has identified the root cause and is working on the resolution.
The incident has been resolved and performance has returned to normal levels. We are continuing to monitor the situation closely.
The incident has been resolved, and all services are operating normally.
**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.
We are currently investigating a major performance degradation of Bancontact payments. Once more information is available we will update
Traffic has returned to regular performance levels, the incident appears outside of our infrastructure. We’ll be monitoring for now.
The incident has been resolved outside of our infrastructure.
An incident occured in the payment performance between 12:58 and 13:15 the team has resolved the incident.
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.
This incident has been resolved.
We are currently investigating a partial outage of payment processing across our channels. We will update as soon as there is more information available
The incident has been resolved and our team is currently monitoring the situation.
The incident has been resolved and our team is currently monitoring the situation before closing the incident.
The incident is resolved and closed. A review will follow to address root cause and prevention.
We have identified a significant decline in Bancontact transaction performance and are actively investigating the issue to resolve it as quickly as possible.
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.
Transaction performance is returning to near normal levels. We will continue to monitor the situation closely before closing the incident.
The incident has been resolved.
A full outage of iDEAL has been identified. We are awaiting resolution by the scheme. For more details https://availability.ideal.nl/
The issue now looks contain to issuer Rabobank
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/
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.
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/
The incident has been resolved by the issuer and we're closing the incident. For more details: https://availability.ideal.nl/
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.
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.
