Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Multisafepay 장애 기록

    54 Multisafepay incidents · 2024년 7월 — official updates, affected components, duration and resolution details.

    현재 상태로 돌아가기

    Revolut 서비스 붕괴

    시작 2026년 10월 20일 오전 10:26 UTC · 1d 0h

    Issues경미한 인시던트
    영향을 받은 구성 요소
    Payments
    1. 2026년 10월 20일 오전 10:26 UTCinvestigating

      Revolut-issued 카드로 카드 거래에 영향을 미치는 Revolut의 측면에 대한 주의가 있습니다. 이 문제점은 MultiSafepay 플랫폼에 외부입니다; 다른 모든 지불 방법은 가동의 남아 있습니다. 우리는 상황을 모니터링하고 한 번 업데이트 서비스를 복원 할 것입니다.

    2. 2026년 10월 21일 오전 10:40 UTCresolved

      이 사건은 해결되었습니다.

    공식 인시던트 업데이트를 자동 번역했습니다.

    알림 납품 성과 degradation

    시작 2026년 9월 12일 오후 3:26 UTC · 1h 19m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    APIPayments
    1. 2026년 9월 12일 오후 3:26 UTCinvestigating

      수정이 배포되었습니다. 이전에 누락된 알림은 자동으로 재입력됩니다.

    2. 2026년 9월 12일 오후 4:42 UTCinvestigating

      이 문제를 조사하고 있습니다.

    3. 2026년 9월 12일 오후 4:45 UTCresolved

      이 사건은 해결되었습니다.

    공식 인시던트 업데이트를 자동 번역했습니다.

    Mastercard 3DS 처리 성능 : 사전 통지

    시작 2026년 7월 15일 오전 7:39 UTC · 2h 19m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    Payments
    1. 2026년 7월 15일 오전 7:39 UTCinvestigating

      Mastercard 거래의 3DS 성능은 상당한 성능의 하락을 경험하고있다. MultiSafepay 플랫폼 밖에서 문제가 발생하고 있습니다.

    2. 2026년 7월 15일 오전 7:53 UTCidentified

      Mastercard는 끝의 문제점을 확인했습니다. 우리는 해결책을 기다리고 있습니다.

    3. 2026년 7월 15일 오전 9:58 UTCresolved

      사건은 11 시부 터 Mastercard에 의해 해결되었습니다.

    공식 인시던트 업데이트를 자동 번역했습니다.

    Documentation Center currently unavailable

    시작 2026년 7월 13일 오후 1:26 UTC · 3h 20m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    docs.multisafepay.com
    1. 2026년 7월 13일 오후 1:26 UTCidentified

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

    2. 2026년 7월 13일 오후 4:46 UTCresolved

      This incident has been resolved.

    iDEAL performance issues identified at issuer ABN AMRO

    시작 2026년 7월 6일 오후 2:43 UTC · 17m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    Payments
    1. 2026년 7월 6일 오후 2:43 UTCinvestigating

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

    2. 2026년 7월 6일 오후 3: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

    시작 2026년 7월 5일 오전 8:48 UTC · 1h 26m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    APIPayments
    1. 2026년 7월 5일 오전 8:48 UTCidentified

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

    2. 2026년 7월 5일 오전 9:16 UTCmonitoring

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

    3. 2026년 7월 5일 오전 10:15 UTCresolved

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

    iDEAL performance issues identified at scheme

    시작 2026년 7월 2일 오전 9:03 UTC · 53m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    Payments
    1. 2026년 7월 2일 오전 9:03 UTCidentified

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

    2. 2026년 7월 2일 오전 9:56 UTCresolved

      The incident has been resolved at 11:35 CEST

    Resolved Service Incident – sFTP report delivery

    시작 2026년 6월 16일 오후 4:00 UTC · 0m

    Pending
    1. 2026년 6월 17일 오전 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

    시작 2026년 6월 4일 오후 2:21 UTC · 3m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    APIPayments
    1. 2026년 6월 4일 오후 2:21 UTCinvestigating

      We are currently investigating a drop in payment performance

    2. 2026년 6월 4일 오후 2:24 UTCresolved

      The incident has been resolved

    iDEAL performance issues identified at issuer Rabobank

    시작 2026년 6월 1일 오전 7:28 UTC · 22m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    Payments
    1. 2026년 6월 1일 오전 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. 2026년 6월 1일 오전 7:49 UTCresolved

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

    Platform performance degradation

    시작 2026년 5월 27일 오후 1:49 UTC · 48m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    MultiSafepay payment pagesAPIPayments
    1. 2026년 5월 27일 오후 1: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. 2026년 5월 27일 오후 1:56 UTCidentified

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

    3. 2026년 5월 27일 오후 2:30 UTCmonitoring

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

    4. 2026년 5월 27일 오후 2:37 UTCresolved

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

    5. 2026년 5월 28일 오후 4: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

    시작 2026년 5월 20일 오후 1:36 UTC · 7m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Payments
    1. 2026년 5월 20일 오후 1:36 UTCinvestigating

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

    2. 2026년 5월 20일 오후 1:41 UTCmonitoring

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

    3. 2026년 5월 20일 오후 1:44 UTCresolved

      The incident has been resolved outside of our infrastructure.

    Payment method performance degradation

    시작 2026년 4월 30일 오후 11:00 UTC · 0m

    Pending
    1. 2026년 5월 1일 오전 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

    시작 2026년 4월 30일 오후 9:05 UTC · 8m

    Pending
    영향을 받은 구성 요소
    MultiSafepay appPayments
    1. 2026년 4월 30일 오후 9: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. 2026년 4월 30일 오후 9:12 UTCresolved

      This incident has been resolved.

    Partial outage - Payment method performance degradation

    시작 2026년 4월 15일 오전 6:43 UTC · 14m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    MultiSafepay payment pagesAPIPayments
    1. 2026년 4월 15일 오전 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. 2026년 4월 15일 오전 6:53 UTCmonitoring

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

    3. 2026년 4월 15일 오전 6:54 UTCmonitoring

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

    4. 2026년 4월 15일 오전 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

    시작 2026년 3월 30일 오전 10:17 UTC · 40m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Payments
    1. 2026년 3월 30일 오전 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. 2026년 3월 30일 오전 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. 2026년 3월 30일 오전 10:48 UTCmonitoring

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

    4. 2026년 3월 30일 오전 10:57 UTCresolved

      The incident has been resolved.

    iDEAL outage identified

    시작 2026년 3월 25일 오후 2:40 UTC · 7m

    Outage심각한 인시던트
    영향을 받은 구성 요소
    Payments
    1. 2026년 3월 25일 오후 2: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. 2026년 3월 25일 오후 2:43 UTCidentified

      The issue now looks contain to issuer Rabobank

    3. 2026년 3월 25일 오후 2: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

    시작 2026년 2월 14일 오전 9:00 UTC · 0m

    Pending
    1. 2026년 2월 14일 오전 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

    시작 2026년 2월 9일 오후 6:47 UTC · 9m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    Payments
    1. 2026년 2월 9일 오후 6: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. 2026년 2월 9일 오후 6: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

    시작 2026년 2월 3일 오전 9:02 UTC · 4h 19m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    MultiSafepay account dashboard
    1. 2026년 2월 3일 오전 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. 2026년 2월 3일 오후 1: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.