This week's monitoring data reveals a critical reliability gap between two banking and finance providers. Starling Bank maintained 100% uptime with an average response time of 357ms, while Mastercard recorded 0% uptime during the monitoring period of 20 April 2026. Both providers reported zero incidents, though Mastercard's zero uptime reading indicates a fundamental accessibility issue.
- Starling Bank: 100% uptime vs Mastercard: 0% uptime (week of 20 April 2026)
- Starling Bank response time averaged 357ms; Mastercard data unavailable
- Both providers reported zero downtime incidents, but Mastercard showed no availability
- Neither provider offers a public status page for real-time incident communication
Uptime This Week
Starling Bank achieved 100% availability throughout the monitoring period, demonstrating consistent platform accessibility. Mastercard's 0% uptime reading suggests complete unavailability to external monitoring during this week. This disparity represents a significant reliability differential, with Starling Bank providing uninterrupted service access.
Response Time
Starling Bank's average response time of 357ms falls within acceptable ranges for banking infrastructure. Mastercard response time data was unavailable due to the 0% uptime condition, preventing comparative analysis of performance metrics.
Incidents & Downtime
Both providers recorded zero confirmed incidents during the monitoring period. However, Mastercard's complete unavailability to monitoring suggests either infrastructure changes, network routing issues, or monitoring endpoint problems that warrant investigation separate from traditional incident reporting.
Which Should You Choose?
For mission-critical payment and banking operations, Starling Bank demonstrates immediate reliability based on this week's data. However, Mastercard's 0% reading requires clarification before drawing conclusions; contact their technical team to verify whether the monitoring endpoint reflects actual service status or represents a separate infrastructure issue.
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