Lambda AI
AS11588 · Lambda
Lambda, Inc.
Tools: Where can I peer with Lambda AI? · Where should Lambda AI peer next? · Compare Lambda AI with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
One thing to fix in Lambda AI's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-11-19 12:40 UTC.
Make the changes on Lambda AI's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Lambda AI has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 206.41.110.59 IPv6 2001:504:41:110::59 Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 3 |
| Nov 18, 2026 | 3 |
| Nov 17, 2026 | 3 |
| Nov 16, 2026 | 3 |
| Nov 15, 2026 | 3 |
| Nov 14, 2026 | 3 |
| Nov 13, 2026 | 3 |
| Nov 12, 2026 | 3 |
| Nov 11, 2026 | 3 |
| Nov 10, 2026 | 3 |
| Nov 9, 2026 | 3 |
| Nov 8, 2026 | 3 |
| Nov 7, 2026 | 3 |
| Nov 6, 2026 | 3 |
| Nov 5, 2026 | 3 |
| Nov 4, 2026 | 3 |
| Nov 3, 2026 | 3 |
| Nov 2, 2026 | 3 |
| Nov 1, 2026 | 3 |
| Oct 31, 2026 | 3 |
| Oct 30, 2026 | 3 |
| Oct 29, 2026 | 3 |
| Oct 28, 2026 | 3 |
| Oct 27, 2026 | 3 |
| Oct 26, 2026 | 3 |
| Oct 25, 2026 | 3 |
| Oct 24, 2026 | 3 |
| Oct 23, 2026 | 3 |
| Oct 22, 2026 | 3 |
| Oct 21, 2026 | 3 |
| Oct 20, 2026 | 3 |
| Oct 19, 2026 | 3 |
| Oct 18, 2026 | 3 |
| Oct 17, 2026 | 3 |
| Oct 16, 2026 | 3 |
| Oct 15, 2026 | 3 |
| Oct 14, 2026 | 3 |
| Oct 13, 2026 | 3 |
| Oct 12, 2026 | 3 |
| Oct 11, 2026 | 3 |
| Oct 10, 2026 | 3 |
| Oct 9, 2026 | 3 |
| Oct 8, 2026 | 3 |
| Oct 7, 2026 | 3 |
| Oct 6, 2026 | 3 |
| Oct 5, 2026 | 3 |
| Oct 4, 2026 | 3 |
| Oct 3, 2026 | 3 |
Map
Where Lambda AI's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
| CANIX Montreal Montreal, Canada | 2 × 100G | Both | |
| ChIX Chicago, United States | 100G | PeeringDB only | |
| KCIX Kansas City, United States | 2 × 100G | Both |
These exchanges have a switch in a facility where Lambda AI lists itself in PeeringDB, but don't have Lambda AI as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.
| Any2WestLos Angeles and Silicon Valley, United States | 284 | |
| Equinix DallasDallas, United States | 211 | |
| NetIXSofia, Bulgaria | 204 | |
| DE-CIX DallasDallas, United States | 177 | |
| BBIX US-WestWest Coast, United States | 87 | |
| DE-CIX ChicagoChicago, United States | 86 | |
| QCIXDavenport, United States | 69 | |
| MegaIX DallasDallas, United States | 30 | |
| JumboIX PeruLima, Peru | 27 | |
| MegaIX Los AngelesLos Angeles, United States | 27 | |
| NYIIX Los AngelesLos Angeles, United States | 21 | |
| Any2ChicagoChicago, United States | 17 | |
| MegaIX ChicagoChicago, United States | 13 | |
| Digital Realty DallasDallas, United States | 12 | |
| DFW-IXDallas, United States | 11 | |
| Chicago Open PipesChicago, United States | 9 | |
| Global Peer ExchangeWashington, United States | 6 |
Facilities (6)
The buildings Lambda AI lists in PeeringDB, and how many of the exchanges in each it's on.
| CoreSite - Chicago (CH1)Chicago | 1 of 6 | |
| CoreSite - Los Angeles (LA1) One WilshireLos Angeles | 0 of 5 | |
| Equinix DA6 - DallasDallas | 0 of 5 | |
| Digital Realty DFW (2323 Bryan St)Dallas | 0 of 4 | |
| Netrality Kansas City - 1102 GrandKansas City | 1 of 2 | |
| Cologix MTL7Montreal | 1 of 1 |