- Level
- confirmed
- Worst impact
- Degraded
- Components
- Cloud
- Down Index
- 17of 100
What to do
Check whether you use Lovable Cloud. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 21m it lasted.
Anything that failed between 2026-08-27 20:38 UTC and 2026-08-27 20:59 UTC may need a replay.Subscribe to Lovable's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=lovable works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Lovable 3
- investigating
We're currently experiencing degraded performance in one of our systems responsible for sending emails on behalf of Lovable apps. This means emails for email verification are delayed. We are working with our email provider to restore functionality as soon as we can.
provider
- monitoring
We're seeing signs of full recovery and will monitor to ensure it's stable. Any emails attempted to be sent during this period of degraded performance will still be processed and sent out to users.
provider
- resolved
Email sending on behalf of Lovable apps has returned to normal operation.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-819a2b637d
Is Lovable still down?
No, this incident was resolved 2026-08-27 20:59 UTC. For Lovable's live state, see https://down.guide/lovable.
How long did it last?
21m, from 2026-08-27 20:38 UTC to 2026-08-27 20:59 UTC, by the times Lovable posted.
What was affected?
Lovable named Cloud.
What caused it?
Lovable hasn't published a root cause. If it does, it shows here.
Where does this come from?
Lovable's official status page, https://status.lovable.dev, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.