Live

Lovable

Lovable is operational

Checked Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Lovable status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Lovable since . The days before that show only what Lovable published.

Incidents in 90 days

25

Days with an incident

19

Median duration

57 min

Longest incident

3 h 51 min

Components

10
Website Operational
90 days agoNo incidentsToday
Login Operational
90 days agoNo incidentsToday
Editor Operational
90 days agoNo incidentsToday
Published customer sites Operational
90 days agoNo incidentsToday
Preview links Operational
90 days agoNo incidentsToday
Cloud Operational
90 days agoNo incidentsToday
API Operational
90 days agoNo incidentsToday
MCP Operational
90 days agoNo incidentsToday
Desktop Operational
90 days agoNo incidentsToday
Mobile Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

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.cc/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.cc/feed.xml?providers=lovable
Slack
/feed subscribe https://outages.cc/feed.xml?providers=lovable

Go from tracking outages to fixing production issues with Polylane.

Try Polylane