DE-CIX Richmond
Ashland, United States · North America
Operated by DE-CIX Group AG · 1 ghost exchange
Who's on DE-CIX Richmond, by source
16 of 28 match: 16 in every source2 in PeeringDB, but on only one of the IX-F list and the website list5 published by the exchange, not in PeeringDB5 in PeeringDB, not on the exchange's own lists
IX-F export: https://portal.de-cix.net/customer_ric, read 2026-11-19 12:22 UTC.
Members list on the website: https://www.de-cix.net/en/locations/richmond/connected-networks (the page loads its list from https://www.de-cix.net/api/networks/RIC), read 2026-11-19 12:22 UTC.
Ports and fees
| Port | Price | Billed | In use |
|---|---|---|---|
| 1G | – | – | 6 |
| 10G | – | – | 7 |
| 100G | – | – | 5 |
Every port speed DE-CIX Richmond lists, plus every speed members are connected at (from its IX-F export).
Prices on request: DE-CIX Richmond doesn't publish its port fees; it asks you to contact it (https://www.de-cix.net/en/services, checked 2026-11-19 12:23 UTC).
How members connect
- Virtual IX
- No: per its IX-F export, 0 of 23 members whose connection its IX-F export describes connect by tunnel.
- In its IX-F export
- 0 by tunnel, 23 on a physical port, 0 not given
- Facilities it lists
- 3 in PeeringDB
- Members with a building in United States
- 14 of the 17 members that list any building in PeeringDB (28 members in all)
- Members' countries
- 4 (where their organizations are, in PeeringDB)
Members over time
Show as a table
| Date | IX-F | Website | PeeringDB |
|---|---|---|---|
| Nov 19, 2026 | 23 | 21 | 23 |
| Nov 18, 2026 | 23 | 21 | 23 |
| Nov 17, 2026 | 23 | 21 | 23 |
| Nov 16, 2026 | 23 | 21 | 23 |
| Nov 15, 2026 | 23 | 21 | 23 |
| Nov 14, 2026 | 23 | 21 | 23 |
| Nov 13, 2026 | 23 | 21 | 23 |
| Nov 12, 2026 | 23 | 21 | 23 |
| Nov 11, 2026 | 23 | 21 | 23 |
| Nov 10, 2026 | 23 | 21 | 23 |
| Nov 9, 2026 | 23 | 21 | 23 |
| Nov 8, 2026 | 23 | 21 | 23 |
| Nov 7, 2026 | 23 | 21 | 23 |
| Nov 6, 2026 | 23 | 21 | 23 |
| Nov 5, 2026 | 23 | 21 | 23 |
| Nov 4, 2026 | 23 | 21 | 23 |
| Nov 3, 2026 | 23 | 21 | 23 |
| Nov 2, 2026 | 23 | 21 | 23 |
| Nov 1, 2026 | 23 | 21 | 23 |
| Oct 31, 2026 | 23 | 21 | 23 |
| Oct 30, 2026 | 23 | 21 | 23 |
| Oct 29, 2026 | 23 | 21 | 23 |
| Oct 28, 2026 | 23 | 21 | 23 |
| Oct 27, 2026 | 23 | 21 | 23 |
| Oct 26, 2026 | 23 | 21 | 23 |
| Oct 25, 2026 | 23 | 21 | 23 |
| Oct 24, 2026 | 23 | 21 | 23 |
| Oct 23, 2026 | 23 | 21 | 23 |
| Oct 22, 2026 | 23 | 21 | 23 |
| Oct 21, 2026 | – | 21 | 23 |
| Oct 20, 2026 | 23 | 21 | 23 |
| Oct 19, 2026 | 24 | 21 | 23 |
| Oct 18, 2026 | 24 | 21 | 23 |
| Oct 17, 2026 | 24 | 21 | 23 |
| Oct 16, 2026 | 24 | 21 | 23 |
| Oct 15, 2026 | 23 | 21 | 23 |
| Oct 14, 2026 | 23 | 21 | 23 |
| Oct 13, 2026 | 23 | 21 | 23 |
| Oct 12, 2026 | 23 | 21 | 23 |
| Oct 11, 2026 | 23 | 21 | 23 |
| Oct 10, 2026 | 23 | 21 | 23 |
| Oct 9, 2026 | 23 | 21 | 23 |
| Oct 8, 2026 | 23 | 21 | 23 |
| Oct 7, 2026 | 23 | 21 | 23 |
| Oct 6, 2026 | 23 | 21 | 23 |
| Oct 5, 2026 | 23 | 21 | 23 |
| Oct 4, 2026 | 23 | 21 | 23 |
| Oct 3, 2026 | 23 | – | 23 |
| Oct 2, 2026 | – | – | 23 |
Traffic, last week
Show as a table
| Time | Traffic |
|---|---|
| Thu Nov 19, 12:00 UTC | 10.2 Gbps |
| Thu Nov 19, 06:00 UTC | 4.57 Gbps |
| Thu Nov 19, 00:00 UTC | 14.7 Gbps |
| Wed Nov 18, 18:00 UTC | 9.46 Gbps |
| Wed Nov 18, 12:00 UTC | 10.9 Gbps |
| Wed Nov 18, 06:00 UTC | 4.59 Gbps |
| Wed Nov 18, 00:00 UTC | 14.4 Gbps |
| Tue Nov 17, 18:00 UTC | 10.1 Gbps |
| Tue Nov 17, 12:00 UTC | 11.1 Gbps |
| Tue Nov 17, 06:00 UTC | 5.32 Gbps |
| Tue Nov 17, 00:00 UTC | 13.7 Gbps |
| Mon Nov 16, 18:00 UTC | 10.7 Gbps |
| Mon Nov 16, 12:00 UTC | 11.2 Gbps |
| Mon Nov 16, 06:00 UTC | 5.83 Gbps |
| Mon Nov 16, 00:00 UTC | 15.4 Gbps |
| Sun Nov 15, 18:00 UTC | 11.9 Gbps |
| Sun Nov 15, 12:00 UTC | 11.4 Gbps |
| Sun Nov 15, 06:00 UTC | 7.27 Gbps |
| Sun Nov 15, 00:00 UTC | 14.3 Gbps |
| Sat Nov 14, 18:00 UTC | 11.8 Gbps |
| Sat Nov 14, 12:00 UTC | 11.5 Gbps |
| Sat Nov 14, 06:00 UTC | 6.73 Gbps |
| Sat Nov 14, 00:00 UTC | 12.9 Gbps |
| Fri Nov 13, 18:00 UTC | 10.1 Gbps |
| Fri Nov 13, 12:00 UTC | 11.6 Gbps |
| Fri Nov 13, 06:00 UTC | 6.21 Gbps |
| Fri Nov 13, 00:00 UTC | 15 Gbps |
| Thu Nov 12, 18:00 UTC | 10.2 Gbps |
Daily peak over time
The highest point each day on the traffic graph DE-CIX Richmond publishes, for every complete day read.
Show as a table
| Date | Daily peak |
|---|---|
| Nov 18, 2026 | 16.2 Gbps |
| Nov 17, 2026 | 15.1 Gbps |
| Nov 16, 2026 | 16.6 Gbps |
| Nov 15, 2026 | 15.1 Gbps |
| Nov 14, 2026 | 16.5 Gbps |
| Nov 13, 2026 | 16.4 Gbps |
| Nov 12, 2026 | 16.9 Gbps |
| Nov 11, 2026 | 18.4 Gbps |
| Nov 10, 2026 | 16.6 Gbps |
| Nov 9, 2026 | 17.5 Gbps |
| Nov 8, 2026 | 16.7 Gbps |
| Nov 7, 2026 | 15.6 Gbps |
| Nov 6, 2026 | 16.9 Gbps |
| Nov 4, 2026 | 17.3 Gbps |
| Nov 3, 2026 | 16.9 Gbps |
| Nov 2, 2026 | 17.5 Gbps |
| Nov 1, 2026 | 15.8 Gbps |
| Oct 31, 2026 | 15.1 Gbps |
| Oct 30, 2026 | 16.3 Gbps |
| Oct 29, 2026 | 16.3 Gbps |
| Oct 28, 2026 | 17 Gbps |
| Oct 27, 2026 | 16.6 Gbps |
| Oct 26, 2026 | 17.3 Gbps |
| Oct 25, 2026 | 18 Gbps |
| Oct 24, 2026 | 15.2 Gbps |
| Oct 23, 2026 | 16.4 Gbps |
| Oct 22, 2026 | 16.2 Gbps |
| Oct 21, 2026 | 15.4 Gbps |
| Oct 20, 2026 | 16.2 Gbps |
| Oct 19, 2026 | 16.5 Gbps |
| Oct 18, 2026 | 17 Gbps |
| Oct 17, 2026 | 17.3 Gbps |
| Oct 16, 2026 | 16.2 Gbps |
| Oct 15, 2026 | 15.2 Gbps |
| Oct 14, 2026 | 16.4 Gbps |
| Oct 13, 2026 | 15.9 Gbps |
| Oct 12, 2026 | 16 Gbps |
| Oct 11, 2026 | 16.3 Gbps |
| Oct 10, 2026 | 17 Gbps |
| Oct 9, 2026 | 15.7 Gbps |
| Oct 8, 2026 | 15.7 Gbps |
| Oct 7, 2026 | 16.6 Gbps |
| Oct 6, 2026 | 15.2 Gbps |
Published by DE-CIX Richmond: source, read 2026-11-19 12:23 UTC.
Exchange details
- Media
- Ethernet
- Protocols
- Unicast IPv4, IPv6
- MTU
- 1500
- Service level
- 24/7 Support
- Terms
- Recurring Fees
- Traffic stats
- www.de-cix.net/locations/richmond/statistics
- Technical
- support@de-cix.net
- Policy
- sales@de-cix.net
- PeeringDB record
- Updated 2023-10-06
Peering LAN prefixes
- 206.53.137.0/24IPv4
- 2001:504:44::/64IPv6
Facilities (3)
- EdgeConneX Richmond (EDCRIC01)Richmond
- Pixel Factory Data CenterAshland
- QTS Richmond (RIC1)Sandston
Route servers
17 networks have a session up with DE-CIX Richmond's route servers (6 more are configured but down), and 15 of them send routes: evidence they're really connected and peering, not just listed. Networks that only peer directly (bilaterally) don't show here. The routes column in the table below has each network's count.
From the public looking glass at lg.de-cix.net (rs1.ric.de-cix.net (IPv4), rs1.ric.de-cix.net (IPv6)), read 2026-11-18 18:37 UTC; one route server per address family, IPv4 and IPv6 counted together. How this is read
Data status
What the last update (every 6 hours) found for DE-CIX Richmond, step by step.
- IX-F export in PeeringDB The exchange hasn't published an IX-F export URL in PeeringDB.
- IX-F database (IXPDB) https://portal.de-cix.net/customer_ric
- Website search Members page already known (checked 2026-11-17).
- Member list Read 2026-11-19 12:22 UTC from the IX-F export.
- Member page 21 networks on https://www.de-cix.net/en/locations/richmond/connected-networks, which loads https://www.de-cix.net/api/networks/RIC, read 2026-11-19.
- Port fees https://www.de-cix.net/en/services couldn't be read:
- Route server looking glass 17 sessions up (6 down) on rs1.ric.de-cix.net (IPv4), rs1.ric.de-cix.net (IPv6), read 2026-11-18 18:37 UTC from https://lg.de-cix.net.
Fix list
Networks where PeeringDB and what DE-CIX Richmond publishes (its IX-F export and its website's members list) disagree. Download CSV Operator report with contacts
Published by the exchange, missing from PeeringDB (5)
These networks could add DE-CIX Richmond to their PeeringDB record.
Addresses and port speeds
Each network's IP addresses and port speed in PeeringDB, against DE-CIX Richmond's IX-F export, for the 18 networks in both. 11 have differences. Download CSV Operator report with contacts
PeeringDB's IX-F import is off for DE-CIX Richmond. With it on, PeeringDB would suggest these corrections to the networks.
IPv6 address differs (3)
| AS13335 Cloudflare | 2001:504:44::1:3335:1 | 2001:504:44::3417:0:1 |
| AS25152 RIPE NCC K-Root Operations | 2001:504:44::2:5152:1 | 2001:504:44::6240:0:1 |
| AS53907 QTS Richmond | 2001:504:44::5:3907:1 | 2001:504:44::d293:0:1 |
IPv4 address missing from PeeringDB (1)
| AS393752 DE-CIX Richmond Route Servers | 206.53.137.252 206.53.137.253 |
206.53.137.66 206.53.137.252 206.53.137.253 |
IPv6 address missing from PeeringDB (3)
| AS10248 Blue Ridge Bankshares | none | 2001:504:44::2808:0:1 |
| AS26202 Planet Fiber VA | none | 2001:504:44::665a:0:1 |
| AS393752 DE-CIX Richmond Route Servers | 2001:504:44:0:6:218:a:1 2001:504:44:0:6:218:a:2 |
2001:504:44:0:6:218:a:1 2001:504:44:0:6:218:a:2 2001:504:44:0:6:218:b:dead |
Port speed differs (7)
| AS112 DNS-OARC-112 | 10G | 20G |
| AS19919 VA SkyWire, LLC | 20G + 10G | 2 × 20G |
| AS26202 Planet Fiber VA | 10G | 1G |
| AS205530 DE-CIX R&D Measurement | 100M | 10G |
| AS212232 BGP.Tools Route Collector | 100M | 1G |
| AS393752 DE-CIX Richmond Route Servers | 2 × 10G | 3 × 20G |
| AS397005 Central Virginia Services | 20G | 100G |
Recent changes Search them
- Oct 20, 2026 IXFAS32934 Meta left DE-CIX Richmond
- Oct 16, 2026 IXFAS32934 Meta added to DE-CIX Richmond
- Oct 4, 2026 WEBMember list now reading DE-CIX Richmond's website members list (21 members)
| AS42 | PCH AS42Exchange lists it as “Packet Clearing House” | 206.53.137.26 | 1G | PeeringDB IX-FWebsite |
| AS112 | DNS-OARC-112Exchange lists it as “AS112” | 206.53.137.112 | 10G | PeeringDB IX-FWebsite |
| AS3580 | Planet Networks | 206.53.137.4 | 100G | PeeringDB IX-FWebsite |
| AS3856 | PCH AS3856Exchange lists it as “Packet Clearing House” | 206.53.137.25 | 1G | PeeringDB IX-FWebsite |
| AS6939 | Hurricane Electric | 206.53.137.34 | 100G | PeeringDB IX-FWebsite |
| AS10248 | Blue Ridge BanksharesExchange lists it as “Blue Ridge Bankshares, Inc.” | 206.53.137.1 | PeeringDB IX-FWebsite | |
| AS11187 | HVENS | 206.53.137.22 | 10G | PeeringDB IX-FWebsite |
| AS13335 | CloudflareExchange lists it as “Cloudflare, Inc” | 206.53.137.36 | 20G | PeeringDB IX-FWebsite |
| AS16708 | Telcom Systems LLC | 206.53.137.40 | 10G | PeeringDB IX-FWebsiteNot in PeeringDB |
| AS19919 | VA SkyWire, LLC | 206.53.137.23 206.53.137.24 |
20G + 10G | PeeringDB IX-FWebsite |
| AS21681 | Empower | 206.53.137.46 | 10G | PeeringDB IX-FWebsite |
| AS25152 | RIPE NCC K-Root OperationsExchange lists it as “RIPE K-ROOT-SERVER” | 206.53.137.20 | 1G | PeeringDB IX-FWebsite |
| AS26202 | Planet Fiber VAExchange lists it as “Planet Networks” | 206.53.137.30 | 10G | PeeringDB IX-FWebsite |
| AS26415 | VeriSign Global Registry ServicesExchange lists it as “VeriSign” | 206.53.137.32 | 10G | PeeringDB IX-FWebsiteNot in PeeringDB |
| AS32425 | Pixel Factory Data Center | 206.53.137.3 | 100G | PeeringDB IX-FWebsite |
| AS40091 | WVVA.netExchange lists it as “GigaBeam Networks LLC” | 206.53.137.48 | 10G | PeeringDB IX-FWebsiteNot in PeeringDB |
| AS51531 | DE-CIX Management GmbH | 206.53.137.110 206.53.137.116 |
2 × 1G | PeeringDB IX-FWebsite |
| AS53907 | QTS RichmondExchange lists it as “Quality Technology Services, LLC” | 206.53.137.38 | 10G | PeeringDB IX-FWebsite |
| AS63293 | Meta AS63293Exchange lists it as “Meta” | 206.53.137.42 | 100G | PeeringDB IX-FWebsite |
| AS205529 | DE-CIX MonitoringExchange lists it as “DE-CIX Richmond” | 206.53.137.249 | 20G | PeeringDB IX-FWebsite |
| AS205530 | DE-CIX R&D MeasurementExchange lists it as “DE-CIX Management GmbH, Research & Development” | 206.53.137.5 | 100M | PeeringDB IX-FWebsite |
| AS212232 | BGP.Tools Route CollectorExchange lists it as “Port 179 Ltd” | 206.53.137.2 | 100M | PeeringDB IX-FWebsite |
| AS393752 | DE-CIX Richmond Route ServersExchange lists it as “DE-CIX Richmond” | 206.53.137.252 206.53.137.253 |
2 × 10G | PeeringDB IX-FWebsite |
| AS394387 | Virginia Union University | 206.53.137.27 | 10G | PeeringDB IX-FWebsiteNot in PeeringDB |
| AS395100 | Roanoke Valley Broadband Authority | 206.53.137.29 | 1G | PeeringDB IX-FWebsiteNot in PeeringDB |
| AS396219 | Craig Botetourt Electric Cooperative | 206.53.137.52 | 1G | PeeringDB IX-FWebsite |
| AS397005 | Central Virginia ServicesExchange lists it as “FireFly” | 206.53.137.41 | 20G | PeeringDB IX-FWebsite |
| AS397156 | RuralBand/PGEC | 206.53.137.49 | 1G | PeeringDB IX-FWebsite |