Incidents and maintenance reported on status page for Lleverage https://status.lleverage.ai/ https://d1lppblt9t2x15.cloudfront.net/logos/efdb90736b7fd0f38fa0f762cc883105.png https://status.lleverage.ai/ en https://status.lleverage.ai/incident/1095450 Tue, 20 Oct 2026 14:49:30 -0000 https://status.lleverage.ai/incident/1095450#b592ab041ee2be83f78b06269db8c3a1a8638113bafa9e503b6b172ec6d3aca4 Incident 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. https://status.lleverage.ai/incident/1095450 Tue, 20 Oct 2026 10:16:34 -0000 https://status.lleverage.ai/incident/1095450#365ed7d95cd985a655c04d5e9bb90b718c8bcafdb8820606bfa78e4ebf1e23c7 Incident Update: The app, workflows and AI steps have been working normally since 09:43 CEST. Still affected: email notifications and alerts are not being sent yet. We're working on restoring them and will post an update as soon as they're back. https://status.lleverage.ai/incident/1095450 Tue, 20 Oct 2026 07:55:49 -0000 https://status.lleverage.ai/incident/1095450#1bc662197131e43f84c0d884cf05ae11c0481e03d1fbf4a01547ffb6a07675d9 Incident Lleverage is mostly working again, but some services are still recovering. What works: You can log in and use the app as normal, and workflows are running again. What's still affected: Notifications are not being sent yet, so you may not receive alerts or emails about workflow runs for now. They will resume once the service is fully restored. Google Cloud is still stabilising some of its databases, so you may occasionally see a slow response or a brief error. If so, please try again. We'll post another update once everything is fully restored. https://status.lleverage.ai/incident/1095450 Tue, 20 Oct 2026 07:33:22 -0000 https://status.lleverage.ai/incident/1095450#16cf1645ba883ddb46df79fadd77c8ca8b6c475a15118ea62507987788b741d6 Incident 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. https://status.lleverage.ai/incident/1095450 Tue, 20 Oct 2026 06:16:35 -0000 https://status.lleverage.ai/incident/1095450#843d5c96d37581fc47994a2b5ab7a7aebabd4243e1c5606897f294afb72ffc9b Incident Since around 08:00 CEST, some requests to the Lleverage app are returning errors, and workflow steps that use AI models are failing or timing out. Our team has identified the affected service and is working on a fix. We'll post an update here as soon as we know more. https://status.lleverage.ai/incident/965783 Thu, 16 Jul 2026 10:13:17 -0000 https://status.lleverage.ai/incident/965783#a22d0371ea3231910ddf5305ed8dab1146a6d50b92ead3709dc6b6d69e43577c Incident The upstream authentication provider has resolved their incident and sign-in performance has returned to normal. Authentication requests are completing in well under a second again and we are seeing no further timeouts. This incident is resolved. https://status.lleverage.ai/incident/965783 Thu, 16 Jul 2026 08:17:53 -0000 https://status.lleverage.ai/incident/965783#2031f3193da0452225a148bfd12a3063b24730e227c01935f3dce6f51581d756 Incident Our upstream authentication provider (WorkOS) is experiencing an ongoing incident with elevated API latency and timeouts. New sign-ins may load slowly, show a spinner, or fail with a gateway timeout. Users with an active session are largely unaffected, though session refreshes may occasionally be slow. The Lleverage platform itself is healthy and workflow execution is unaffected. We are monitoring the upstream incident and will post updates here as it progresses.