Precios
Historial de estadoActualizaciones RSSAPI de estado

Desarrollado por Uptimus

    Historial de interrupciones de Multisafepay

    54 incidentes de Multisafepay registrados desde julio de 2024, con actualizaciones oficiales, componentes afectados, duración y detalles de resolución.

    Volver al estado actual

    Interrupción del servicio de revuelta

    Comenzó 20 de octubre de 2026 a las 10:26 UTC · 1d 0h

    IssuesIncidente menor
    Componentes afectados
    Payments
    1. 20 de octubre de 2026 a las 10:26 UTCinvestigating

      Somos conscientes de un outage en el lado de Revolut que impacta las transacciones de tarjetas con tarjetas enviadas por Revolut. Esta cuestión es externa a la plataforma MultiSafepay; todos los demás métodos de pago siguen funcionando. Estamos monitoreando la situación y proporcionaremos una actualización una vez restaurado el servicio.

    2. 21 de octubre de 2026 a las 10:40 UTCresolved

      Este incidente ha sido resuelto.

    Traducido automáticamente desde la actualización oficial del incidente.

    Degradación de los resultados de la notificación

    Comenzó 12 de septiembre de 2026 a las 15:26 UTC · 1h 19m

    IssuesIncidente menor
    Componentes afectados
    APIPayments
    1. 12 de septiembre de 2026 a las 15:26 UTCinvestigating

      Se ha desplegado una solución. Las notificaciones previamente solicitadas serán automáticamente reenviadas.

    2. 12 de septiembre de 2026 a las 16:42 UTCinvestigating

      Seguimos investigando esta cuestión.

    3. 12 de septiembre de 2026 a las 16:45 UTCresolved

      Este incidente ha sido resuelto.

    Traducido automáticamente desde la actualización oficial del incidente.

    Mastercard 3DS Processing Performance: Deprecation notice

    Comenzó 15 de julio de 2026 a las 7:39 UTC · 2h 19m

    IssuesIncidente menor
    Componentes afectados
    Payments
    1. 15 de julio de 2026 a las 7:39 UTCinvestigating

      El rendimiento de 3DS de la transacción de Mastercard está experimentando una caída significativa del rendimiento. Estamos investigando el tema, parece estar fuera de la plataforma MultiSafepay.

    2. 15 de julio de 2026 a las 7:53 UTCidentified

      Mastercard ha identificado la cuestión al final que estamos esperando resolución.

    3. 15 de julio de 2026 a las 9:58 UTCresolved

      El incidente ha sido resuelto por Mastercard alrededor de las 11:00 CEST.

    Traducido automáticamente desde la actualización oficial del incidente.

    Documentation Center currently unavailable

    Comenzó 13 de julio de 2026 a las 13:26 UTC · 3h 20m

    OutageIncidente mayor
    Componentes afectados
    docs.multisafepay.com
    1. 13 de julio de 2026 a las 13:26 UTCidentified

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

    2. 13 de julio de 2026 a las 16:46 UTCresolved

      This incident has been resolved.

    iDEAL performance issues identified at issuer ABN AMRO

    Comenzó 6 de julio de 2026 a las 14:43 UTC · 17m

    IssuesIncidente menor
    Componentes afectados
    Payments
    1. 6 de julio de 2026 a las 14:43 UTCinvestigating

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

    2. 6 de julio de 2026 a las 15:00 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

    Comenzó 5 de julio de 2026 a las 8:48 UTC · 1h 26m

    IssuesIncidente menor
    Componentes afectados
    APIPayments
    1. 5 de julio de 2026 a las 8:48 UTCidentified

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

    2. 5 de julio de 2026 a las 9:16 UTCmonitoring

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

    3. 5 de julio de 2026 a las 10:15 UTCresolved

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

    iDEAL performance issues identified at scheme

    Comenzó 2 de julio de 2026 a las 9:03 UTC · 53m

    IssuesIncidente menor
    Componentes afectados
    Payments
    1. 2 de julio de 2026 a las 9:03 UTCidentified

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

    2. 2 de julio de 2026 a las 9:56 UTCresolved

      The incident has been resolved at 11:35 CEST

    Resolved Service Incident – sFTP report delivery

    Comenzó 16 de junio de 2026 a las 16:00 UTC · 0m

    Pending
    1. 17 de junio de 2026 a las 7: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.

    Partial outage - payment processing below performance level

    Comenzó 4 de junio de 2026 a las 14:21 UTC · 3m

    OutageIncidente mayor
    Componentes afectados
    APIPayments
    1. 4 de junio de 2026 a las 14:21 UTCinvestigating

      We are currently investigating a drop in payment performance

    2. 4 de junio de 2026 a las 14:24 UTCresolved

      The incident has been resolved

    iDEAL performance issues identified at issuer Rabobank

    Comenzó 1 de junio de 2026 a las 7:28 UTC · 22m

    IssuesIncidente menor
    Componentes afectados
    Payments
    1. 1 de junio de 2026 a las 7: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 de junio de 2026 a las 7:49 UTCresolved

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

    Platform performance degradation

    Comenzó 27 de mayo de 2026 a las 13:49 UTC · 48m

    OutageIncidente mayor
    Componentes afectados
    MultiSafepay payment pagesAPIPayments
    1. 27 de mayo de 2026 a las 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 de mayo de 2026 a las 13:56 UTCidentified

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

    3. 27 de mayo de 2026 a las 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 de mayo de 2026 a las 14:37 UTCresolved

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

    5. 28 de mayo de 2026 a las 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.

    Major performance degradation of Bancontact payments

    Comenzó 20 de mayo de 2026 a las 13:36 UTC · 7m

    OutageIncidente mayor
    Componentes afectados
    Payments
    1. 20 de mayo de 2026 a las 13:36 UTCinvestigating

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

    2. 20 de mayo de 2026 a las 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 de mayo de 2026 a las 13:44 UTCresolved

      The incident has been resolved outside of our infrastructure.

    Payment method performance degradation

    Comenzó 30 de abril de 2026 a las 23:00 UTC · 0m

    Pending
    1. 1 de mayo de 2026 a las 11:21 UTCresolved

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

    Platform performance degradation

    Comenzó 30 de abril de 2026 a las 21:05 UTC · 8m

    Pending
    Componentes afectados
    MultiSafepay appPayments
    1. 30 de abril de 2026 a las 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 de abril de 2026 a las 21:12 UTCresolved

      This incident has been resolved.

    Partial outage - Payment method performance degradation

    Comenzó 15 de abril de 2026 a las 6:43 UTC · 14m

    OutageIncidente mayor
    Componentes afectados
    MultiSafepay payment pagesAPIPayments
    1. 15 de abril de 2026 a las 6: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 de abril de 2026 a las 6:53 UTCmonitoring

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

    3. 15 de abril de 2026 a las 6:54 UTCmonitoring

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

    4. 15 de abril de 2026 a las 6:57 UTCresolved

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

    [Bancontact] Full disruption in payment success rate

    Comenzó 30 de marzo de 2026 a las 10:17 UTC · 40m

    OutageIncidente mayor
    Componentes afectados
    Payments
    1. 30 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 10:57 UTCresolved

      The incident has been resolved.

    iDEAL outage identified

    Comenzó 25 de marzo de 2026 a las 14:40 UTC · 7m

    OutageIncidente crítico
    Componentes afectados
    Payments
    1. 25 de marzo de 2026 a las 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 de marzo de 2026 a las 14:43 UTCidentified

      The issue now looks contain to issuer Rabobank

    3. 25 de marzo de 2026 a las 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/

    Bancontact transaction outage

    Comenzó 14 de febrero de 2026 a las 9:00 UTC · 0m

    Pending
    1. 14 de febrero de 2026 a las 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.

    iDEAL performance issues identified at issuer ABN AMRO

    Comenzó 9 de febrero de 2026 a las 18:47 UTC · 9m

    IssuesIncidente menor
    Componentes afectados
    Payments
    1. 9 de febrero de 2026 a las 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 de febrero de 2026 a las 18:56 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

    Comenzó 3 de febrero de 2026 a las 9:02 UTC · 4h 19m

    IssuesIncidente menor
    Componentes afectados
    MultiSafepay account dashboard
    1. 3 de febrero de 2026 a las 9: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 de febrero de 2026 a las 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.