JudoPay Outage History

JudoPay is up right now

JudoPay had 10 outages in the last 2 years totaling 398h 4m of downtime — averaging 0.4 incidents per month.

There were 10 JudoPay outages since October 29, 2025 totaling 398h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://judopay.statuspal.io

Minor September 3, 2026

Transaction Failures Observed

Detected by Pingoru
Sep 03, 2026, 05:19 PM UTC
Resolved
Sep 03, 2026, 05:29 PM UTC
Duration
9m
Affected: Gateway Only Transaction ProcessingJGW1 - Transactions
Timeline · 2 updates
  1. investigating Sep 03, 2026, 05:19 PM UTC

    We are currently investigating an issue affecting some transaction processing services. We apologise for any inconvenience caused. This has been observed for the following:WorldPay

  2. resolved Sep 03, 2026, 05:29 PM UTC

    Transaction processing has been restored to normal. We would like to take this opportunity to apologise again for any inconvenience this has caused.

Read the full incident report →

Major June 23, 2026

Worldpay Acquirer Degradation

Detected by Pingoru
Jun 23, 2026, 08:06 PM UTC
Resolved
Jun 23, 2026, 08:22 PM UTC
Duration
16m
Affected: General NotificationsGateway Only Transaction ProcessingJGW1 - TransactionsJGW2 - Latency
Timeline · 5 updates
  1. monitoring Jun 23, 2026, 08:06 PM UTC

    We are aware that some merchants processing through Worldpay may currently be experiencing latency, declines, or failed transactions. This issue is with Worldpay directly and is outside of Judopay’s systems — our platform is fully operational and functioning without issue. We recommend checking Worldpay’s status page for the latest updates: https://status.access.worldpay.com/ We will continue to monitor the situation and update this page as more information becomes available.

  2. investigating Jun 23, 2026, 08:14 PM UTC

    We are still experiencing issues with some transaction processing services and are continuing to investigate. We apologise for any inconvenience caused and hope to have the service restored to normal as soon as possible. We can assure you our operations team is working hard to resolve this issue as soon as possible. This has been observed for the following:WorldPay

  3. resolved Jun 23, 2026, 08:17 PM UTC

    The transaction latency issues have been restored to normal thresholds. We would like to take this opportunity to apologise again for any inconvenience this has caused.

  4. investigating Jun 23, 2026, 08:19 PM UTC

    We are still experiencing issues with some transaction processing services and are continuing to investigate. We apologise for any inconvenience caused and hope to have the service restored to normal as soon as possible. We can assure you our operations team is working hard to resolve this issue as soon as possible. This has been observed for the following:WorldPay

  5. resolved Jun 23, 2026, 08:22 PM UTC

    The transaction latency issues have been restored to normal thresholds. We would like to take this opportunity to apologise again for any inconvenience this has caused.

Read the full incident report →

Minor June 23, 2026

Transaction Latency

Detected by Pingoru
Jun 23, 2026, 08:02 PM UTC
Resolved
Jun 23, 2026, 08:12 PM UTC
Duration
10m
Affected: Gateway Only Transaction ProcessingJGW2 - Latency
Timeline · 2 updates
  1. investigating Jun 23, 2026, 08:02 PM UTC

    We have noticed that some transactions have exceeded latency thresholds and are currently investigating the issue. We apologise for any inconvenience caused. This has been observed for the following:WorldPay

  2. resolved Jun 23, 2026, 08:12 PM UTC

    The transaction latency issues have been restored to normal thresholds. We would like to take this opportunity to apologise again for any inconvenience this has caused.

Read the full incident report →

Minor June 16, 2026

3DS2 Auth failures observed in Sandbox environment

Detected by Pingoru
Jun 16, 2026, 12:28 PM UTC
Resolved
Jun 16, 2026, 03:39 PM UTC
Duration
3h 11m
Affected: Payment ServicesSandbox3rd Party 3DS2 Sandbox
Timeline · 6 updates
  1. investigating Jun 16, 2026, 12:28 PM UTC

    We are currently experiencing 3rd party issues with the 3DS2 authorisation in our Sandbox environment and are continuing to investigate with our Partners. We apologise for any inconvenience caused and hope to have the service restored to normal as soon as possible. Live transactions processing are not being affected.

  2. investigating Jun 16, 2026, 02:04 PM UTC

    We are still experiencing issues with the Sandbox environment and are continuing to investigate. We apologise for any inconvenience caused and hope to have the service restored as soon as possible.

  3. investigating Jun 16, 2026, 03:04 PM UTC

    We are still experiencing issues with the Sandbox environment and are continuing to investigate. We apologise for any inconvenience caused and hope to have the service restored as soon as possible.

  4. monitoring Jun 16, 2026, 03:10 PM UTC

    We are seeing 3DS2 frictionless authorisations running successfully in our Sandbox environment and are continuing to investigate challenges with our Partners. We apologise for any inconvenience caused and hope to have the service restored to normal as soon as possible. Live transactions processing are not being affected.

  5. resolved Jun 16, 2026, 03:38 PM UTC

    3DS2 authentications are now back to normal. We apologise for any inconvenience caused.

  6. investigating Jun 16, 2026, 04:04 PM UTC

    We are still experiencing issues with the Sandbox environment and are continuing to investigate. We apologise for any inconvenience caused and hope to have the service restored as soon as possible.

Read the full incident report →

Minor January 5, 2026

Issues with API endpoints documentation

Detected by Pingoru
Jan 05, 2026, 11:55 AM UTC
Resolved
Jan 12, 2026, 11:56 AM UTC
Duration
7d
Affected: General Notifications
Timeline · 2 updates
  1. investigating Jan 08, 2026, 11:55 AM UTC

    Some users may notice that API endpoints documentation located at https://docs.judopay.com/api-reference are not loading or rendering correctly in our documentation portal. This is due to a technical issue with our third-party documentation provider following a recent library update. We are working closely with our technology partner to resolve the display issues. We will provide a further update once the API documentation portal is fully restored and apologize for the inconvenience.

  2. resolved Jan 12, 2026, 11:56 AM UTC

    Our partner has now confirmed they have implemented a fix and the issue has now been mitigated. The API documentation page is now fully functional. We apologise for any inconvenience caused and appreciate your patience while our partner completes their investigation.

Read the full incident report →

Minor November 18, 2025

3DS2 Authentication Failures Observed

Detected by Pingoru
Nov 18, 2025, 02:58 PM UTC
Resolved
Nov 18, 2025, 04:37 PM UTC
Duration
1h 38m
Affected: General Notifications
Timeline · 2 updates
  1. monitoring Nov 18, 2025, 12:00 PM UTC

    Currently we are observing that some card issuers are experiencing ongoing problems with processing 3D Secure 2 authentication challenge flows. This is resulting in a higher rate of failed authentication attempts with the majority seen on Visa/Mastercard. We have established this is occurring external to Judopay and we are aware that this is actively being investigated by the card issuers 3DS Authentication & Technology partners - possible cause suggest this may be related to the ongoing global Cloudflare outage impacting multiple networks and services worldwide. Please accept our apologies for any inconvenience this external issue may be causing.

  2. resolved Nov 18, 2025, 04:37 PM UTC

    We’ve received confirmation from our technical partners that the issue has now been fully resolved. 3DS2 challenge flows are operating as expected, and no further impact is observed. We’ll continue to monitor, but no action is required at this time.

Read the full incident report →

Minor November 16, 2025

Apple Pay Payments through Webpayments

Detected by Pingoru
Nov 16, 2025, 03:00 AM UTC
Resolved
Nov 16, 2025, 09:22 PM UTC
Duration
18h 22m
Affected: General Notifications
Timeline · 4 updates
  1. investigating Nov 16, 2025, 10:12 AM UTC

    We’re seeing issues affecting Apple Pay payments through our Web Payments service. Our systems are operating normally, and the behaviour appears to be originating on Apple’s side. We’ve escalated this with our technical partner and will share further updates as soon as we have more detail. In the meantime, please use an alternative payment method. We’re sorry for the inconvenience.

  2. investigating Nov 16, 2025, 03:49 PM UTC

    Our engineers are continuing to investigate the issue and are working closely with our technology partners to identify the root cause. WebPayments by card remain fully operational. We apologise for the disruption and will provide further updates as soon as we have progress.

  3. investigating Nov 16, 2025, 07:40 PM UTC

    Our engineers believe they’ve identified the root cause and are now applying a fix. The issue is limited to Apple Pay on WebPayments — all standard card payments remain fully operational. We’ll share another update once the fix has been deployed.

  4. resolved Nov 16, 2025, 09:22 PM UTC

    Our engineers have identified the root cause and successfully deployed a fix. Apple Pay on Web Payments is now fully operational. Thanks for your patience while we worked through this.

Read the full incident report →

Minor November 5, 2025

Elevated Transaction Latency (Barclays Acquirer)

Detected by Pingoru
Nov 05, 2025, 12:30 PM UTC
Resolved
Nov 05, 2025, 04:50 PM UTC
Duration
4h 20m
Affected: General Notifications
Timeline · 2 updates
  1. investigating Nov 05, 2025, 03:13 PM UTC

    We are aware of increased transaction response times impacting processing through the Barclays acquirer on gateway JGW2. Our gateway partner has identified the issue and is actively investigating. Judopay’s systems remain fully operational and are processing transactions as normal. We will provide further updates as soon as more information becomes available.

  2. resolved Nov 05, 2025, 04:50 PM UTC

    As of 15:30 GMT response times have returned to acceptable thresholds for transactions routed through to the Barclays acquirer on gateway JGW2. Our gateway partner continues to monitor performance to ensure stability. Judopay’s systems have remained fully operational throughout, however we would like to apologise for any inconvenience caused during this incident.

Read the full incident report →