Uptrue's independent monitoring of Barclays and Revolut during the week of 20 April 2026 reveals a stark contrast in accessibility. Barclays maintained 100% uptime with a 127ms average response time, while Revolut recorded 0% uptime during the monitoring period. Both services reported zero confirmed incidents, suggesting measurement or availability anomalies requiring further investigation.
- Barclays achieved 100% uptime with 127ms average response times
- Revolut recorded 0% uptime during the monitoring week
- No incidents were logged by either provider despite the uptime disparity
- Data collected via Uptrue's independent monitoring infrastructure
Uptime This Week
Barclays demonstrated consistent availability at 100% throughout the monitored period. Revolut's 0% uptime metric indicates the service was unreachable from Uptrue's monitoring endpoints during this week. The disconnect between zero recorded incidents and zero uptime suggests potential network routing, DNS resolution, or endpoint accessibility issues rather than declared service incidents.
Response Time
Barclays responded with an average latency of 127ms, indicating normal operational performance. Revolut response time data was unavailable due to the service being inaccessible during monitoring.
Incidents & Downtime
Neither provider reported maintenance windows or service incidents during the week of 20 April 2026. The absence of declared incidents paired with Revolut's complete inaccessibility warrants review of whether monitoring detected transient connectivity failures versus sustained outages.
Which Should You Choose?
Barclays is the clear choice for production dependencies requiring guaranteed availability during this period. If Revolut services are mission-critical, direct investigation with the provider is essential to clarify the accessibility gap between monitoring data and service status declarations.
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