Uptrue's independent monitoring tracked Barclays and Mastercard throughout the week of 20 April 2026. Barclays maintained 100% uptime with a 127ms average response time, while Mastercard recorded 0% uptime during the same period, though both services logged zero incidents in our monitoring.
- Barclays achieved 100% uptime vs. Mastercard's 0% uptime during monitoring period
- Barclays responded in an average of 127ms; Mastercard response data unavailable
- Both providers recorded zero incidents despite vastly different uptime measurements
- Data collected by Uptrue's independent monitoring service week of 20 April 2026
Uptime This Week
Barclays delivered perfect availability at 100% uptime throughout the week. Mastercard showed 0% uptime in Uptrue's monitoring, indicating the service was unreachable or unresponsive during the entire measurement period. This extreme discrepancy warrants investigation into network configuration, DNS resolution, or geographic monitoring endpoint factors.
Response Time
Barclays responded to monitoring requests in 127ms on average, well within acceptable thresholds for financial services. Mastercard response time data was unavailable, consistent with the 0% uptime reading—requests did not complete successfully enough to generate reliable latency metrics.
Incidents & Downtime
Neither provider triggered explicit incident detection in Uptrue's monitoring system despite Mastercard's complete unavailability. The zero-incident count suggests Uptrue's incident classification requires specific failure signatures that may differ from raw connectivity or response metrics. Mastercard's 0% uptime reading itself represents a critical condition requiring immediate remediation.
Which Should You Choose?
For current production traffic, Barclays' 100% uptime and 127ms response time demonstrate reliable availability. The Mastercard 0% reading requires verification before any service decisions—cross-check with alternative monitoring sources to confirm whether this reflects actual outage or monitoring endpoint misconfiguration.
All uptime, response time, and incident data is collected by Uptrue's independent monitoring infrastructure. HTTP checks run every 5 minutes. An incident is recorded only after 2+ consecutive failed checks. Uptrue is not affiliated with any monitored service. For corrections: reports@uptrue.io