Is Lovable Down? How to Tell If It's Lovable or Your App
Lovable or your app not working? Check its status, then test the editor, your published site and your backend separately to find what's really broken.
Your Lovable app isn't working, or the Lovable editor won't respond, and you need to know one thing fast: is Lovable down, or is it something in your project?
The answer changes what you do next. If Lovable has an incident, the best move is to wait, tell your users and avoid making random changes. If it's your project, waiting won't fix anything. This guide gives you a short routine to tell the two apart, based on Lovable's own docs and real incidents from its status page.
"Lovable" is really three things
When people say "Lovable is down", they usually mean one of three different parts. Each can fail on its own:
- The editor at
lovable.dev: where you chat with Lovable and it changes your code. - Your published app: the site your visitors open. Lovable's hosting docs say each published app gets a public address on
lovable.app(or your own custom domain), served from locations around the world. - Your backend: the database, sign-in, storage and functions. That's either Lovable's built-in backend (Lovable Cloud) or a Supabase project you connected yourself.
The editor can be broken while your published app works perfectly, and the other way round. So test each part separately instead of guessing.
Step 1: Check Lovable's status (one minute)
Start outside your project:
- Open Lovable's official status page at
status.lovable.dev. It lists current and past incidents, and you can subscribe to updates. - Or open our live Lovable status page, which shows the official status and our own check of
lovable.devfrom outside.
Read the incident text, not just the color. Lovable's incidents are often partial. A few real examples from its status page:
- January 5, 2026: "A portion of chat requests are currently failing" — some users saw failed chat requests and slow loading, marked as affecting the Editor. It was resolved in about 15 minutes.
- November 28, 2025: a full outage of the Website (
lovable.devwasn't loading). The resolution note said Lovable's hosting provider, Netlify, had resolved the issue. - October 20, 2025: a service disruption caused by an AWS outage in the
us-east-1region, marked as affecting the Editor. Lovable estimated up to 13% of users were affected.
Notice what these have in common: the affected part was the editor or the website, which is where you build. That's why the next step matters.
Step 2: Test your published app, not the editor
Open your app the way a visitor would:
- Open a private (incognito) window, so no login or cache gets in the way.
- Go to your published address:
your-app.lovable.appor your custom domain. - Try the main things a user does: load the home page, sign in, open a page with data.
Even better, check from a different network too, such as your phone on mobile data. Or run our free checkup, which opens your site from our server, outside your own network.
Now compare:
| Editor | Published app | What it means |
|---|---|---|
| Broken | Works | Lovable's editor has a problem. Your users are fine. Wait. |
| Works | Broken | Your project. Keep going with Step 3. |
| Broken | Broken | Could be a wider Lovable incident. Check the status page again. |
| Works | Works for you, not for others | A network or domain problem. See Step 5. |
Step 3: If the editor is down, don't fight it
When the status page shows an Editor incident, or chat requests keep failing:
- Stop sending the same prompt again and again. During an incident, requests may fail. When it's over, you want a clear picture of which of your changes actually went through.
- Don't start big changes until the incident is resolved. When it is, check the last few changes Lovable made before you continue.
- Subscribe to updates on
status.lovable.dev, so you know when it's over without refreshing the page.
Lovable's docs describe the published site as a snapshot of your app at the time you published it. That's why an editor incident doesn't necessarily mean your live app is down — Step 2 tells you for sure.
Step 4: If your published app is broken, find which part fails
If Lovable's status is green and your live app is broken, the cause is almost always one of these.
The page is blank or shows an error
Open the live site, right-click → Inspect → Console, and read the first red error. A white page with an error like supabaseUrl is required or a failed script is a problem in your build or settings, not a Lovable outage. Our guide to a Lovable app showing a blank white screen goes through the usual causes one by one.
The page loads, but sign-in or data doesn't work
That points to the backend.
- Lovable Cloud: open the More menu in your project's toolbar and choose Logs. Lovable's docs describe this as the place to debug errors and track backend activity. Errors there tell you whether a function failed or a query was rejected.
- Your own Supabase project: check our Supabase status page for an incident. Then open your project in the Supabase dashboard. A Free plan project that had no activity for a week may be paused, which breaks sign-in and data while the site itself still loads. Our guide on a paused Supabase project shows how to resume it.
- "Failed to fetch" in the console: see Supabase "Failed to fetch" error.
Your recent changes aren't on the live site
This is the most common "Lovable is broken" moment that isn't a problem at all. Lovable's hosting docs say edits don't go live automatically: the published site is a snapshot, and your changes appear only after you open the Publish dialog and click Publish changes.
The lovable.app address works, but your custom domain doesn't
Then the problem is the domain, not Lovable. Lovable's docs say you can check a domain under Project → Settings → Domains, where its status should be Live. Our guide on a Lovable custom domain not working covers DNS records, the www version and SSL.
Nothing obvious, and the status page is green
Lovable's hosting docs suggest this order: check status.lovable.dev for platform-wide incidents, and if none is listed, confirm the project is still published in the Publish dialog, then contact Lovable's support.
Step 5: It works for you, but not for some users (or the other way round)
If your app works on your laptop but a user says it's down, or it works on mobile data but not on your Wi-Fi, the problem is often between the user and the servers: a DNS cache, an internet provider, or a regional block.
This happened for real in 2026: Supabase reported that certain internet providers in India blocked access to supabase.co from February 24 to March 3, 2026, under a government order. Apps whose backend was on Supabase loaded in India, but their data requests failed, and they worked over a VPN. Our guide Website works with a VPN but not without explains how to recognize this and what to do.
If it really is Lovable: what to do
- Tell your users. A short message — "We're seeing a problem with our platform provider and are watching it" — saves you a pile of support messages. If you have a status page, update it.
- Don't change working things. If only the editor is affected, your live app is fine; don't republish or reconnect anything "just in case".
- Check once it's resolved. Open your live app, sign in and test the main flows. Then go back to building.
A five-minute routine to remember
- Lovable status — is there an incident, and which part does it affect?
- Your published app in a private window — does it load and work?
- Editor broken, app fine → wait. App broken, status green → it's your project.
- Console for blank pages, backend logs for data and sign-in, Publish changes for missing updates, Settings → Domains for custom domains.
- Works on one network but not another → a network or regional problem, not Lovable.
The same routine works for other platforms. If your app is hosted on Vercel instead, see Vercel site down? How to tell if it's you or Vercel, and check the status of every service your app depends on on our status pages.
FAQ
- Where can I see if Lovable is down?
- Lovable's official status page is status.lovable.dev. It lists current and past incidents and lets you subscribe to updates. Our Lovable status page shows the same official status plus our own check of lovable.dev from outside.
- The Lovable editor doesn't respond. Is my live app down too?
- Not necessarily. The editor where you chat with Lovable and the published app your visitors use are different things. Open your published address in a private window: if it loads and works, your users are fine and only building is affected.
- Lovable's status is green but my app is broken. What now?
- Then the problem is most likely in your project: the last change, the backend, a custom domain or an unpublished update. Open the browser console on the live site, check your backend logs, and confirm the project is still published in the Publish dialog.
- I changed my app in Lovable but the live site didn't change. Is Lovable down?
- Probably not. Lovable's docs say the published site is a snapshot: edits go live only after you open the Publish dialog and click Publish changes.