DAL01 - COLO Internet Connectivity Disruption (Upstream Provider)
minor- Started
- Jul 26, 2:48 PM EDT
- Resolved
- Jul 26, 9:41 PM EDT
- Duration
- 6h 53m
Lambda Labs's updates (3)
- identified · Jul 26, 2:48 PM EDT
**Severity Level:** Medium DAL01 - COLO Internet Connectivity Disruption (Upstream Provider) We are currently investigating a loss of internet connectivity affecting colocation customers in our DAL01 (Dallas) facility. The disruption is due to a down Dedicated Internet Access (DIA) circuit with one of our upstream providers. Customers with IP addresses in the **38.147.81.0/24** range may be unable to send or receive traffic over the affected circuit. We have opened a ticket with the upstream provider and are actively working with them to restore service. We will provide another update as soon as additional information becomes available. Thank you for your patience and understanding during this time. ----------------------------------------------------------------------------- In the event you’re unsure as to whether your service is impacted by this incident, please open a support ticket. We’ll get back to you as soon as possible. • [https://support.lambdalabs.com/hc/en-us/requests/new](https://support.lambdalabs.com/hc/en-us/requests/new "https://support.lambdalabs.com/hc/en-us/requests/new") To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.
- identified · Jul 26, 8:52 PM EDT
**Severity Level: Medium** DAL01 - COLO Internet Connectivity Disruption (Upstream Provider) We continue to work with our upstream provider to resolve the DIA circuit outage affecting DAL01. Our team is actively engaged and we're in regular contact as we work toward restoration. Customers with IP addresses in the **38.147.81.0/24** range remain impacted until service is restored. We do not have an ETA at this time but will share another update as soon as we have new information. Thank you for your patience while we work through this with our provider. ----------------------------------------------------------------------------- In the event you’re unsure as to whether your service is impacted by this incident, please open a support ticket. We’ll get back to you as soon as possible. • [https://support.lambdalabs.com/hc/en-us/requests/new](https://support.lambdalabs.com/hc/en-us/requests/new "https://support.lambdalabs.com/hc/en-us/requests/new") To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.
- resolved · Jul 26, 9:41 PM EDT
**Severity Level:** Medium The incident has been resolved. The network is now working as expected. Thank you for your patience. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still impacted by this, please open a support ticket and we’ll get back to you as soon as possible. • [https://support.lambdalabs.com/hc/en-us/requests/new](https://support.lambdalabs.com/hc/en-us/requests/new "https://support.lambdalabs.com/hc/en-us/requests/new") To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.
What our checks recorded
We checked Lambda 83 times from Lambda Labs's start time to its resolution, once every five minutes. Every one of them reached Lambda's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 83 ms, against 109 ms over the 24 hours before. Lambda Labs posted the incident at Jul 26, 2:48 PM EDT.
Updates are Lambda Labs's own words from its status page (status: resolved); we never add an inferred cause.