JudoPay incident

Transaction Latency

Major Resolved View vendor source →

JudoPay experienced a major incident on February 14, 2026 affecting Gateway Only Transaction Processing and JGW2 - Latency, lasting 30m. The incident has been resolved; the full update timeline is below.

Started
Feb 14, 2026, 02:02 AM UTC
Resolved
Feb 14, 2026, 02:32 AM UTC
Duration
30m
Detected by Pingoru
Feb 14, 2026, 02:02 AM UTC

Affected components

Gateway Only Transaction ProcessingJGW2 - Latency

Update timeline

  1. investigating Feb 14, 2026, 02:02 AM 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:Barclays

  2. investigating Feb 14, 2026, 02:12 AM UTC

    We are still experiencing some issues with transaction latency and are continuing to investigate. We apologise for any inconvenience caused and hope to have latency restored to normal as soon as possible. This has been observed for the following:Barclays

  3. investigating Feb 14, 2026, 02:22 AM UTC

    We are still experiencing some issues with transaction latency and are continuing to investigate. We apologise for any inconvenience caused and hope to have latency restored to normal as soon as possible. This has been observed for the following:Barclays

  4. resolved Feb 14, 2026, 02:27 AM 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.

  5. resolved Feb 14, 2026, 02:32 AM 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.