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

      リボリュートのカード取引に影響するレボリュートの側には、レボリュートが発行したカードとの取引に影響を及ぼすオナージュを意識しています。 この問題は、MultiSafepayプラットフォームの外部です。他のすべての支払い方法は、運用中のままです。 状況を監視し、サービスが復元されると更新を行います.

    2. 2026年10月21日 10:40 UTCresolved

      この事件は解決しました.

    公式のインシデント更新を自動翻訳しています。

    通知配達性能の低下

    開始 2026年9月12日 15:26 UTC · 1h 19m

    Issues軽微なインシデント
    影響を受けたコンポーネント
    APIPayments
    1. 2026年9月12日 15:26 UTCinvestigating

      修正が展開されました。 以前はキュート通知が自動的に再送信されます.

    2. 2026年9月12日 16:42 UTCinvestigating

      今後もこの問題について調査を続けてまいります.

    3. 2026年9月12日 16: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

      Mastercardは、午前11時頃にMastercardが解決しました.

    公式のインシデント更新を自動翻訳しています。

    Documentation Center currently unavailable

    開始 2026年7月13日 13:26 UTC · 3h 20m

    Outage重大なインシデント
    影響を受けたコンポーネント
    docs.multisafepay.com
    1. 2026年7月13日 13: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日 16:46 UTCresolved

      This incident has been resolved.

    iDEAL performance issues identified at issuer ABN AMRO

    開始 2026年7月6日 14:43 UTC · 17m

    Issues軽微なインシデント
    影響を受けたコンポーネント
    Payments
    1. 2026年7月6日 14:43 UTCinvestigating

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

    2. 2026年7月6日 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

    開始 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日 16: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日 14:21 UTC · 3m

    Outage重大なインシデント
    影響を受けたコンポーネント
    APIPayments
    1. 2026年6月4日 14:21 UTCinvestigating

      We are currently investigating a drop in payment performance

    2. 2026年6月4日 14: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日 13:49 UTC · 48m

    Outage重大なインシデント
    影響を受けたコンポーネント
    MultiSafepay payment pagesAPIPayments
    1. 2026年5月27日 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. 2026年5月27日 13:56 UTCidentified

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

    3. 2026年5月27日 14: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日 14:37 UTCresolved

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

    5. 2026年5月28日 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

    開始 2026年5月20日 13:36 UTC · 7m

    Outage重大なインシデント
    影響を受けたコンポーネント
    Payments
    1. 2026年5月20日 13: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日 13: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日 13:44 UTCresolved

      The incident has been resolved outside of our infrastructure.

    Payment method performance degradation

    開始 2026年4月30日 23: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日 21:05 UTC · 8m

    Pending
    影響を受けたコンポーネント
    MultiSafepay appPayments
    1. 2026年4月30日 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. 2026年4月30日 21: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日 14:40 UTC · 7m

    Outage致命的なインシデント
    影響を受けたコンポーネント
    Payments
    1. 2026年3月25日 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. 2026年3月25日 14:43 UTCidentified

      The issue now looks contain to issuer Rabobank

    3. 2026年3月25日 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

    開始 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日 18:47 UTC · 9m

    Issues軽微なインシデント
    影響を受けたコンポーネント
    Payments
    1. 2026年2月9日 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. 2026年2月9日 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

    開始 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日 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.