Project previews failing to load or loading slowly for some users
Project previews fail to load, load slowly, or appear blank for some Lovable users, mainly in the New York and New Jersey area. Previews load normally again, and Lovable monitors the system to keep it stable.
State
Monitoring
Started
Ongoing for
1 h 14 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
1 h 2 min 84%
Monitoring
11 min 16%
Updates
Times in UTCAs posted by Lovable
Project previews are loading normally again. The issue caused previews to fail or load slowly for some users, mainly in the New York and New Jersey area. We are monitoring to make sure everything stays stable.
Some users are experiencing issues with project previews, including previews failing to load, loading slowly, or appearing blank. Our team is investigating and working to restore normal preview functionality as quickly as possible.
Some users are experiencing issues with project previews, including previews failing to load, loading slowly, or appearing blank. Our team is investigating and working to restore normal preview loading as quickly as possible.
Lovable in the last 90 days
Full historyIncidents in 90 days
26
Days with an incident
20
Median duration
57 min
This incident
1.3× the median
Other Lovable incidents
All incidentsLovable·Some Lovable Cloud apps unable to reach backend
This incident has been resolved.
Lovable·Chat and project changes are currently failing for some users
This incident has been 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.
Lovable·Enabling Lovable Cloud on projects is currently failing for some users
This incident has been resolved.
Lovable·Lovable is slow at answering
Service is returning to normal. Any delayed messages should be handled within 10-20 minutes at most.
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.
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.
https://outages.live/feed.xml?providers=lovable/feed subscribe https://outages.live/feed.xml?providers=lovableFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane