DACS-NX Legacy Network
AS40217
DACS Network Exchange
Tools: Where can I peer with DACS-NX Legacy Network? · Where should DACS-NX Legacy Network peer next? · Compare DACS-NX Legacy Network with another network
This network elsewhere: its registry history on RIR Tracker
PeeringDB fix list Printable page · CSV
3 things to fix in DACS-NX Legacy Network's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on DACS-NX Legacy Network's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (2)
On the exchange's own member list, but not in DACS-NX Legacy Network's PeeringDB record. Add one entry per connection with these values.
-
IPv4 206.80.238.171 IPv6 2001:504:91::171 Speed Not published RS peer Not published -
IPv4 206.197.187.105 IPv6 2001:504:30::ba04:217:1 Speed 10000 Mbps (10G) RS peer Not published
Correct these entries (1)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 206.197.187.105 is AS6515 DACS NX 206.197.187.105 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 2 |
| Nov 18, 2026 | 2 |
| Nov 17, 2026 | 2 |
| Nov 16, 2026 | 2 |
| Nov 15, 2026 | 2 |
| Nov 14, 2026 | 2 |
| Nov 13, 2026 | 2 |
| Nov 12, 2026 | 2 |
| Nov 11, 2026 | 2 |
| Nov 10, 2026 | 2 |
| Nov 9, 2026 | 2 |
| Nov 8, 2026 | 2 |
| Nov 7, 2026 | 2 |
| Nov 6, 2026 | 2 |
| Nov 5, 2026 | 2 |
| Nov 4, 2026 | 2 |
| Nov 3, 2026 | 2 |
| Nov 2, 2026 | 2 |
| Nov 1, 2026 | 2 |
| Oct 31, 2026 | 2 |
| Oct 30, 2026 | 2 |
| Oct 29, 2026 | 2 |
| Oct 28, 2026 | 2 |
| Oct 27, 2026 | 2 |
| Oct 26, 2026 | 2 |
| Oct 25, 2026 | 2 |
| Oct 24, 2026 | 2 |
| Oct 23, 2026 | 2 |
| Oct 22, 2026 | 2 |
| Oct 21, 2026 | 2 |
| Oct 20, 2026 | 2 |
| Oct 19, 2026 | 2 |
| Oct 18, 2026 | 2 |
| Oct 17, 2026 | 2 |
| Oct 16, 2026 | 2 |
| Oct 15, 2026 | 2 |
| Oct 14, 2026 | 2 |
| Oct 13, 2026 | 2 |
| 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 DACS-NX Legacy Network'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.
| FCIX Fremont, United States | Not in PeeringDB | ||
| SFMIX San Francisco, United States | 10G | Not in PeeringDB Address taken |
These exchanges have a switch in a facility where DACS-NX Legacy Network lists itself in PeeringDB, but don't have DACS-NX Legacy Network 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.
| Equinix AshburnAshburn, United States | 347 | |
| DE-CIX New YorkNew York, United States | 281 | |
| EVIXFremont, United States | 227 | |
| NetIXSofia, Bulgaria | 204 | |
| NYIIX New YorkNew York, United States | 186 | |
| FREMIXFremont, United States | 141 | |
| NVIXAshburn, United States | 78 | |
| LINX NoVAAshburn, Reston, Manassas, United States | 57 | |
| Any2EastWashington DC, Reston, Boston, New York, Atlanta, United States | 50 | |
| MegaIX AshburnAshburn, United States | 49 | |
| CIX-NoVAAshburn, Reston, Washington DC, United States | 34 | |
| PR-IXSan Juan, Puerto Rico | 33 | |
| ARIXFremont, Portland, Flagstaff, United States | 22 | |
| Lambda-IXFremont, United States | 22 | |
| MegaIX New YorkNew York, United States | 22 | |
| MegaIX Bay AreaSan Francisco, United States | 21 | |
| DACS-IX EastWashington DC, United States | 15 | |
| Zero Internet eXchange San JoseSan Jose, United States | 15 | |
| DACS-IX WestSilicon Valley, United States | 14 | |
| DACS-IX CentralChicago, United States | 7 | |
| Global Peer ExchangeWashington, United States | 6 | |
| Ninja-IX Bay AreaNorthern California, United States | 6 | |
| GNM-IX USNew York, United States | 4 | |
| Nell-IX NoVAReston, United States | 4 | |
| ixFabricGlobal, Australia | 2 |
Facilities (11)
The buildings DACS-NX Legacy Network lists in PeeringDB, and how many of the exchanges in each it's on.
| Hurricane Electric Fremont 2Fremont | 2 of 12 | |
| Equinix DC1-DC15,DC21-DC22 - AshburnAshburn | 0 of 9 | |
| CoreSite - Reston (VA1)Reston | 0 of 6 | |
| Telehouse - New York ChelseaNew York | 0 of 4 | |
| Databridge Sites Silver SpringSilver Spring | 0 of 2 | |
| Crown Castle Baltimore (111 Market, 700 E Pratt)Baltimore | 0 of 1 | |
| DataBridge Sites AuroraAurora | 0 of 1 | |
| Flexential - Las Vegas/North (LAS04)North Las Vegas | 0 of 1 | |
| Zayo Baltimore - 111 Market PlBaltimore | 0 of 1 | |
| Colo Solutions Downtown OrlandoOrlando | No exchange | |
| Databank Atlanta (ATL1)Atlanta | No exchange |
Recent changes Search them
- Oct 13, 2026 [WEB] AS40217 DACS-NX Legacy Network left FREMIX