Live

Map and location search issues in some published projects

Map and location search issues in some published projects have been resolved. We have pushed a fix so that projects using location search are guided to the working setup, and if your project is still affected you can ask the Lovable agent to fix it and it will apply the update for you. All systems are operating normally.

The latest update from Lovable.

State

Resolved

Started

Lasted

3 h 25 min

Worst impact

Degraded

Timeline

3 updates
13:2914:2015:1216:0316:54
DegradedUpdate postedTimes in UTC

Investigating

3 h 25 min 100%

Updates

Times in UTC

As posted by Lovable

Resolved

Map and location search issues in some published projects have been resolved. We have pushed a fix so that projects using location search are guided to the working setup, and if your project is still affected you can ask the Lovable agent to fix it and it will apply the update for you. All systems are operating normally.

Investigating

Some published projects that use our maps connector for map and location search features may temporarily not load results correctly, for example place lookups or location images. Only projects using the maps connector are affected. This is a temporary measure while we investigate, and we will share an update as soon as we have more.

Investigating

Some published projects that use map and location search features may temporarily not load results correctly, for example place lookups or location images. Projects that use our built-in maps connector are not affected. We will share an update as soon as we have more information.

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

3.6× 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

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane