My app won't come back after a restart: is it me or the platform?

What it means in plain English

A restart that does not bring the app back can be a problem in the project, or a problem the platform has already posted. The check is the host's official status page, read today. A resolved incident from another day is an example of what those pages look like. It is not today's status.

Open the page for the host you use and read the current notice:

• Supabase Status: https://status.supabase.com/ (opens in a new tab)
• Lovable Status: https://status.lovable.dev/ (opens in a new tab)
• Vercel Status: https://www.vercel-status.com/ (opens in a new tab)
• Bolt.new Status: https://status.bolt.new/ (opens in a new tab)
• Replit Status: https://status.replit.com/ (opens in a new tab)

Those five URLs returned a page titled with that product's status. This page does not copy whatever "operational" or "down" state they showed on 21 October 2026. The notice on the page when you open it is the current one.

Likely causes

• The status page lists a current incident whose wording matches a restart that does not finish, or a backend that does not come back. Two resolved examples are below, each from its own status page.
• The status page lists no such notice. Then that page is not reporting this outage, and the failure is in the published app. Different problems, with their own pages: 500: INTERNAL_SERVER_ERROR / FUNCTION_INVOCATION_FAILED on Vercel, Lovable app is a blank white or black screen after publish, and Replit app works in preview but not when published.

How to fix it, step by step

1. Open the status URL for the host above. Read the incidents listed now, not an example from this page.
2. If a current incident says projects or backends are stuck after a restart, wait for the next update on that status page. In the Supabase example, the investigating update said they were investigating and would provide more updates. In the Lovable example, the identified update said they were monitoring and would post an update on the status page.
3. When that incident is marked resolved, reload the app. The Supabase incident below was marked Resolved. The Lovable incident below has "status": "resolved" in the incidents JSON.
4. If the status page has no notice that matches the app staying down after a restart, that page is not reporting this outage. Compare the error you see with the three fix pages linked above. Those pages are other problems. They are not this status report.

Two resolved examples

Each example below is quoted from that host's own status page.

Supabase, 20-21 October 2026

https://status.supabase.com/incidents/01M5DN6V02FJHZTE9390XJM9YY (opens in a new tab) is titled "Projects stuck in restarting state" and is marked Resolved.

The investigating update says: "Some projects in us-east-2 are stuck in restarting state. We are actively investigating this and will provide more updates as information becomes available."

A later monitoring update says: "The fix has fully rolled out. Projects are no longer stuck in a restarting state. We will continue to monitor the situation."

The resolved update says: "All affected projects have be fixed. We have not seen recurrence of the issue and we are resolving the incident."

The incident covers 20-21 October 2026 and is marked Resolved. The page does not print a time zone, so this page does not state a clock time. The investigating wording is some projects in us-east-2, not every project.

Lovable, 21 October 2026

https://status.lovable.dev/incidents/01M5DZAPZAKVN0ZYHD9SXXXVK3 (opens in a new tab) is titled "Lovable backends stuck after restart".

https://status.lovable.dev/api/v2/incidents.json (opens in a new tab) records that incident as id 01M5DZAPZAKVN0ZYHD9SXXXVK3, name "Lovable backends stuck after restart", status resolved, created_at 2026-10-21T00:56:08Z, and resolved_at 2026-10-21T02:47:55Z. The Z suffix is UTC. That is 21 October 2026, 00:56:08 through 02:47:55 UTC.

The identified update says: "Some Lovable backends (Lovable Cloud) aren’t coming back after a restart. If yours is affected, your app may be down, and sign-in or data may not load. The cause is an issue at one of our upstream vendors. We’re monitoring it and will post an update here as soon as we have one."

The resolved update says: "A fix is being rolled out and users should no longer experience issues with backend stuck after restart."

That update calls the cause "an issue at one of our upstream vendors" and does not give the vendor's name.

How to check it worked

• The host's status page either has no matching restart incident, or the matching incident is marked resolved, and a reload shows the app responding.
• If the app is still down and the status page does not list that symptom, you are past the platform check. Use the error on screen with the other fix pages linked above.

Sources

• https://status.supabase.com/ (opens in a new tab)
• https://status.supabase.com/incidents/01M5DN6V02FJHZTE9390XJM9YY (opens in a new tab)
• https://status.lovable.dev/ (opens in a new tab)
• https://status.lovable.dev/incidents/01M5DZAPZAKVN0ZYHD9SXXXVK3 (opens in a new tab)
• https://status.lovable.dev/api/v2/incidents.json (opens in a new tab)
• https://www.vercel-status.com/ (opens in a new tab)
• https://status.bolt.new/ (opens in a new tab)
• https://status.replit.com/ (opens in a new tab)