Database creation failures in APAC
Lovable reports that some users cannot create databases for projects in the Asia-Pacific region. Lovable has identified the issue. The failures relate to an ongoing incident at the database provider that affects project creation in Tokyo.
State
Identified
Started
Ongoing for
36 min
Worst impact
Degraded
Timeline
1 updateIdentified
36 min 100%
Updates
Times in UTCAs posted by Lovable
Some users may be unable to create databases for projects in the Asia-Pacific region. The failures appear related to an ongoing incident with our database provider affecting project creation in Tokyo.
Lovable in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
22
Median duration
58 min
This incident
38% shorter than the median
Other Lovable incidents
All incidentsLovable·Degraded Lovable Cloud project creation
Lovable Cloud project creation did not work for some users. The vendor reported degraded performance in its US-West-2 region. Lovable reports that this incident is resolved. It lasted 81 minutes.
Lovable·Project previews failing to load or loading slowly for some users
Lovable reported that project previews failed to load or loaded slowly for some users, mainly in the New York and New Jersey area. Lovable monitored the fix and then reported the incident 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.
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