Lovable Outage History

Status: Identified Our provider is looking into the issue. Affected components Cloud (Degraded performance)

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)

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)

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)

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)

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)

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)

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)

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)

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

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)

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)

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)