DownForAI

Salad status: API, auth, latency & outage reports

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

Operational
Last probe 2h ago·1 surface
Probe-monitoredLow confidence
📚 Docs →💳 Pricing →
100.0%
24h Uptime
108ms
p50 Network Latencyⓘ
287ms
p95 Network Latencyⓘ
0
Incidents (30d)

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

No infrastructure incidents have been tracked for Salad since monitoring began, and no community reports were submitted in the last 24 hours. Automated checks continue on the configured schedule.

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

Current Status

✅
Operational
Everything works normally
✓Checked by our probes · 80ms
Verified 2h ago
✓No major incident reported
ⓘNo reports in the last 24h

Having issues?

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

0reports in the last 24 hours

Surface Health

Salad WebOperational
HTTP 200p50 108ms2h ago

Uptime — last 24h

100.0%

Network latency — last 20 probes

Loading…

What DownForAI can verify about Salad

No confirmed provider-side issue detected
DownForAI currently sees Salad 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 Salad in the last 24 hours.

Known error signatures

Common failure patterns and how to diagnose them

Provider details

SaladCloud runs containers on a distributed network of consumer GPUs at low prices, suited to batch inference that tolerates node churn. Failures are inherent to the model: nodes leaving mid-job, slow allocation and variable performance.

What we monitor
SaladCloud portal / API — Container groups
Distributed GPU network — Consumer nodes

Fallback alternatives

What to use if this service is down

SaladCloud cannot allocate
Vast.ai or RunPod (monitored on DownForAI) offer low-cost GPU capacity with more predictable nodes
Moderate effort

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.

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

Community Discussion

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

Still having issues with Salad?

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