Live

Issues with image and video generation

0

Image and video generation did not work for some users on Lovable. File and document storage in projects was also reported as affected. Lovable reports that the issue is resolved and that it lasted 38 minutes.

State

Resolved

Started

Lasted

38 min

Worst impact

Degraded

Timeline

5 updates
17:5918:0818:1818:2718:37
DegradedUpdate postedTimes in UTC

Investigating

31 min 82%

Monitoring

7 min 18%

Updates

Times in UTC

As posted by Lovable

Resolved

This should now be resolved. Thank you for your patience.

Monitoring

The issue that affected image and video generation as well as documents and files should now be resolved. We’ll continue to monitor the situation. Thank you for your patience.

Investigating

Some users are currently having problems with generating images and videos. The agent may fail generating these assets or work without access to uploaded documents. Our team is investigating.

Investigating

Some users are currently having problems with generating images and videos. This may also affect file and document storage in their project. The agent may fail generating these assets or work without access to uploaded documents. Our team is investigating.

Investigating

Some users are currently having problems with generating images and videos as well as file and document storage in their projects. The agent may fail generating these assets or work without access to uploaded documents. Our team is investigating.

Lovable in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

31

Days with an incident

25

Median duration

58 min

This incident

35% shorter than the median

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

3 h 51 min
median 58 min
90 days agoToday

Other Lovable incidents

All incidents

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