Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Multisafepay outage history

    54 recorded Multisafepay incidents since July 2024, with official updates, affected components, duration and resolution information.

    Back to current status

    Revolut service disruption

    Started October 20, 2026 at 10:26 AM UTC · 1d 0h

    IssuesMinor incident
    Affected components
    Payments
    1. October 20, 2026 at 10:26 AM UTCinvestigating

      We are aware of an outage on Revolut’s side that impacts card transactions with Revolut-issued cards. This issue is external to the MultiSafepay platform; all other payment methods remain operational. We are monitoring the situation and will provide an update once service is restored.

    2. October 21, 2026 at 10:40 AM UTCresolved

      This incident has been resolved.

    Notification delivery performance degradation

    Started September 12, 2026 at 3:26 PM UTC · 1h 19m

    IssuesMinor incident
    Affected components
    APIPayments
    1. September 12, 2026 at 3:26 PM UTCinvestigating

      A fix has been deployed. Previously queued notifications will automatically be re-sent.

    2. September 12, 2026 at 4:42 PM UTCinvestigating

      We are continuing to investigate this issue.

    3. September 12, 2026 at 4:45 PM UTCresolved

      This incident has been resolved.

    Mastercard 3DS Processing Performance: Deprecation notice

    Started July 15, 2026 at 7:39 AM UTC · 2h 19m

    IssuesMinor incident
    Affected components
    Payments
    1. July 15, 2026 at 7:39 AM UTCinvestigating

      3DS performance of Mastercard transaction is experiencing a significant performance drop. We are investigating the issue, it appears to be outside of MultiSafepay platform.

    2. July 15, 2026 at 7:53 AM UTCidentified

      Mastercard has identified the issue on their end we are awaiting resolution.

    3. July 15, 2026 at 9:58 AM UTCresolved

      The incident has been resolved by Mastercard at around 11:00 CEST.

    Documentation Center currently unavailable

    Started July 13, 2026 at 1:26 PM UTC · 3h 20m

    OutageMajor incident
    Affected components
    docs.multisafepay.com
    1. July 13, 2026 at 1:26 PM UTCidentified

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

    2. July 13, 2026 at 4:46 PM UTCresolved

      This incident has been resolved.

    iDEAL performance issues identified at issuer ABN AMRO

    Started July 6, 2026 at 2:43 PM UTC · 17m

    IssuesMinor incident
    Affected components
    Payments
    1. July 6, 2026 at 2:43 PM UTCinvestigating

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

    2. July 6, 2026 at 3:00 PM UTCresolved

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

    Notification delivery performance degradation

    Started July 5, 2026 at 8:48 AM UTC · 1h 26m

    IssuesMinor incident
    Affected components
    APIPayments
    1. July 5, 2026 at 8:48 AM UTCidentified

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

    2. July 5, 2026 at 9:16 AM UTCmonitoring

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

    3. July 5, 2026 at 10:15 AM UTCresolved

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

    iDEAL performance issues identified at scheme

    Started July 2, 2026 at 9:03 AM UTC · 53m

    IssuesMinor incident
    Affected components
    Payments
    1. July 2, 2026 at 9:03 AM UTCidentified

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

    2. July 2, 2026 at 9:56 AM UTCresolved

      The incident has been resolved at 11:35 CEST

    Resolved Service Incident – sFTP report delivery

    Started June 16, 2026 at 4:00 PM UTC · 0m

    Pending
    1. June 17, 2026 at 7:23 AM 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.

    Partial outage - payment processing below performance level

    Started June 4, 2026 at 2:21 PM UTC · 3m

    OutageMajor incident
    Affected components
    APIPayments
    1. June 4, 2026 at 2:21 PM UTCinvestigating

      We are currently investigating a drop in payment performance

    2. June 4, 2026 at 2:24 PM UTCresolved

      The incident has been resolved

    iDEAL performance issues identified at issuer Rabobank

    Started June 1, 2026 at 7:28 AM UTC · 22m

    IssuesMinor incident
    Affected components
    Payments
    1. June 1, 2026 at 7:28 AM 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. June 1, 2026 at 7:49 AM UTCresolved

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

    Platform performance degradation

    Started May 27, 2026 at 1:49 PM UTC · 48m

    OutageMajor incident
    Affected components
    MultiSafepay payment pagesAPIPayments
    1. May 27, 2026 at 1:49 PM 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. May 27, 2026 at 1:56 PM UTCidentified

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

    3. May 27, 2026 at 2:30 PM UTCmonitoring

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

    4. May 27, 2026 at 2:37 PM UTCresolved

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

    5. May 28, 2026 at 4:29 PM 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.

    Major performance degradation of Bancontact payments

    Started May 20, 2026 at 1:36 PM UTC · 7m

    OutageMajor incident
    Affected components
    Payments
    1. May 20, 2026 at 1:36 PM UTCinvestigating

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

    2. May 20, 2026 at 1:41 PM UTCmonitoring

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

    3. May 20, 2026 at 1:44 PM UTCresolved

      The incident has been resolved outside of our infrastructure.

    Payment method performance degradation

    Started April 30, 2026 at 11:00 PM UTC · 0m

    Pending
    1. May 1, 2026 at 11:21 AM UTCresolved

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

    Platform performance degradation

    Started April 30, 2026 at 9:05 PM UTC · 8m

    Pending
    Affected components
    MultiSafepay appPayments
    1. April 30, 2026 at 9:05 PM 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. April 30, 2026 at 9:12 PM UTCresolved

      This incident has been resolved.

    Partial outage - Payment method performance degradation

    Started April 15, 2026 at 6:43 AM UTC · 14m

    OutageMajor incident
    Affected components
    MultiSafepay payment pagesAPIPayments
    1. April 15, 2026 at 6:43 AM 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. April 15, 2026 at 6:53 AM UTCmonitoring

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

    3. April 15, 2026 at 6:54 AM UTCmonitoring

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

    4. April 15, 2026 at 6:57 AM UTCresolved

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

    [Bancontact] Full disruption in payment success rate

    Started March 30, 2026 at 10:17 AM UTC · 40m

    OutageMajor incident
    Affected components
    Payments
    1. March 30, 2026 at 10:17 AM 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. March 30, 2026 at 10:21 AM 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. March 30, 2026 at 10:48 AM UTCmonitoring

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

    4. March 30, 2026 at 10:57 AM UTCresolved

      The incident has been resolved.

    iDEAL outage identified

    Started March 25, 2026 at 2:40 PM UTC · 7m

    OutageCritical incident
    Affected components
    Payments
    1. March 25, 2026 at 2:40 PM UTCidentified

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

    2. March 25, 2026 at 2:43 PM UTCidentified

      The issue now looks contain to issuer Rabobank

    3. March 25, 2026 at 2:47 PM 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/

    Bancontact transaction outage

    Started February 14, 2026 at 9:00 AM UTC · 0m

    Pending
    1. February 14, 2026 at 10:25 AM 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.

    iDEAL performance issues identified at issuer ABN AMRO

    Started February 9, 2026 at 6:47 PM UTC · 9m

    IssuesMinor incident
    Affected components
    Payments
    1. February 9, 2026 at 6:47 PM 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. February 9, 2026 at 6:56 PM UTCresolved

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

    Payout delay - February 2nd 2026

    Started February 3, 2026 at 9:02 AM UTC · 4h 19m

    IssuesMinor incident
    Affected components
    MultiSafepay account dashboard
    1. February 3, 2026 at 9:02 AM 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. February 3, 2026 at 1:21 PM 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.