The issue has now been resolved

This incident has been resolved.

We have identified and resolved the issue. The message queue should now be functioning as normal. If you have pending work in your queue, we recommend pausing and then unpausing it to resume processing.

Customer can now continue to enable Lovable Cloud in asian-pacific regions without further issues

All connections to the Slack app have been restored.
However, if you are still running into issues, we recommend reconnecting the app.

This incident has been resolved

The issue was resolved by the upstream provider

This incident has been resolved.

The agent was processessing the first follow-up in the queue but the second follow-up were remaining stuck indefinitely. This is now resolved.

Publishes were failing for some users during a few hours, but is now fixed. Republishing will solve it

The issue has been resolved and Live preview is fully operational again

This issue has now been resolved

The issue has been resolved.

The issue has been resolved.

No impact observed to customers

This issue has been resolved.

Publishing was not working for a small amount of users who got errors when publishing. The issue has now resolved

The incident is resolved and the Lovable agent's performance has returned to normal.

All affected customers should now have received their credits. We sincerely apologize for the inconvenience this caused and appreciate your patience throughout.

If you have any questions or are still experiencing issues related to this, please don't hesitate to reach out to our support team.

This issue has been fully resolved. Publishing is working as normal and all previously affected projects are now displaying their most recent publish correctly

Team is monitoring the fix

Errors affecting chat requests and related project functions have been resolved.

This incident has been resolved. Making a new external commit to your repo should trigger a sync and pull in the external commits that aren't showing.

We are continuing to monitor the situation. If you are still having issues, please reach out to support.

Projects integrated with GitHub are no longer experiencing increased failure rates

The elevated Lovable Project creation rate errors are now fixed. We had an issue with upstream provider.

A fix has been deployed and connections work as expected.

This incident has been resolved

The issue has been resolved

This incident has been resolved

The issue causing increased error rates when creating new Lovable Cloud projects has been resolved.
Our infrastructure vendor has implemented a fix and project creation has returned to normal across regions. We have monitored the system and confirmed that services are operating normally.
We apologize for the disruption and appreciate your patience while we worked to resolve the issue.

The issue affecting chat requests in the Editor has been resolved and services have been stable for over 3 hours.

The issue affecting project creation in Lovable Cloud has been resolved. Our team identified the cause and implemented a fix, and project creation is now operating normally.
We will continue to monitor the system to ensure stability. Thank you for your patience while we worked to resolve the issue.

This incident has been resolved.

lovable.dev is back up.

Supabase have resolved their incident, and everything is back to being operational.

Access to Supabase’s website has now been fully restored for all users across India.

If you were previously affected, you should now be able to access your Supabase projects without interruptions. Please clear your DNS cache or restart your network connection if you still encounter issues. Allow up to 24 hours for changes to propagate across providers.

Thank you for your patience while we worked through this incident.

Due to a GitHub outage, projects that were connected to GitHub could not be edited for a while. Service is now back to normal.

The issue is resolved.

This issue has been resolved

duplicated

All services are back to healthy.

This incident has been resolved.
The impact of this event was limited to log visibility and log retention. Some logs between 20:20 UTC and 23:23 UTC on Friday, Feb 20, 2026 may not be available.

This incident is now resolved

This incident has been resolved.

All our metrics have recovered to pre-incident levels and all systems are operational.

We have successfully resolved the issue affecting project revert functionality. Our team deployed a fix that restores it to a stable version, addressing the root cause of the failures.

Users who experienced errors or missing progress when attempting to revert projects should now find these issues resolved. All revert operations are functioning normally.

Thank you for your patience while we worked through this issue.

This incident has been resolved.

We have successfully resolved the high error ratio affecting Lovable cloud project creation. The issue began at approximately 10:12 UTC and was fully resolved by 10:28 UTC on February 9, 2026.

We sincerely apologize for the disruption this caused. Thank you for your patience and understanding as we worked to resolve this issue. If you experienced any failed project creation attempts during this window, please feel free to retry them now—they should complete successfully.

The issue is resolved

Between 16:45 - 18:30 we observed a high rate of failure when enabling Lovable Cloud for new projects, but has since recovered and operations are back to normal.

We have completed our investigation and monitoring of the incident that occurred on February 1st. Our systems have been operating normally, and we have confirmed that all necessary backfill processes have completed successfully.

We've successfully resolved the issue with Supabase connector functionality. The fix has been deployed and all users should now be able to connect to Supabase without any problems.

Thank you for your patience while we worked on this.

We have found the root cause and deployed a fix. All systems are back to a healthy state. We will continue to monitor the situation.

We've resolved the issue that was preventing access to projects. The problem was caused by a recent update to how we check user permissions, which incorrectly blocked some users from viewing their projects.

Thank you for your patience while we worked through this.

The issue has been fully resolved. We've identified the root cause and will be improving our testing and deployment processes to prevent similar issues in the future. We appreciate your patience.

The issue has been resolved and chat is now functioning normally. We apologize for any inconvenience this may have caused.

We have identified the root cause of the issue and random refreshes should no longer occur.

We have fixed the cause of the problem and queueing should now work as usual!

We found the cause for the higher than usual latency and deployed a fix. We will continue to monitor the situation over the next few days.

Levels looks steady

We are pleased to report that the issues affecting GitHub have been resolved. We have confirmed that services are now fully operational, and all affected systems have been restored. Normal operations have resumed. We apologize for any disruption this incident may have caused.

The networking issues that caused elevated failure rates since January 16th have been fully resolved. Platform reliability has returned to normal levels and we've completed our investigation into the root cause.

Project creation success rate is back to normal

We have identified the cause of the problem and publishing should now work as usual!

We've reduced the load on our deployment infrastructure and thus recovered.