Affected components
Update timeline
- investigating Feb 14, 2026, 01:57 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
- investigating Feb 14, 2026, 02:07 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
- resolved Feb 14, 2026, 02:37 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.
- resolved Feb 14, 2026, 02:42 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.
Looking to track JudoPay downtime and outages?
Pingoru polls JudoPay's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when JudoPay reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track JudoPay alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required