MultiSafepay Outage History

32 incidents recorded over the last 365 days, 27 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live MultiSafepay status100.00% uptime history

Every Recorded MultiSafepay Incident

MultiSafepay incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 22, 2026TEST environment -- Scheduled maintenance announcementThe maintenance has been finalised.32h 39mResolved
Oct 20, 2026Revolut service disruptionThis incident has been resolved.24h 13mResolved
Sep 12, 2026Notification delivery performance degradationThis incident has been resolved.1h 19mResolved
Aug 19, 2026Scheduled Maintenance - Payment PlatformThe scheduled maintenance has been completed.2h 0mScheduled
Jul 15, 2026Mastercard 3DS Processing Performance: Deprecation noticeThe incident has been resolved by Mastercard at around 11:00 CEST.2h 19mResolved
Jul 13, 2026Documentation Center currently unavailableThis incident has been resolved.3h 20mResolved
Jul 6, 2026iDEAL performance issues identified at issuer ABN AMROThe incident has been resolved, we're keeping track of any flare ups For more details: https://availability.ideal.nl/16 minResolved
Jul 5, 2026Notification delivery performance degradationThe incident has been resolved and previously failed notifications have been resent.1h 26mResolved
Jul 2, 2026iDEAL performance issues identified at schemeThe incident has been resolved at 11:35 CEST52 minResolved
Jun 17, 2026Resolved Service Incident – sFTP report deliveryWe 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…-923 minResolved
Jun 14, 2026Scheduled maintenance by Bancontact - brief interruptions possibleThe scheduled maintenance has been completed.6h 0mScheduled
Jun 4, 2026Partial outage - payment processing below performance levelThe incident has been resolved3 minResolved
Jun 1, 2026iDEAL performance issues identified at issuer RabobankThe incident has been resolved. For more details https://availability.ideal.nl/21 minResolved
May 27, 2026Platform performance degradation**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…47 minResolved
May 20, 2026Major performance degradation of Bancontact paymentsThe incident has been resolved outside of our infrastructure.7 minResolved
May 5, 2026Scheduled Database Maintenance – Brief service interruptions possibleThe scheduled maintenance has been completed.3h 0mScheduled
Apr 30, 2026Payment method performance degradationAn incident occured in the payment performance between 12:58 and 13:15 the team has resolved the incident.0 minResolved
Apr 30, 2026Platform performance degradationThis incident has been resolved.7 minResolved
Apr 30, 2026Scheduled Database Maintenance – Brief service interruptionsThe scheduled maintenance has been completed.2h 0mScheduled
Apr 15, 2026Partial outage - Payment method performance degradationThe incident is resolved and closed. A review will follow to address root cause and prevention.13 minResolved
Mar 30, 2026[Bancontact] Full disruption in payment success rateThe incident has been resolved.40 minResolved
Mar 26, 2026Scheduled Maintenance – CTAP POS DNS UpdateThe scheduled maintenance has been completed.10 minScheduled
Mar 25, 2026iDEAL outage identifiedThe incident has been resolved by the scheme. Our team will monitor the situation but resolve the incident. For more details: https://availability.ideal.nl/6 minResolved
Feb 14, 2026Bancontact transaction outageBancontact 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…-85 minResolved
Feb 9, 2026iDEAL performance issues identified at issuer ABN AMROThe incident has been resolved by the issuer and we're closing the incident. For more details: https://availability.ideal.nl/9 minResolved
Feb 3, 2026Payout delay - February 2nd 2026Our 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.4h 18mResolved
Dec 5, 2025Shopify affected by Cloudflare issueThe incident has been resolved. We'll be monitoring closely.15 minResolved
Dec 5, 2025iDEAL performance issues identifiedThe incident has been resolved. We'll be monitoring the situation.18 minResolved
Dec 1, 2025iDEAL performance issues identified at issuer RabobankThe incident has been resolved by the issuer.16 minResolved
Nov 18, 2025Cloudflare Supplier Incident - No payment performance impactWe’re closing this issue as we haven’t observed any further incidents. Cloudflare is still reporting some issues on their side that are affecting parts of their global infrastructure.3h 20mResolved
Nov 10, 2025[iDEAL] Multiple issuers are experiencing performance issuesThe incident has been resolved by iDEAL.39 minResolved
Nov 5, 2025[iDEAL] Issuer Rabobank is experiencing a major performance dropThe incident has been resolved at 11:2247 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next MultiSafepay incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This MultiSafepay Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before MultiSafepay acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single MultiSafepay outage in this window ran 1d 8h, against a mean recovery of 3h 4m. If you depend on MultiSafepay in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.