Lovable outage history

Lovable experienced degraded connectivity to external AI assistants, beginning at 1:49 PM UTC. The issue prevented some users from linking Lovable to external AI assistants, impacting automation and live interactions. The Lovable MCP component entered a degraded state as engineers investigated the root cause.

Over the afternoon, a fix was identified and deployed. A targeted fix was rolled out around 4:24 PM UTC, and Lovable MCP returned to full operation by 4:49 PM UTC. The incident lasted roughly three hours with ongoing monitoring after restoration.

Lovable experienced a brief login outage starting at 2:14 PM UTC, with sign-in via social providers (Google, GitHub, and other SSO options) unavailable for some users. This prevented authentication and access to Lovable features that require logging in. User reports began around 1:45 PM UTC, including a Lisbon user noting Google login failures at 2:28 PM UTC.

Engineering investigated and restored sign-in by 2:29 PM UTC, with the login service returning to normal shortly after. The incident lasted roughly fifteen minutes and primarily affected the authentication flow rather than the entire platform.

Impact began at 4:54 PM UTC when Lovable flagged increased errors in the Lovable MCP, traced to an upstream provider. Users relying on Lovable MCP experienced degraded performance and intermittent failures as requests routed through that component were affected.

The issue was resolved by 5:44 PM UTC, with Lovable returning to normal as the upstream provider's problem was resolved. The incident persisted for about 50 minutes.

A brief incident affected access to the Lovable dashboard, lasting from 2:44 PM UTC to 2:54 PM UTC. During this window, users could not reach the Lovable Dashboard, and the Lovable Website status was listed as a reported issue with the team actively investigating. The issue appeared isolated to the Lovable Website and was resolved when the status returned to up by 2:54 PM UTC. Overall impact was limited, with no clear regional pattern and only modest user feedback observed.

Users attempting to create Lovable cloud projects faced errors as the Cloud component entered a degraded state, impacting new project workflows. The issue appeared limited to the project-creation path and did not report broader service disruption.

The incident began at 1:14 AM UTC and was resolved by 3:04 AM UTC, lasting about two hours. Lovable’s status page noted that the upstream provider identified the root cause and is actively applying a fix, with ongoing monitoring and a follow-up update as more details become available.

Users attempting to create Lovable cloud projects in the Americas faced an elevated error rate and increased latency, while APAC and EMEA were unaffected and some creations still completed. The issue began at 10:49 PM UTC and was resolved by 12:49 AM UTC. Lovable's Cloud component was listed as degraded during the incident, and the team said they were investigating with their vendor and monitoring recovery on the project-creation error ratio.

Lovable experienced errors in image generation that affected some user requests, impacting the Editor component. The disruption began at 10:49 PM UTC as a provider issue surfaced and the team started routing requests through backup systems to keep image generation working while a permanent fix was pursued.

A fix was applied and monitoring began at 11:09 PM UTC, with the Editor component returning to normal operation by 11:14 PM UTC. The event lasted around 25 minutes, after which image generation capability was restored.

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.