DownForAI

PearAI status: API, auth, latency & outage reports

PearAI is operational right now. DownForAI checks PearAI every ~75 minutes across 1 monitored surface, with 0 community reports in the last 24 hours.

Operational
Last probe 1h ago·1 surface
Probe-monitoredLow confidence
📚 Docs →
100.0%
24h Uptime
597ms
p50 Network Latency
1065ms
p95 Network Latency
0
Incidents (30d)

DownForAI monitors PearAI via a single endpoint — PearAI Web. Current status: operational — all surfaces are responding normally. Measured uptime over the last 24 hours: 100.0%. Median response time (24 h): 597 ms; p95: 1065 ms.

PearAI has had no tracked outages since joining the DownForAI monitoring network. No community reports have been filed in the last 24 hours.

Data confidence: LowLast checked 1h 29m ago · 1 monitored surface · 1 with 24 h latency data

Current Status

Operational
Everything works normally
Checked by our probes · 459ms
Verified 1h ago
No major incident reported
No reports in the last 24h

Having issues?

Help other users by reporting if PearAI is not working for you.

0reports in the last 24 hours

Surface Health

PearAI WebOperational
HTTP 200p50 597ms1h ago

Uptime — last 24h

100.0%

Network latency — last 20 probes

Loading…

What DownForAI can verify about PearAI

No confirmed provider-side issue detected
DownForAI currently sees PearAI as operational based on available monitoring signals.
Signal source: public surface check · Monitoring confidence: Low
Still having trouble?

The issue may be account-specific, regional, network-related, or related to authentication, billing, quota, or rate limits.

Incident history (30d)

No incidents recorded in the past 30 days.

Reported symptoms

No user reports for PearAI in the last 24 hours.

Known error signatures

Common failure patterns and how to diagnose them

Provider details

PearAI is an open-source AI code editor built on VS Code that bundles tools like Continue and Cline behind a single subscription and its own model router. Failures come from the router/backend or from the extensions it wraps, not from the editor binary.

Community channels
What we monitor
PearAI server / routerModel access for subscribers
trypear.aiWebsite and account
Bundled extensionsChat, agent and search features
Ecosystem dependencies
Third-party model providers behind the router
Operator notes
  • trypear.ai/docs answered 402 (hosting paused) when this entry was written; the docs link points to the main site.

Fallback alternatives

What to use if this service is down

PearAI's backend is down
Cursor or Continue (monitored on DownForAI) with your own API key provide the same editor workflow
Easy switch

How we monitor

DownForAI checks monitored AI service surfaces on a rotating schedule, roughly every 75 minutes per surface, from a single centralized probe infrastructure. For services with an official machine-readable status page, we use that official status signal when available. For other services, we perform a basic public-surface check. Some services block datacenter probes; in those cases we mark them as “Monitoring limited” instead of treating a failed probe as a confirmed outage. Status is classified as Operational, Degraded, or Outage. Network latency (check response time) measures how long the monitored endpoint took to respond to our probe — it is not model inference speed, time-to-first-token, or tokens-per-second performance. We are independent of all providers listed and receive no compensation to report any particular status.

PearAI statusEmbed this status badgeREADME · docs ▾
Markdown
[![PearAI status](https://downforai.com/api/badge/pearai.svg)](https://downforai.com/pearai)
HTML
<a href="https://downforai.com/pearai"><img src="https://downforai.com/api/badge/pearai.svg" alt="PearAI status" /></a>

Community Discussion

0/1000
No comments yet. Be the first to share your experience!

Still having issues with PearAI?

Let the community know and help others experiencing the same problem.