DownForAI

Lindy.ai status: API, auth, latency & outage reports

Lindy.ai is operational right now. DownForAI checks Lindy.ai 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
467ms
p50 Network Latencyⓘ
765ms
p95 Network Latencyⓘ
0
Incidents (30d)

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

No agent runtime incidents have been tracked for Lindy.ai 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 35m ago · 1 monitored surface · 1 with 24 h latency data

Current Status

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

Having issues?

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

0reports in the last 24 hours

Surface Health

Lindy AI WebOperational
HTTP 200p50 467ms2h ago

Uptime — last 24h

100.0%

Network latency — last 20 probes

Loading…

What DownForAI can verify about Lindy.ai

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

Known error signatures

Common failure patterns and how to diagnose them

Provider details

Lindy builds AI employees ('Lindies') that automate email, meetings, CRM updates and phone calls from triggers, on credit-based plans. Lindies run in Lindy's cloud on third-party models and connected apps.

What we monitor
lindy.ai app — Builder
Agent runtime — Triggers and executions
Integrations — Gmail, calendars, CRMs, telephony
Ecosystem dependencies
Model providersConnected apps

Fallback alternatives

What to use if this service is down

Lindy is down
Relay.app, Zapier AI or Relevance AI (monitored on DownForAI) run comparable AI automations
Major migration

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.

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

Community Discussion

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

Still having issues with Lindy.ai?

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