This report compares uptime and performance metrics for AutoTrader (autotrader.co.uk) and CarGurus (cargurus.com) across the week of 27 April 2026, based on continuous monitoring by Uptrue's independent infrastructure. CarGurus maintained 100% uptime with a 197ms average response time, while AutoTrader's monitoring data showed critical reliability issues during this period.
- CarGurus achieved 100% uptime; AutoTrader recorded 0% uptime during the monitoring period
- CarGurus maintained 197ms average response time with zero incidents
- Both providers reported zero total downtime minutes according to incident logs, indicating a significant data discrepancy for AutoTrader
- CarGurus publishes no official status page; AutoTrader maintains a status page but its accuracy requires verification
Uptime This Week
CarGurus demonstrated perfect availability at 100% uptime throughout the week. AutoTrader's 0% uptime metric indicates severe service degradation or monitoring detection issues during this period. The discrepancy between reported incidents (0) and the 0% uptime figure for AutoTrader suggests either monitoring anomalies or incomplete incident classification.
Response Time
CarGurus responded to requests with an average latency of 197ms, indicating solid performance within typical acceptable thresholds for automotive e-commerce platforms. Response time data was unavailable for AutoTrader, preventing comparative analysis on this dimension.
Incidents & Downtime
Both providers show zero recorded incidents in their official logs. However, AutoTrader's 0% uptime reading contradicts the zero-incident report, suggesting either undetected infrastructure failures or gaps in incident documentation. CarGurus' zero incidents align consistently with its 100% uptime metric.
Which Should You Choose?
CarGurus is the clear choice for production use during this period based on demonstrated 100% availability and consistent response times. AutoTrader requires immediate investigation of the 0% uptime metric before being considered reliable for critical integration, particularly given the conflicting incident data.
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