Lovable outage history

An outage affected Lovable's Cloud project creation, preventing some users from creating new projects. The issue began at 4:14 PM UTC and impacted the Cloud component as engineers investigated the root cause. A fix was identified and rolled out, with the Cloud component returning to normal by 5:34 PM UTC. The disruption lasted roughly an hour and twenty minutes before services were restored.

Lovable users were unable to chat as the Editor component failed. The outage began at 2:24 PM UTC with chats not working, and early user reports appeared around 2:15 PM UTC describing internal errors and requests not being processed. The impact appeared global, affecting the chat experience and editor functionality for a period of time.

Status updates show the issue progressing from outage to degraded service before full restoration. The Editor moved from down to degraded at 2:44 PM UTC and a partial fix was attempted at 2:59 PM UTC. A full recovery followed by 3:09 PM UTC, after which chats and the Editor returned to normal operation.

Users attempting to connect new custom domains to Lovable encountered failures during provisioning, with new domain setup and retries failing. The issue did not affect sites already running on active custom domains, which continued to load normally. The incident began at 12:49 AM UTC and was resolved by 1:04 AM UTC when Lovable restored the ability to set up new custom domains, lasting about 15 minutes.

Users of Lovable experienced a brief disruption affecting the Editor's preview builds, with build failures reported for some projects. The incident began around 7:19 AM UTC as Lovable flagged issues and the Editor component showed a degraded state. The impact appeared limited to preview builds in the editor, not applying to other workflows.

By 7:59 AM UTC, the status page indicated the spike was returning toward normal and the impact remained confined to Editor previews. A final update at 8:39 AM UTC confirmed the Editor component had returned to normal, with Lovable continuing to monitor and implement changes to reduce the chance of recurrence. The full incident lasted about 1 hour 20 minutes.

Users began encountering elevated build errors starting at 9:59 AM UTC, with Lovable's Editor and the live preview affected as builds could fail or display errors for some users. The issue appeared to be limited to the Editor component and related preview functionality, rather than a full service outage.

The Lovable team investigated and worked to restore normal behavior. By 10:24 AM UTC, the Editor had recovered and normal live preview operation resumed, marking an incident that lasted roughly 25 minutes.

Lovable briefly experienced a display issue in the billing UI where some customers' credit balances appeared as 0 even though credits remained. The problem began when Lovable moved to a warning state at 2:54 PM UTC with the note Credits not showing and was resolved a few minutes later when the status returned to normal at 2:59 PM UTC. The incident affected the credits display component and could have caused confusion about remaining credits, but there was no broader impact to account access or transactions. The status page indicated an ongoing investigation and later restoration of normal service.

Lovable reports an ISP-level network connectivity problem in the India region that prevents access to Lovable Cloud projects. The issue is not caused by Lovable's infrastructure, which remains operational, but by connectivity blocks imposed by Indian internet service providers. Affected users are advised to use a VPN or switch their DNS to 1.1.1.1 as a workaround.

The incident began at Feb 26, 2026 4:19 PM UTC when Lovable moved from up to warn status. The issue appears regional to India, with user reports starting around 5:45 PM UTC and continuing, indicating ongoing impact for customers attempting to reach Lovable Cloud projects from affected networks. Lovable's status updates note that the problem lies outside Lovable's infrastructure and that services themselves remain operational; no estimated resolution time is available yet.

Lovable experienced an API outage that disabled core platform features for Editor, Website, and Login, preventing users from logging in or accessing projects. An Early Warning Signal flagged login and database issues affecting access to projects from 8:55 AM UTC to 9:37 AM UTC. StatusGator detected the issue at Feb 26, 2026 8:55 AM UTC, about 9 minutes before Lovable posted its first official update. The outage began at 9:04 AM UTC and persisted until 9:59 AM UTC, with restoration of Editor, Website, and Login by that time.

Overall, there were 22 user reports during the incident, indicating a broad impact reported from many regions. Lovable issued 3 status updates describing technical difficulties with the API and degraded access. By 09:59 UTC, all listed components were back online, and normal service resumed. The outage lasted roughly 55 minutes and is characterized as a major disruption due to the impact on multiple core components.

Lovable experienced a cloud provider incident that degraded logs and observability across all cloud-based projects. This affected monitoring, troubleshooting, and visibility into Lovable services. The issue began at 8:49 PM UTC and was resolved by 12:04 AM UTC, lasting about 3 hours and 15 minutes.

Two official status updates were posted during the incident: the Cloud component moved from up to warn as the cloud provider issue began, and later returned to up when the provider resolved the incident. The outage appears to have been global, impacting all cloud-based projects.

Lovable experienced cloud connectivity problems that affected a subset of projects, with some projects failing to restart. The incident began at Feb 19, 2026 8:44 PM UTC and was resolved by Feb 19, 2026 9:44 PM UTC. User reports started around 7:45 PM UTC before Lovable publicly acknowledged the issue, indicating early visibility from users. The impact was limited to the Cloud component and produced degraded performance rather than a full outage. The provider posted two updates during the incident.