Embedded dashboards not loading correctly
Timeline · 1 update
- 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.
There were 3 Lightdash outages since March 24, 2026 totaling 5h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.
We've identified an issue with embedded content not loading correctly. We are working swiftly to implement a fix. More coming soon shortly.
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.
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.
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.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We have deployed a fix to our network configuration and all services are healthy. We will continue monitoring.
We've seen no errors related to network configuration.
**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.
Pingoru polls Lightdash's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required