Statusfield LogoStatusfield
Lleverage status
Lleverage logo and current status indicator

Lleverage Incident History

Operational

lleverage.ai ↗2 top-level components

checked Oct 23, 2026 5:21 AM UTC · Lleverage's official status page

Lleverage is up and running.

Lleverage is currently operational with all systems functioning normally.

All components operational

Be the first to know

Statusfield watches Lleverage alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.

30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.

Lleverage incident history

2 reports published by Lleverage in the last 30 days · 1 still open

When Lleverage breaks, it is typically resolved in 2h 3m — median across 3 resolved incidents over 30 days.

October 20, 2026

Degraded service: recovering from a Google Cloud database outage

Last update

  1. resolvedOct 20 · 14:49 UTC

    Everything is working normally again. Email notifications and alerts have been sending normally since 13:44 CEST, and the app, workflows and AI steps have worked normally since 09:43 CEST. Between about 08:00 and 09:43 CEST, parts of the app returned errors, AI steps failed, and some scheduled workflows and API calls did not run. Between 08:00 and 13:44 CEST, some email notifications and alerts were not sent, and others arrived late. If you rely on email alerts for failed runs, please check your run history for this morning and re-run any workflows that failed or did not run. We'll share a short write-up within 2 working days.

Reported by Lleverage on their status page.

Degraded service: AI steps and workflow runs failing

Ongoing · last update

  1. degradedOct 20 · 07:33 UTC

    Update: We’ve confirmed this is a wider issue caused by a database outage at Google Cloud, one of our infrastructure providers. As a result, parts of Lleverage are still unavailable or not working reliably. We’re working with Google to restore full service as quickly as possible, and we’ll post another update here as soon as we know more.

Reported by Lleverage on their status page.