PathConnect
AS47536 · PathConnect GmbH
PathConnect GmbH
Tools: Where can I peer with PathConnect? · Where should PathConnect peer next? · Compare PathConnect with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
3 things to fix in PathConnect'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 PathConnect'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 PathConnect's PeeringDB record. Add one entry per connection with these values.
-
IPv4 193.189.83.160 IPv6 2001:7f8:33::a104:7536:1 Speed 100 Mbps (100M) 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.
-
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64From its IX-F export and website members list
IPv4 193.239.119.73 IPv6 2001:7f8:13::a504:7536:1 Speed Not published 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 (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 Port speed differs 2 × 25G 2 × 10G - In the entry with IPv4 185.1.147.108: set Speed to 10000 (10G) (now 25000).
- In the entry with IPv4 185.1.147.109: set Speed to 10000 (10G) (now 25000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 8 |
| Nov 18, 2026 | 8 |
| Nov 17, 2026 | 8 |
| Nov 16, 2026 | 8 |
| Nov 15, 2026 | 8 |
| Nov 14, 2026 | 8 |
| Nov 13, 2026 | 8 |
| Nov 12, 2026 | 8 |
| Nov 11, 2026 | 8 |
| Nov 10, 2026 | 8 |
| Nov 9, 2026 | 8 |
| Nov 8, 2026 | 8 |
| Nov 7, 2026 | 8 |
| Nov 6, 2026 | 8 |
| Nov 5, 2026 | 8 |
| Nov 4, 2026 | 8 |
| Nov 3, 2026 | 8 |
| Nov 2, 2026 | 8 |
| Nov 1, 2026 | 8 |
| Oct 31, 2026 | 8 |
| Oct 30, 2026 | 8 |
| Oct 29, 2026 | 8 |
| Oct 28, 2026 | 8 |
| Oct 27, 2026 | 8 |
| Oct 26, 2026 | 8 |
| Oct 25, 2026 | 8 |
| Oct 24, 2026 | 8 |
| Oct 23, 2026 | 8 |
| Oct 22, 2026 | 8 |
| Oct 21, 2026 | 8 |
| Oct 20, 2026 | 8 |
| Oct 19, 2026 | 8 |
| Oct 18, 2026 | 8 |
| Oct 17, 2026 | 8 |
| Oct 16, 2026 | 8 |
| Oct 15, 2026 | 8 |
| Oct 14, 2026 | 8 |
| Oct 13, 2026 | 8 |
| Oct 12, 2026 | 8 |
| Oct 11, 2026 | 8 |
| Oct 10, 2026 | 8 |
| Oct 9, 2026 | 8 |
| Oct 8, 2026 | 8 |
| Oct 7, 2026 | 8 |
| Oct 6, 2026 | 8 |
| Oct 5, 2026 | 8 |
| Oct 4, 2026 | 8 |
| Oct 3, 2026 | 8 |
Map
Where PathConnect'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.
| FogIXP Avers, Switzerland | 2 × 25G | Both Speed differs | |
| FogIXP Frankfurt Frankfurt, Germany | 2 × 25G | PeeringDB | |
| Giganet IXN Amsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine | 10G | PeeringDB | |
| Giganet IXN Frankfurt Frankfurt, Germany | 10G | PeeringDB | |
| KleyReX Frankfurt, Germany | 100M | Not in PeeringDB | |
| LOCIX FRANKFURT Frankfurt am Main, Germany | 10G | PeeringDB | |
| MAINPORT Peer-Exchange Frankfurt am Main, Germany | 10G | Both | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | Not in PeeringDB |
These exchanges have a switch in a facility where PathConnect lists itself in PeeringDB, but don't have PathConnect 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 | |
| GNM-IXAmsterdam, Netherlands | 741 | |
| TPIX PLWarsaw, Poland | 480 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| NIX.CZPrague, Czechia | 225 | |
| Peering.czPrague, Bratislava, Vienna, Frankfurt, Czechia | 207 | |
| NetIXSofia, Bulgaria | 204 | |
| THINX WarsawWarsaw, Poland | 194 | |
| PITER-IX FrankfurtFrankfurt, Germany | 172 | |
| 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 | |
| MegaIX FrankfurtFrankfurt, Germany | 114 | |
| ERA-IX FrankfurtFrankfurt, Germany | 85 | |
| Equinix FrankfurtFrankfurt, Germany | 78 | |
| BALT-IXVilnius, Lithuania | 77 | |
| NIX.SKBratislava, Slovakia | 68 | |
| 91-IXFrankfurt, Germany | 53 | |
| RoNIXBucharest, Romania | 43 | |
| Balcan-IXBucharest, Romania | 29 | |
| 1-DE FREEFrankfurt, Germany | 27 | |
| NIX.CZ FENIXPrague, Czechia | 8 | |
| City-IX FrankfurtFrankfurt, Germany | 7 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 |
Facilities (3)
The buildings PathConnect lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix FR5 - Frankfurt, KleyerStrasseFrankfurt | 8 of 33 | |
| Equinix FR7 - Frankfurt, GutleutstrasseFrankfurt | 3 of 12 | |
| NTT Frankfurt 1 Data Center (FRA1)Frankfurt | 4 of 8 |