Uptrue monitored two AI tools during the week of April 20, 2026: Civitai (civitai.com) and Perplexity (perplexity.ai). Civitai achieved 97.93% uptime with an average response time of 273ms, while Perplexity reported 0% uptime during the monitoring period. This stark difference reflects fundamentally different service availability levels across the AI tools category.
- Civitai maintained 97.93% uptime with only 2 incidents totaling 185 minutes of downtime
- Perplexity experienced complete unavailability (0% uptime) with no successful responses recorded
- Civitai's average response time of 273ms remained consistent throughout the week
- Data collected by Uptrue's independent monitoring infrastructure across all test intervals
Uptime This Week
Civitai demonstrated reliable service availability at 97.93% uptime, meaning the platform was accessible for nearly 98% of the monitoring period. Perplexity showed 0% uptime, indicating the service was unreachable from Uptrue's monitoring endpoints throughout the entire week. This 97.93 percentage-point gap represents a critical difference in operational reliability.
Response Time
Civitai responded to requests in an average of 273ms, indicating reasonable performance for image generation and model services. Perplexity response data was unavailable due to the 0% uptime status—no successful connections were established to measure latency. This prevented comparative analysis of response time performance.
Incidents & Downtime
Civitai experienced 2 discrete incidents during the monitoring week, with combined downtime of 185 minutes (approximately 3 hours). Perplexity registered 0 incidents despite total unavailability, suggesting either continuous outage rather than discrete incidents or monitoring endpoint access restrictions. The incident profile indicates Civitai's downtime was episodic rather than persistent.
Which Should You Choose?
Choose Civitai for production workloads requiring consistent availability—its 97.93% uptime makes it suitable for non-critical integrations, though the 185 minutes of downtime warrants monitoring for time-sensitive applications. Perplexity should not be selected for any availability-dependent use cases based on this monitoring period's data. Implementation choice should account for the 2.07% potential downtime window.
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