CarGurus delivered perfect uptime during the week of 20 April 2026, while AutoTrader experienced complete service unavailability. This stark contrast reflects significant operational differences between the two automotive platforms during the monitored period. CarGurus maintained consistent 200ms response times with zero incidents, whereas AutoTrader logged zero uptime across all monitoring checkpoints.
- CarGurus achieved 100% uptime vs. AutoTrader's 0% during the monitoring week
- CarGurus averaged 200ms response time; AutoTrader response data unavailable due to service unavailability
- Both platforms recorded zero incidents, but AutoTrader's 0% uptime indicates underlying systemic issues
- CarGurus maintained full availability across the entire monitoring period with no downtime events
Uptime This Week
CarGurus maintained 100% uptime throughout the week, with all monitoring checks succeeding across the period. AutoTrader registered 0% uptime, indicating the service was unreachable or non-responsive during the entire monitoring window. This disparity suggests AutoTrader faced fundamental infrastructure or availability issues during this timeframe.
Response Time
CarGurus delivered consistent 200ms average response times, indicating normal operational performance. AutoTrader response time data was unavailable due to complete service unavailability, preventing measurement of latency metrics.
Incidents & Downtime
Neither platform officially logged incidents during the monitoring period, though AutoTrader's 0% uptime classification suggests undetected or undocumented outages occurred. CarGurus recorded zero downtime events and zero incidents, correlating directly with its perfect uptime metric. The absence of reported incidents paired with measured unavailability indicates AutoTrader's situation may have gone unmonitored by internal systems.
Which Should You Choose?
CarGurus is the clear choice for this monitoring period based on measured reliability. AutoTrader should be avoided until investigation confirms restoration of service availability and underlying causes are resolved. Organizations dependent on either platform should establish independent uptime monitoring to catch future degradation.
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