Uptrue's independent monitoring tracked Perplexity and Writesonic during the week of 27 April 2026. Writesonic delivered 99.9% uptime with a 185ms average response time, while Perplexity reported 0% uptime in our monitoring data despite claims of operational status on its official status page.
- Writesonic achieved 99.9% uptime; Perplexity showed 0% uptime in Uptrue monitoring
- Writesonic averaged 185ms response time; Perplexity response data unavailable
- Both providers reported zero incidents and zero minutes of downtime in their official channels
- Significant discrepancy between Perplexity's official status page (claiming 100% uptime) and Uptrue's independent measurements
Uptime This Week
Writesonic maintained 99.9% uptime throughout the monitoring period, meeting typical SLA standards for production services. Perplexity's 0% uptime reading from Uptrue's independent monitoring contradicts its official status page, which claims 100% website uptime and 99.96% API uptime over the past 90 days. This substantial discrepancy warrants investigation into monitoring methodology or service accessibility differences.
Response Time
Writesonic responded to requests in an average of 185ms, indicating stable performance under typical traffic conditions. Perplexity response time data was unavailable during the monitoring period, likely correlating with the 0% uptime measurement.
Incidents & Downtime
Both providers' official status pages reported zero incidents and zero total downtime minutes during the period. However, Uptrue's independent measurements for Perplexity diverge significantly from this reporting, suggesting either partial service degradation not captured in incident logs or detection of access issues not reflected in official channels. Writesonic's metrics aligned consistently with its status page reporting.
Which Should You Choose?
Writesonic is the reliable choice for this period based on Uptrue's independent data, with verified 99.9% uptime and responsive performance. Perplexity users should seek clarification on the monitoring discrepancy before committing to production workloads, or wait for additional monitoring cycles to establish patterns.
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