Chase and Starling Bank both maintained perfect uptime during the monitoring period of 20 April 2026, each recording 100% availability with zero incidents. However, Chase delivered noticeably faster response times, averaging 277ms compared to Starling Bank's 355ms.
- Chase and Starling Bank both achieved 100% uptime with zero incidents during the week of 20 April 2026
- Chase's average response time of 277ms was 78ms faster than Starling Bank's 355ms
- Neither provider experienced any measurable downtime during the monitoring period
- Response time difference suggests Chase may provide a better user experience for time-sensitive transactions
Uptime This Week
Both providers demonstrated flawless availability during this monitoring period. Chase and Starling Bank each sustained 100% uptime with zero recorded incidents or downtime events. This perfect performance reflects robust infrastructure across both banking platforms.
Response Time
Chase responded to requests significantly faster, with an average response time of 277ms versus Starling Bank's 355ms. The 78ms difference—approximately 22% faster—could impact user experience during peak transaction volumes. Both providers remain within acceptable ranges for banking operations, though Chase's performance provides a measurable advantage.
Incidents & Downtime
Neither provider recorded any incidents or downtime during the week of 20 April 2026. The absence of disruptions indicates stable systems and effective monitoring across both platforms. This level of reliability is expected in the banking sector, where service continuity is critical.
Which Should You Choose?
Choose Chase if response speed is a priority, particularly for high-frequency trading or time-sensitive operations where the 78ms difference matters. For general banking needs where both providers deliver perfect availability, Starling Bank remains a viable choice; the decision should factor in other services, fees, and feature set alongside these performance metrics.
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