Lovable Outage History

Lovable is up right now

Lovable had 91 outages in the last 2 years — averaging 3.7 incidents per month.

There were 91 Lovable outages since January 27, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.lovable.dev

Minor February 26, 2026

Supabase accessibility issue for users in India

Detected by Pingoru
Feb 26, 2026, 04:18 PM UTC
Resolved
Feb 26, 2026, 04:18 PM UTC
Duration
—
Timeline · 2 updates
  1. monitoring Feb 26, 2026, 04:15 PM UTC

    Status: Monitoring We're aware that users in India are currently unable to access Supabase due to an ISP-level connectivity issue. This appears to be a block implemented by certain Indian internet service providers, not an issue with Supabase's infrastructure, which remains fully operational. Supabase has reached out to the affected ISPs to resolve this matter. We'll continue to monitor the situation and update you as soon as connectivity is restored for all users in India.

  2. resolved Feb 26, 2026, 04:18 PM UTC

    Status: Resolved duplicated

Read the full incident report →

Minor February 26, 2026

Technical difficulties with our services

Detected by Pingoru
Feb 26, 2026, 10:24 AM UTC
Resolved
Feb 26, 2026, 10:24 AM UTC
Duration
—
Affected: EditorWebsiteLogin
Timeline · 5 updates
  1. investigating Feb 26, 2026, 09:02 AM UTC

    Status: Investigating We're currently experiencing technical difficulties with our API, which is affecting some platform functionality. Our team is working on resolving this as quickly as possible. Affected components Website (Full outage) Editor (Full outage)

  2. investigating Feb 26, 2026, 09:04 AM UTC

    Status: Investigating We're currently experiencing technical difficulties with our API, which is affecting some platform functionality. Our team is working on resolving this as quickly as possible. Affected components Website (Full outage) Editor (Full outage)

  3. investigating Feb 26, 2026, 09:10 AM UTC

    Status: Investigating We're currently experiencing technical difficulties with our services, which is affecting some platform functionality. Our team is working on resolving this as quickly as possible. Affected components Website (Full outage) Editor (Full outage) Login (Full outage)

  4. monitoring Feb 26, 2026, 09:54 AM UTC

    Status: Monitoring We've identified and mitigated the technical issue. We will be continuing to monitor. Affected components Website (Operational) Editor (Operational) Login (Operational)

  5. resolved Feb 26, 2026, 10:24 AM UTC

    Status: Resolved All services are back to healthy. Affected components Website (Operational) Editor (Operational) Login (Operational)

Read the full incident report →

Minor February 21, 2026

Cloud Provider Incident Impacting Logs and Observability

Detected by Pingoru
Feb 21, 2026, 12:00 AM UTC
Resolved
Feb 21, 2026, 12:00 AM UTC
Duration
—
Affected: Cloud
Timeline · 6 updates
  1. investigating Feb 20, 2026, 08:49 PM UTC

    Status: Investigating We’re currently experiencing issues with our cloud provider that are impacting logs and observability. All cloud-based projects are affected. Affected components Cloud (Partial outage)

  2. identified Feb 20, 2026, 09:14 PM UTC

    Status: Identified Our provider has identified an issue resulting in missing log, observability, and edge function information. Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. Affected components Cloud (Partial outage)

  3. identified Feb 20, 2026, 09:40 PM UTC

    Status: Identified Our provider has patched an issue resulting in missing log, observability, and edge function information. Services are stabilizing but not fully restored. Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. Affected components Cloud (Partial outage)

  4. identified Feb 20, 2026, 10:25 PM UTC

    Status: Identified Our provider has patched an issue resulting in missing log, observability, and edge function information. Services are still stabilizing but not fully restored. Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. Affected components Cloud (Partial outage)

  5. identified Feb 20, 2026, 11:16 PM UTC

    Status: Identified Our provider has patched an issue resulting in missing log, observability, and edge function information. Services are still stabilizing but not fully restored. Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. Affected components Cloud (Degraded performance)

  6. resolved Feb 21, 2026, 12:00 AM UTC

    Status: Resolved 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. Affected components Cloud (Operational)

Read the full incident report →

Minor February 19, 2026

Lovable Cloud connectivity problems

Detected by Pingoru
Feb 19, 2026, 09:39 PM UTC
Resolved
Feb 19, 2026, 09:39 PM UTC
Duration
—
Affected: Cloud
Timeline · 5 updates
  1. identified Feb 19, 2026, 06:27 PM UTC

    Status: Identified Our provider has an outage in eu-central-1, impacting a small portion of our users in this region. Affected components Cloud (Partial outage)

  2. identified Feb 19, 2026, 07:10 PM UTC

    Status: Identified Our provider has an outage in eu-central-1, impacting a small portion of our users in this region. The root cause is still unknown at this time. Affected components Cloud (Partial outage)

  3. resolved Feb 19, 2026, 08:25 PM UTC

    Status: Resolved Our provider resolved the issue. Affected components Cloud (Operational)

  4. monitoring Feb 19, 2026, 08:44 PM UTC

    Status: Monitoring Some affected projects affected by the incident are failing to restart, our provider is investigating. Affected components Cloud (Degraded performance)

  5. resolved Feb 19, 2026, 09:39 PM UTC

    Status: Resolved This incident is now resolved Affected components Cloud (Operational)

Read the full incident report →

Minor February 17, 2026

Projects using github experiencing elevated errors

Detected by Pingoru
Feb 17, 2026, 06:05 PM UTC
Resolved
Feb 17, 2026, 06:05 PM UTC
Duration
—
Timeline · 2 updates
  1. investigating Feb 17, 2026, 04:51 PM UTC

    Status: Investigating Projects hosted on Github are experiencing a higher rate of errors than normal. We're investigating

  2. resolved Feb 17, 2026, 06:05 PM UTC

    Status: Resolved This incident has been resolved.

Read the full incident report →

Minor February 12, 2026

High failure rate for reverts

Detected by Pingoru
Feb 12, 2026, 06:30 AM UTC
Resolved
Feb 12, 2026, 06:30 AM UTC
Duration
—
Affected: Editor
Timeline · 2 updates
  1. investigating Feb 11, 2026, 09:28 AM UTC

    Status: Investigating We are currently investigating an issue affecting the project revert functionality for a subset of users. Some users may experience failures when attempting to revert projects to previous versions. Our team has identified the root cause and is actively working on a fix. We will provide updates as we make progress toward resolution. We apologize for any inconvenience this may cause. Thank you for your patience. Affected components Editor (Degraded performance)

  2. resolved Feb 12, 2026, 06:30 AM UTC

    Status: Resolved 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. Affected components Editor (Operational)

Read the full incident report →

Minor February 9, 2026

Elevated error rates on project connected to github

Detected by Pingoru
Feb 09, 2026, 08:40 PM UTC
Resolved
Feb 09, 2026, 08:40 PM UTC
Duration
—
Affected: Editor
Timeline · 6 updates
  1. investigating Feb 09, 2026, 09:18 AM UTC

    Status: Investigating We are currently experiencing elevated error rates for projects connected to GitHub due to ongoing issues on GitHub’s platform. Specifically, users may see increased failures when attempting to push code changes to their repositories Affected components Editor (Degraded performance)

  2. resolved Feb 09, 2026, 03:16 PM UTC

    Status: Resolved GitHub has resolved their incident, and we are confirming that error rates have returned to normal. All services are operating normally, and code push operations are functioning as expected. Thank you for your patience during this incident. Affected components Editor (Operational)

  3. identified Feb 09, 2026, 04:42 PM UTC

    Status: Identified We are currently experiencing elevated error rates affecting multiple services due to ongoing issues on GitHub's platform. This is impacting: • Code push operations to GitHub repositories • Project transfer workflows • Chat functionality GitHub is investigating degraded performance again. We are actively monitoring the situation and will provide updates as more information becomes available. We apologize for any disruption this may cause. We will update this page as soon as we have more information or when the issue is resolved. Affected components Editor (Partial outage)

  4. resolved Feb 09, 2026, 06:02 PM UTC

    Status: Resolved This incident has been resolved. Affected components Editor (Operational)

  5. identified Feb 09, 2026, 07:12 PM UTC

    Status: Identified Elevated error rates and slow response times occurred when pushing code to GitHub, transferring projects, and using chat features due to upstream GitHub outages. Affected components Editor (Operational)

  6. resolved Feb 09, 2026, 08:40 PM UTC

    Status: Resolved "This incident has been resolved." Affected components Editor (Operational)

Read the full incident report →

Minor February 9, 2026

High error rate creating Lovable cloud

Detected by Pingoru
Feb 09, 2026, 09:40 AM UTC
Resolved
Feb 09, 2026, 09:40 AM UTC
Duration
—
Affected: Cloud
Timeline · 2 updates
  1. investigating Feb 09, 2026, 09:26 AM UTC

    Status: Investigating We are currently investigating a high error ratio affecting Lovable cloud project creation. Users attempting to create new projects in this region may experience failures. Our engineering team is actively working to identify and resolve the root cause. We will provide updates as soon as we have more information. We apologize for any disruption this may cause and appreciate your patience as we work to restore full service. Affected components Cloud (Degraded performance)

  2. resolved Feb 09, 2026, 09:40 AM UTC

    Status: 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. Affected components Cloud (Operational)

Read the full incident report →

Minor February 6, 2026

Elevated errors from an upstream provider causing builds to fail

Detected by Pingoru
Feb 06, 2026, 08:33 AM UTC
Resolved
Feb 06, 2026, 08:33 AM UTC
Duration
—
Timeline · 4 updates
  1. investigating Feb 05, 2026, 04:12 PM UTC

    Status: Investigating Some users are experiencing failing requests

  2. identified Feb 05, 2026, 04:36 PM UTC

    Status: Identified We have identified an error with an upstream provider and are working to resolve

  3. monitoring Feb 05, 2026, 05:20 PM UTC

    Status: Monitoring We have implemented a workaround and errors the number of errors has been reduced.

  4. resolved Feb 06, 2026, 08:33 AM UTC

    Status: Resolved The issue is resolved

Read the full incident report →

Minor February 4, 2026

Errors enabling lovable cloud

Detected by Pingoru
Feb 04, 2026, 06:48 PM UTC
Resolved
Feb 04, 2026, 06:48 PM UTC
Duration
—
Affected: Cloud
Timeline · 2 updates
  1. investigating Feb 04, 2026, 05:05 PM UTC

    Status: Investigating Users might face errors when enabling lovable cloud in their lovable projects Affected components Cloud (Degraded performance)

  2. resolved Feb 04, 2026, 06:48 PM UTC

    Status: 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. Affected components Cloud (Operational)

Read the full incident report →

Minor February 4, 2026

Monthly credit refill is delayed

Detected by Pingoru
Feb 04, 2026, 02:20 PM UTC
Resolved
Feb 04, 2026, 02:20 PM UTC
Duration
—
Affected: Editor
Timeline · 3 updates
  1. identified Feb 01, 2026, 05:53 PM UTC

    Status: Identified If you are on a free plan, you may still see the credit limit from January. We are working on resolving the issue and resuming the automatic credit refill. Affected components Editor (Degraded performance)

  2. identified Feb 02, 2026, 01:11 AM UTC

    Status: Identified We have identified several issues in the code responsible for the credit refill, and are working on fixing them. We have also started a separate, faster refill process to unblock users who had run out of monthly credits entirely. Even if you haven't received credits yet, you might still see "Mar 1" as the next refill date. This is a display bug and it doesn't affect the refill. --- Our goal is to finish both refills as soon as possible. This means we might have to pause and resume the refills as we are fixing the causes of slowness one by one. If you haven't received the credits yet, this is because the process was paused before it could reach you, and will soon resume. Affected components Editor (Degraded performance)

  3. resolved Feb 04, 2026, 02:20 PM UTC

    Status: Resolved 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. Affected components Editor (Operational)

Read the full incident report →

Minor February 4, 2026

Issues connecting Supabase through connectors

Detected by Pingoru
Feb 04, 2026, 09:06 AM UTC
Resolved
Feb 04, 2026, 09:06 AM UTC
Duration
—
Affected: Editor
Timeline · 2 updates
  1. identified Feb 04, 2026, 08:38 AM UTC

    Status: Identified We’re aware of an issue preventing some users from connecting Supabase through the connectors. We’ve identified the cause and are currently rolling out a fix. We’ll share another update once the fix is fully deployed and we’ve confirmed recovery. Affected components Editor (Partial outage)

  2. resolved Feb 04, 2026, 09:06 AM UTC

    Status: Resolved 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. Affected components Editor (Operational)

Read the full incident report →

Minor February 1, 2026

The Lovable coding agent is experiencing an elevated error rate

Detected by Pingoru
Feb 01, 2026, 11:26 AM UTC
Resolved
Feb 01, 2026, 11:26 AM UTC
Duration
—
Affected: Editor
Timeline · 2 updates
  1. investigating Feb 01, 2026, 12:53 AM UTC

    Status: Investigating We're investigating elevated error rates in the Lovable Agent Affected components Editor (Degraded performance)

  2. resolved Feb 01, 2026, 11:26 AM UTC

    Status: Resolved 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. Affected components Editor (Operational)

Read the full incident report →

Minor January 30, 2026

Incorrect "missing permissions" dialogs

Detected by Pingoru
Jan 30, 2026, 08:38 PM UTC
Resolved
Jan 30, 2026, 08:38 PM UTC
Duration
—
Affected: Editor
Timeline · 2 updates
  1. identified Jan 30, 2026, 08:17 PM UTC

    Status: Identified Some users may see incorrect "missing permissions" dialogs. We've identified the issue and a fix is in progress. Affected components Editor (Partial outage)

  2. resolved Jan 30, 2026, 08:38 PM UTC

    Status: Resolved 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. Affected components Editor (Operational)

Read the full incident report →

Minor January 30, 2026

A subset of chat requests are failing

Detected by Pingoru
Jan 30, 2026, 08:41 AM UTC
Resolved
Jan 30, 2026, 08:41 AM UTC
Duration
—
Affected: Editor
Timeline · 4 updates
  1. investigating Jan 30, 2026, 08:12 AM UTC

    Status: Investigating A small subset of chat requests are failing with Internal Errors. We're investigating the root cause and will share more details as our analysis progresses. Affected components Editor (Partial outage)

  2. identified Jan 30, 2026, 08:24 AM UTC

    Status: Identified We identified the issues and are rolling out a fix Affected components Editor (Partial outage)

  3. monitoring Jan 30, 2026, 08:31 AM UTC

    Status: Monitoring A fix has been deployed and service has returned to normal. We apologize for any inconvenience this may have caused. We're continuing to monitor to ensure stability. Affected components Editor (Partial outage)

  4. resolved Jan 30, 2026, 08:41 AM UTC

    Status: Resolved 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. Affected components Editor (Operational)

Read the full incident report →

Minor January 27, 2026

Frequent automatic hard refreshes

Detected by Pingoru
Jan 27, 2026, 07:03 PM UTC
Resolved
Jan 27, 2026, 07:03 PM UTC
Duration
—
Affected: Editor
Timeline · 2 updates
  1. investigating Jan 27, 2026, 04:37 PM UTC

    Status: Investigating We’re investigating unexpectedly hard refreshing/reloading, which can interrupt sessions and occasionally cause recent input to be lost. We’re investigating and working on a fix. Affected components Editor (Degraded performance)

  2. resolved Jan 27, 2026, 07:03 PM UTC

    Status: Resolved We have identified the root cause of the issue and random refreshes should no longer occur. Affected components Editor (Operational)

Read the full incident report →