Degraded Lovable Cloud project creation
Lovable Cloud project creation had degraded performance in the US-West-2 region. Lovable reports that the vendor's upstream provider made changes and the service is recovering. The incident is resolved and lasted 1 hour and 21 minutes.
State
Resolved
Started
Lasted
1 h 21 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
1 h 21 min 100%
Updates
Times in UTCAs posted by Lovable
Our vendor reports that its upstream provider has implemented changes and project creation in US-West-2 is recovering.
Some users may experience errors when creating new Lovable Cloud projects. Our vendor is experiencing degraded performance in its US-West-2 region. We are investigating the impact on project creation.
Lovable in the last 90 days
Full historyIncidents in 90 days
27
Days with an incident
21
Median duration
58 min
This incident
1.4× the median
Other Lovable incidents
All incidentsLovable·Project previews failing to load or loading slowly for some users
Lovable project previews failed to load or loaded slowly for some users, mainly in the New York and New Jersey area. Lovable reports that the issue is resolved. The outage lasted 95 minutes.
Lovable·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.
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.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.
https://outages.cc/feed.xml?providers=lovable/feed subscribe https://outages.cc/feed.xml?providers=lovableFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane