What happened
On September 15, 2026, Lovable had a significant outage starting at 16:43 UTC. It lasted about an hour and was resolved at 17:58 UTC. Lovable has since reported the issue as resolved. No further detail about the cause has been published.
Who this kind of outage hits, and how they usually find out
If you build on Lovable, your app or project lives inside it. When Lovable has a bigger problem, things stop working, and the tool itself rarely sends you a message saying so. Most people find out the wrong way: a customer tries to use something, it fails, and they write in to ask what is going on. By then you are already behind. You are reading a complaint instead of a heads-up, and you have no idea how long the problem has been running.
That gap, between when the tool broke and when you heard about it, is where the damage happens. A paying customer noticed before you did. That is a hard position to explain.
Why this is especially rough if you are not an engineer
There is no error log to open. There is no red screen telling you something is wrong. The work just stops moving. A form does not submit, a build does not finish, a page does not load. If you are not watching closely, it looks like user error or a fluke. You might spend time troubleshooting your own setup before it even occurs to you that the tool itself is the problem. The first clear signal is often an unhappy person on the other end, and by then the outage may already be over, which makes it even harder to explain.
Timeline
- 16:43 UTC - Lovable’s outage began. The problem was significant.
- About one hour of disruption.
- 17:58 UTC - Lovable reported the issue resolved.
How a watcher catches this before your users do
NoCrash reads Lovable’s public status page every minute. The moment that page flips from working to having trouble, NoCrash sends you a plain-language message about it. Not a raw status code. Not a wall of technical text. A short note in plain English, sitting next to everything else you build on, telling you something is wrong right now.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you give it a URL or add a small JS snippet to your app, it watches that as well. So if something goes quiet on your own side, that surfaces alongside any tool-level trouble.
What this changes is simple. Instead of a customer writing in to tell you your thing is broken, you get a calm heads-up first. You can post a note, pause a campaign, or just know what is happening before anyone asks. NoCrash does not find the outage before Lovable’s own status page does. It catches it within a minute of Lovable’s own report, and it tells you in words you can act on immediately.
The official source
Lovable’s own status page is the authoritative record for this outage. No direct link is available at this time, so check Lovable’s official channels for the full account.