MultiSafepay Status Page

May 27, 2026 · resolved May 27

**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.

May 20, 2026 · resolved May 20

The incident has been resolved outside of our infrastructure.

Apr 30, 2026 · resolved Apr 30

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

Apr 30, 2026 · resolved Apr 30

This incident has been resolved.

Apr 15, 2026 · resolved Apr 15

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