DeepMind (deepmind.google) and Perplexity (perplexity.ai) were monitored independently by Uptrue during the week of 20 April 2026. DeepMind delivered 99.59% uptime with a 216ms average response time, while Perplexity showed 0% uptime with no response data available.
- DeepMind achieved 99.59% uptime with only one incident causing 30 minutes of downtime
- Perplexity showed 0% uptime during the monitoring period with no successful responses recorded
- DeepMind maintained a 216ms average response time when operational
- The uptime gap between providers represents a critical difference for production workloads
Uptime This Week
DeepMind maintained 99.59% uptime over the monitoring period, translating to approximately 30 minutes of unavailability during the week. Perplexity recorded 0% uptime, indicating either complete service unavailability or connectivity failures that prevented successful responses throughout the monitoring window. This substantial disparity highlights fundamentally different reliability profiles.
Response Time
DeepMind's average response time of 216ms falls within acceptable ranges for most AI tool applications. Perplexity response time data was unavailable due to the 0% uptime reading, preventing comparative latency analysis.
Incidents & Downtime
DeepMind experienced a single incident responsible for the 30-minute downtime window. Perplexity reported zero incidents but maintained zero uptime, suggesting the monitoring could not establish successful service contact rather than incident-free operation. The distinction is significant: DeepMind's single incident is isolated and measurable, whereas Perplexity's status indicates pervasive availability issues.
Which Should You Choose?
DeepMind is the reliable choice for production dependencies, with 99.59% uptime and a single incident establishing predictable failure patterns. Perplexity should not be considered for mission-critical applications until sustained uptime is demonstrated. Engineers requiring redundancy should prioritize DeepMind or seek additional backup providers.
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