LWLcom
AS50629 · LWLcom
LWLcom GmbH
Tools: Where can I peer with LWLcom? · Where should LWLcom peer next? · Compare LWLcom with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
8 things to fix in LWLcom's PeeringDB record, from what its exchanges publish: 4 to add, 3 to correct, 1 to check. As of 2026-11-19 18:41 UTC.
Make the changes on LWLcom'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 (4)
On the exchange's own member list, but not in LWLcom's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.170.10 IPv6 2001:7f8:9e::c5c5:0:1 Speed 10000 Mbps (10G) RS peer Yes -
IPv4 185.1.210.22 IPv6 2001:7f8:3d::c5c5:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 185.1.208.13 IPv6 2001:7f8:44::c5c5:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 193.189.83.39 IPv6 2001:7f8:33::a105:629:1 Speed 2500 Mbps (2.5G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Correct these entries (3)
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 Port speed differs 100G 10G - In the entry with IPv4 193.178.185.11: set Speed to 10000 (10G) (now 100000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 2 × 100G 100G PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 100G 12.5G - In the entry with IPv4 185.0.20.137: set Speed to 12500 (12.5G) (now 100000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If LWLcom has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 185.1.74.19 IPv6 2001:7f8:a5::5:629:2 Speed 100000 Mbps (100G) IPv4 185.1.74.30 IPv6 2001:7f8:a5::5:629:3 Speed 20000 Mbps (20G) 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 | 29 |
| Nov 18, 2026 | 29 |
| Nov 17, 2026 | 29 |
| Nov 16, 2026 | 29 |
| Nov 15, 2026 | 29 |
| Nov 14, 2026 | 29 |
| Nov 13, 2026 | 29 |
| Nov 12, 2026 | 29 |
| Nov 11, 2026 | 29 |
| Nov 10, 2026 | 29 |
| Nov 9, 2026 | 29 |
| Nov 8, 2026 | 29 |
| Nov 7, 2026 | 29 |
| Nov 6, 2026 | 29 |
| Nov 5, 2026 | 29 |
| Nov 4, 2026 | 29 |
| Nov 3, 2026 | 29 |
| Nov 2, 2026 | 29 |
| Nov 1, 2026 | 29 |
| Oct 31, 2026 | 29 |
| Oct 30, 2026 | 29 |
| Oct 29, 2026 | 29 |
| Oct 28, 2026 | 29 |
| Oct 27, 2026 | 29 |
| Oct 26, 2026 | 29 |
| Oct 25, 2026 | 29 |
| Oct 24, 2026 | 29 |
| Oct 23, 2026 | 29 |
| Oct 22, 2026 | 29 |
| Oct 21, 2026 | 29 |
| Oct 20, 2026 | 29 |
| Oct 19, 2026 | 29 |
| Oct 18, 2026 | 29 |
| Oct 17, 2026 | 29 |
| Oct 16, 2026 | 29 |
| Oct 15, 2026 | 29 |
| Oct 14, 2026 | 29 |
| Oct 13, 2026 | 29 |
| Oct 12, 2026 | 29 |
| Oct 11, 2026 | 29 |
| Oct 10, 2026 | 29 |
| Oct 9, 2026 | 29 |
| Oct 8, 2026 | 29 |
| Oct 7, 2026 | 29 |
| Oct 6, 2026 | 29 |
| Oct 5, 2026 | 29 |
| Oct 4, 2026 | 29 |
| Oct 3, 2026 | 29 |
Map
Where LWLcom'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.
| 1-DE FREE Frankfurt, Germany | 100G | PeeringDB | |
| 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 100G | Both | |
| AMS-IX Amsterdam, Netherlands | 20G | Both | |
| BCIX Berlin, Germany | 100G | Both Speed differs | |
| BREM-IX Bremen, Germany | 10G | Both | |
| Community-IX Berlin, Frankfurt, Germany | 100G + 20G | PeeringDB only | |
| DE-CIX Dusseldorf Düsseldorf, Germany | 10G | Not in PeeringDB | |
| DE-CIX Hamburg Hamburg, Germany | 100G | Not in PeeringDB | |
| DE-CIX Munich Munich, Germany | 100G | Not in PeeringDB | |
| DO-IX Dortmund, Germany | 100G | Both | |
| ERA-IX Amsterdam Amsterdam, Netherlands | 100G | Both | |
| ERA-IX Frankfurt Frankfurt, Germany | 100G | Both | |
| FogIXP Frankfurt Frankfurt, Germany | 10G | PeeringDB | |
| Frys-IX Fryslân, Netherlands | 100G | Both | |
| GNM-IX Amsterdam, Netherlands | 2 × 100G | Both Speed differs | |
| INTERIX Amsterdam, Netherlands | 100G | Both | |
| KleyReX Frankfurt, Germany | 2.5G | Not in PeeringDB | |
| LOCIX DUSSELDORF Dusseldorf, Germany | 10G | PeeringDB | |
| LOCIX FRANKFURT Frankfurt am Main, Germany | 100G | PeeringDB | |
| MAINPORT Peer-Exchange Frankfurt am Main, Germany | 100G | Both | |
| MegaIX Dusseldorf Dusseldorf, Germany | 100G | Both | |
| MegaIX Frankfurt Frankfurt, Germany | 100G | Both | |
| MegaIX Hamburg Hamburg, Germany | 100G | Both | |
| MegaIX Munich Munich, Germany | 100G | Both | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 25G | Both | |
| Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia | 100G | Both Speed differs | |
| PITER-IX Frankfurt Frankfurt, Germany | 100G | PeeringDB | |
| Speed-IX Dronten, Netherlands | 10G | Both | |
| VIX Vienna, Austria | 10G | Both |
These exchanges have a switch in a facility where LWLcom lists itself in PeeringDB, but don't have LWLcom 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.
| DE-CIX FrankfurtFrankfurt, Germany | 1,075 | |
| FogIXPAvers, Switzerland | 532 | |
| TPIX PLWarsaw, Poland | 480 | |
| Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine | 268 | |
| NIX.CZPrague, Czechia | 225 | |
| NetIXSofia, Bulgaria | 204 | |
| THINX WarsawWarsaw, Poland | 194 | |
| ixFabric - AmsterdamAmsterdam, Netherlands | 181 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| InterLAN-IXBucharest, Romania | 149 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| BIXBudapest, Hungary | 122 | |
| LSIXAmsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands | 105 | |
| Equinix FrankfurtFrankfurt, Germany | 78 | |
| B-IXSofia, Bulgaria | 77 | |
| BALT-IXVilnius, Lithuania | 77 | |
| NIX.SKBratislava, Slovakia | 68 | |
| 1-NL FREEAmsterdam, Netherlands | 60 | |
| HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France | 58 | |
| FogIXP AmsterdamAmsterdam, Netherlands | 57 | |
| Equinix AmsterdamAmsterdam, Netherlands | 51 | |
| BBIX AmsterdamAmsterdam, Netherlands | 50 | |
| Giganet IXN FrankfurtFrankfurt, Germany | 50 | |
| PyramIXCairo, Egypt | 48 | |
| Giganet IXN AmsterdamAmsterdam, Netherlands | 47 | |
| MegaIX BerlinBerlin, Germany | 43 | |
| RoNIXBucharest, Romania | 43 | |
| Clue-IXAmsterdam, Netherlands | 36 | |
| Balcan-IXBucharest, Romania | 29 | |
| Asteroid AmsterdamAmsterdam, Netherlands | 27 | |
| NeverIX VelbertVelbert, Germany | 22 | |
| OpenCarrier OCIXDuesseldorf, Germany | 20 | |
| NL-ix 2Amsterdam, Netherlands | 19 | |
| RegPEXAnkara, Türkiye | 19 | |
| NSIX AmsterdamAmsterdam, Netherlands | 13 | |
| AKIXZurich, Switzerland | 11 | |
| NIX.CZ FENIXPrague, Czechia | 8 | |
| City-IX FrankfurtFrankfurt, Germany | 7 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| SBIX DusseldorfDusseldorf, Germany | 5 | |
| STACIXFrankfurt, Germany | 5 | |
| TMW-iXFrankfurt am Main, Germany | 5 | |
| Noord-IXLeeuwarden, Netherlands | 4 | |
| TievoluIXFrankfurt, Germany | 4 |
Facilities (33)
The buildings LWLcom lists in PeeringDB, and how many of the exchanges in each it's on.