Lightdash incident
Network configuration may cause warehouse timeout errors
Affected components
Update timeline
- 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.
- 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.
Looking to track Lightdash downtime and outages?
Pingoru polls Lightdash's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Lightdash reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Lightdash alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required