Signing in with Apple is currently slow or failing for some users. This affects signing in to Lovable and signing in to apps built with Lovable. Our team is investigating.
Some users may see errors or delays when the Lovable agent works on their projects. Our team is working on a fix.
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.
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.
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 apps built with Lovable Cloud are currently unable to reach their backend, which may cause errors when loading data or signing in. Our team is investigating and will share an update soon.
Chat and project changes are currently failing for some users. Our team has identified the cause and is working on a fix.
Some users may see errors when setting up a database or backend for a new project. Existing projects are not affected. Our team is investigating.
Enabling Lovable Cloud on projects is currently failing for some users. Existing projects and apps already using Lovable Cloud are not affected. Our team is investigating.
Lovable may take minutes to answer messages in the chat. We are investigating and will try to restore full functionality as soon as possible.
Changes syncing between Lovable and GitHub may be delayed for some users. This is caused by an issue at one of our providers, and things are starting to recover. We are monitoring closely.
Some Lovable backends (Lovable Cloud) aren’t coming back after a restart. If yours is affected, your app may be down, and sign-in or data may not load. The cause is an issue at one of our upstream vendors. We’re monitoring it and will post an update here as soon as we have one.