outages.live
Live
LovableIncident ·

Degraded performance when enabling Lovable Cloud

ResolvedOfficial update

Enabling Lovable Cloud has resumed to normal success rates.

The latest update from Lovable.

State

Resolved

Started

Lasted

2 h 14 min

Worst impact

Degraded

Timeline

3 updates
19:1219:4620:1920:5321:27
DegradedUpdate postedTimes in UTC

Investigating

25 min 19%

Monitoring

1 h 49 min 81%

Updates

Times in UTC

As posted by Lovable

Resolved

Enabling Lovable Cloud has resumed to normal success rates.

Monitoring

We're seeing Lovable Cloud enablement back to full success rates and will monitor to confirm that it remains stable.

Investigating

We're seeing elevated error rates for projects enabling Lovable Cloud and are actively investigating.

Lovable in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

25

Days with an incident

19

Median duration

57 min

This incident

2.4× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

3 h 51 min
median 57 min
90 days agoToday

Other Lovable incidents

All incidents

Lovable·Some Lovable Cloud apps unable to reach backend

This incident has been resolved.

Resolved

Lovable·Chat and project changes are currently failing for some users

This incident has been resolved

Resolved

Lovable·Some users may see errors when setting up a database or backend for a new project, or when remixing a project.

Some users may see errors when setting up a database or backend for a new project, or when remixing a project. Our team is investigating.

Resolved

Lovable·Enabling Lovable Cloud on projects is currently failing for some users

This incident has been resolved.

Resolved

Lovable·Lovable is slow at answering

Service is returning to normal. Any delayed messages should be handled within 10-20 minutes at most.

Resolved

Follow Lovable

Your coding agent knows when Lovable is down, and tells you when a failure is theirs, not yours. You can also get Lovable incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "lovable" and tell me if Lovable has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=lovable
Slack
/feed subscribe https://outages.live/feed.xml?providers=lovable

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane