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.

error levels are back to normal

This incident has been resolved.

This incident has been resolved.

This incident has been resolved

We’ve resolved the issue that caused lovable.dev to return “internal server error” responses. Service has been restored and we’re monitoring to ensure everything remains stable.

Loading times should be back to normal.

Loading times should be back to normal.

We’ve resolved the issue impacting our service. Users should no longer experience failed requests or slow loading times. Thanks for your patience, and sorry for the disruption.

The problem was identified and fixed. The issue if fully resolved.

This incident has been resolved.

Chat requests are no longer failing, and we are fully operational. We apologize for any inconvenience this may have caused.

Error rates have recovered

We've identified the issue and routed to another provider. The system has recovered.

Questions should now work again

The error rate for creating Supabase projects is back to normal

This issue has been resolved, thank you for your patience!

We sincerely apologize for any inconvenience this incident may have caused to your operations.

This incident has been resolved

We are pleased to report that the incident affecting sandbox acquisition and chat requests has been resolved.

Summary
Between approximately 20:10 CET and 20:52 CET on December 3rd, 2025, we experienced issues with sandbox acquisition, which impacted chat request functionality.

Resolution
Operations have returned to normal. We have temporarily moved to a secondary provider to ensure stability.

We apologize for any inconvenience this incident may have caused.

The issue has been resolved. All systems are operating normally. We apologize for any inconvenience.