Lightdash Outage History

Lightdash is up right now

Lightdash had 9 outages in the last 2 years totaling 17h 19m of downtime — averaging 0.4 incidents per month.

There were 9 Lightdash outages since May 29, 2025 totaling 17h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.lightdash.com

Minor May 6, 2026

Degraded database performance (US)

Detected by Pingoru
May 06, 2026, 03:14 PM UTC
Resolved
May 06, 2026, 04:55 PM UTC
Duration
1h 40m
Affected: Lightdash Cloud (US)
Timeline · 4 updates
  1. investigating May 06, 2026, 03:14 PM UTC

    We're investigating elevated database latency on Lightdash Cloud (US). Queries may be slower than usual. EU is unaffected.

  2. identified May 06, 2026, 03:32 PM UTC

    A fix has been applied to the database and is rolling out.

  3. monitoring May 06, 2026, 03:42 PM UTC

    Systems are stable, fix has been applied successfully. Monitoring system vitals.

  4. resolved May 06, 2026, 04:55 PM UTC

    Services stable, incident has been resolved.

Read the full incident report →

Notice April 27, 2026

Embedded dashboards not loading correctly

Detected by Pingoru
Apr 27, 2026, 10:28 AM UTC
Resolved
Apr 27, 2026, 10:59 AM UTC
Duration
31m
Timeline · 1 update
  1. identified Apr 27, 2026, 10:28 AM UTC

    We've identified an issue with embedded content not loading correctly. We are working swiftly to implement a fix. More coming soon shortly.

Read the full incident report →

Major April 21, 2026

Network configuration may cause warehouse timeout errors

Detected by Pingoru
Apr 21, 2026, 11:37 AM UTC
Resolved
Apr 21, 2026, 02:48 PM UTC
Duration
3h 11m
Affected: Lightdash Cloud (EU)
Timeline · 2 updates
  1. identified Apr 21, 2026, 11:37 AM UTC

    We unintentionally added a new external IP address for customers in the EU. Customers using firewalls for their warehouse may see unexpected requests from: 34.140.90.83 - we are fixing this now.

  2. resolved Apr 21, 2026, 02:48 PM UTC

    Earlier today, an additional egress IP address was unintentionally provisioned on our EU cluster. This caused some queries from Lightdash to customer warehouses to be blocked, where the new IP was not on the customer's allowlist. We've worked directly with affected customers to apply an allowlist update, and error rates have returned to normal. We're now monitoring to confirm stability and working with our cloud provider to consolidate back to a single egress IP at the infrastructure layer. Action required if you're still seeing warehouse connection errors: please ensure both `34.79.239.130` and `34.140.90.83` are on your warehouse IP allowlist. Our [IP allowlisting guide](https://docs.lightdash.com/get-started/setup-lightdash/connect-project#adding-lightdashs-static-ip-addresses-to-your-allow-list) has been updated to reflect the current EU egress IP set and includes step-by-step instructions. We apologise for the disruption.

Read the full incident report →

Major March 24, 2026

Intermittent API errors across US

Detected by Pingoru
Mar 24, 2026, 10:35 AM UTC
Resolved
Mar 24, 2026, 12:19 PM UTC
Duration
1h 43m
Affected: Lightdash Cloud (US)
Timeline · 6 updates
  1. identified Mar 24, 2026, 10:35 AM UTC

    We have identified an issue in our network configuration that is leading to some requests failing. We've identified fix and are deploying to production.

  2. identified Mar 24, 2026, 10:35 AM UTC

    We are continuing to work on a fix for this issue.

  3. identified Mar 24, 2026, 10:36 AM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Mar 24, 2026, 11:34 AM UTC

    We have deployed a fix to our network configuration and all services are healthy. We will continue monitoring.

  5. resolved Mar 24, 2026, 12:19 PM UTC

    We've seen no errors related to network configuration.

  6. postmortem Mar 24, 2026, 12:21 PM UTC

    **Root cause** Our cloud networking layer had insufficient capacity to handle the volume of outbound connections from our services. As traffic grew, we periodically exceeded the available connection limits, causing some requests to be dropped. **What we fixed** We restructured our internal network architecture, significantly reducing the load on our outbound connection layer. This freed up capacity. ‌ **Ensuring it won’t happen again** We’ve permanently re-architected to prevent this specific issue. We’ve added monitoring \+ alerts to catch similar network errors.

Read the full incident report →

Major September 29, 2025

Embedding features may be unavailable

Detected by Pingoru
Sep 29, 2025, 06:34 PM UTC
Resolved
Sep 29, 2025, 07:26 PM UTC
Duration
51m
Affected: Lightdash Cloud (US)Lightdash Cloud (EU)
Timeline · 4 updates
  1. identified Sep 29, 2025, 06:34 PM UTC

    Some customers may notice embedded content not loading and the settings page missing. We've found an error with an external provider we use to flag this feature, we're working on a fix now

  2. monitoring Sep 29, 2025, 07:09 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Sep 29, 2025, 07:25 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Sep 29, 2025, 07:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 12, 2025

Google Cloud Platform outage

Detected by Pingoru
Jun 12, 2025, 06:40 PM UTC
Resolved
Jun 12, 2025, 11:16 PM UTC
Duration
4h 36m
Affected: Lightdash Cloud (US)Lightdash Cloud (EU)
Timeline · 3 updates
  1. identified Jun 12, 2025, 06:40 PM UTC

    Google Cloud Storage outage. Core services used to power Lightdash queries are currently unavailable. We're investigating work arounds. You can read more on Google Cloud Storage status here: https://status.cloud.google.com/

  2. monitoring Jun 12, 2025, 10:12 PM UTC

    Queries are loading. Waiting for GCP to confirm services are stable

  3. resolved Jun 12, 2025, 11:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 12, 2025

Users can't access all dashboards (on app.lightdash.cloud)

Detected by Pingoru
Jun 12, 2025, 07:50 AM UTC
Resolved
Jun 12, 2025, 08:52 AM UTC
Duration
1h 2m
Timeline · 4 updates
  1. investigating Jun 12, 2025, 07:50 AM UTC

    We've identified an issue with loading all dashboards on shared Lightdash instances.

  2. monitoring Jun 12, 2025, 08:06 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Jun 12, 2025, 08:51 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jun 12, 2025, 08:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 2, 2025

Degraded performance

Detected by Pingoru
Jun 02, 2025, 09:43 AM UTC
Resolved
Jun 02, 2025, 10:50 AM UTC
Duration
1h 6m
Affected: Lightdash Cloud (US)Lightdash Cloud (EU)
Timeline · 3 updates
  1. investigating Jun 02, 2025, 09:43 AM UTC

    We are currently investigating this issue.

  2. investigating Jun 02, 2025, 10:06 AM UTC

    We're currently experiencing downtime on some of our larger instances, including: - app.lightdash.cloud - eu1.lightdash.cloud Our team is actively investigating the issue and working to restore access as quickly as possible. We’ll keep you updated as soon as we know more. Thanks for your patience!

  3. resolved Jun 02, 2025, 10:50 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 29, 2025

Degraded performance in app.lightdash.cloud

Detected by Pingoru
May 29, 2025, 10:42 AM UTC
Resolved
May 29, 2025, 01:17 PM UTC
Duration
2h 34m
Timeline · 4 updates
  1. investigating May 29, 2025, 10:42 AM UTC

    Users may notice slower page load times and delayed query responses during this time. Our engineering team is actively investigating the root cause and working to restore normal performance levels.

  2. identified May 29, 2025, 11:28 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 29, 2025, 12:57 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 29, 2025, 01:17 PM UTC

    We can confirm that the fix was successful and that the issue has been resolved. Thank you for your patience

Read the full incident report →