Telehouse
AS57344 · AS-57344
Telehouse AD
Tools: Where can I peer with Telehouse? · Where should Telehouse peer next? · Compare Telehouse with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
13 things to fix in Telehouse's PeeringDB record, from what its exchanges publish: 13 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on Telehouse's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Correct these entries (13)
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 IPv4 address in PeeringDB, not in the export 185.1.30.26 185.1.30.40 185.1.30.45 185.1.30.57 185.1.30.58 185.1.30.85 185.1.30.111 185.1.30.116 185.1.30.120 185.1.30.126 185.1.30.143 185.1.30.144 185.1.30.26 185.1.30.40 185.1.30.45 185.1.30.57 185.1.30.58 185.1.30.111 185.1.30.116 185.1.30.120 185.1.30.126 185.1.30.143 185.1.30.144 Port speed differs 12 × 470G 470G - In the entry with IPv4 185.1.30.85: set IPv4 to (empty) (now 185.1.30.85).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 193.169.198.166 193.169.198.170 193.169.198.171 193.169.198.203 193.169.198.204 193.169.198.166 193.169.198.168 193.169.198.170 193.169.198.171 193.169.198.203 193.169.198.204 193.169.198.218 193.169.198.219 IPv6 address missing from PeeringDB none 2001:7f8:58::e000:0:1 - In the entry with IPv4 193.169.198.166: set IPv6 to 2001:7f8:58::e000:0:1 (now empty).
- Add an entry: IPv4 193.169.198.168, IPv6 –.
- Add an entry: IPv4 193.169.198.218, IPv6 –.
- Add an entry: IPv4 193.169.198.219, IPv6 –.
-
Problem PeeringDB has The export has Port speed differs 1G 100G - In the entry with IPv4 185.1.170.235: set Speed to 100000 (100G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 100G - In the entry with IPv4 185.1.210.204: set Speed to 100000 (100G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 2G 100G - In the entry with IPv4 185.1.192.241: set Speed to 100000 (100G) (now 2000).
-
Problem PeeringDB has The export has Port speed differs 1G 100G - In the entry with IPv4 185.1.208.213: set Speed to 100000 (100G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 2 × 100G 100G PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions 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 and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 2 × 20G 20G PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 20G - In the entry with IPv4 195.66.231.109: set Speed to 20000 (20G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 2 × 10G 10G -
Problem PeeringDB has The export has Port speed differs 100G 13.75G - In the entry with IPv4 185.0.20.82: set Speed to 13750 (13.75G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 2 × 10G 10G PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 31 |
| Nov 18, 2026 | 31 |
| Nov 17, 2026 | 31 |
| Nov 16, 2026 | 31 |
| Nov 15, 2026 | 31 |
| Nov 14, 2026 | 31 |
| Nov 13, 2026 | 31 |
| Nov 12, 2026 | 31 |
| Nov 11, 2026 | 31 |
| Nov 10, 2026 | 31 |
| Nov 9, 2026 | 31 |
| Nov 8, 2026 | 31 |
| Nov 7, 2026 | 31 |
| Nov 6, 2026 | 31 |
| Nov 5, 2026 | 31 |
| Nov 4, 2026 | 31 |
| Nov 3, 2026 | 31 |
| Nov 2, 2026 | 31 |
| Nov 1, 2026 | 31 |
| Oct 31, 2026 | 31 |
| Oct 30, 2026 | 31 |
| Oct 29, 2026 | 31 |
| Oct 28, 2026 | 31 |
| Oct 27, 2026 | 31 |
| Oct 26, 2026 | 31 |
| Oct 25, 2026 | 31 |
| Oct 24, 2026 | 31 |
| Oct 23, 2026 | 31 |
| Oct 22, 2026 | 31 |
| Oct 21, 2026 | 31 |
| Oct 20, 2026 | 31 |
| Oct 19, 2026 | 31 |
| Oct 18, 2026 | 31 |
| Oct 17, 2026 | 31 |
| Oct 16, 2026 | 31 |
| Oct 15, 2026 | 31 |
| Oct 14, 2026 | 31 |
| Oct 13, 2026 | 30 |
| Oct 12, 2026 | 30 |
| Oct 11, 2026 | 30 |
| Oct 10, 2026 | 30 |
| Oct 9, 2026 | 30 |
| Oct 8, 2026 | 30 |
| Oct 7, 2026 | 30 |
| Oct 6, 2026 | 30 |
| Oct 5, 2026 | 30 |
| Oct 4, 2026 | 30 |
| Oct 3, 2026 | 30 |
Map
Where Telehouse'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.
| AMS-IX Amsterdam, Netherlands | 20G | Both | |
| B-IX Sofia, Bulgaria | 12 × 470G | Both IPv4 not in exportSpeed differs | |
| Balcan-IX Bucharest, Romania | 2 × 10G | PeeringDB | |
| BIX Budapest, Hungary | 25G | Both | |
| BIX.BG Sofia, Bulgaria | 5 × 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| DE-CIX Dusseldorf Düsseldorf, Germany | 1G | Both Speed differs | |
| DE-CIX Frankfurt Frankfurt, Germany | 2 × 100G | Both | |
| DE-CIX Hamburg Hamburg, Germany | 1G | Both Speed differs | |
| DE-CIX Madrid Madrid, Spain | 2G | Both Speed differs | |
| DE-CIX Munich Munich, Germany | 1G | Both Speed differs | |
| DTEL-IX Kiev, Ukraine | 2 × 2G | PeeringDB | |
| ERA-IX Amsterdam Amsterdam, Netherlands | 2 × 10G | Both | |
| FogIXP Avers, Switzerland | 10G | Both | |
| France-IX Paris Paris, France | 100G | PeeringDB | |
| Frys-IX Fryslân, Netherlands | 100G | Both | |
| Global-IX Amsterdam, Netherlands | 100G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 2 × 100G | Both Speed differs | |
| GNM-IX UA Kiev, Ukraine | 100G | PeeringDB | |
| INTERIX Amsterdam, Netherlands | 2 × 100G | Both Speed differs | |
| InterLAN-IX Bucharest, Romania | 2 × 20G | Both Speed differs | |
| LINX LON1 London, United Kingdom | 10G | Both Speed differs | |
| LOCIX FRANKFURT Frankfurt am Main, Germany | 2 × 100G | PeeringDB | |
| LSIX Amsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands | 2 × 10G | Both Speed differs | |
| MINAP Milan Milan, Italy | 100G | Both | |
| MIX-IT Milan, Italy | 20G | Both | |
| NIX.CZ Prague, Czechia | 25G | Both | |
| NIX.SK Bratislava, Slovakia | 25G | Both | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 10G | Both | |
| Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia | 100G | Both Speed differs | |
| PITER-IX Frankfurt Frankfurt, Germany | 2 × 100G | PeeringDB | |
| Speed-IX Dronten, Netherlands | 2 × 10G | Both Speed differs |
These exchanges have a switch in a facility where Telehouse lists itself in PeeringDB, but don't have Telehouse 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.
| TPIX PLWarsaw, Poland | 480 | |
| KleyReXFrankfurt, Germany | 471 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine | 268 | |
| Equinix ParisParis, France | 239 | |
| 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 | |
| MegaIX FrankfurtFrankfurt, Germany | 114 | |
| ERA-IX FrankfurtFrankfurt, Germany | 85 | |
| Equinix FrankfurtFrankfurt, Germany | 78 | |
| BALT-IXVilnius, Lithuania | 77 | |
| SIX.SKBratislava, Slovakia | 71 | |
| FogIXP FrankfurtFrankfurt, Germany | 67 | |
| 1-NL FREEAmsterdam, Netherlands | 60 | |
| HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France | 58 | |
| FogIXP AmsterdamAmsterdam, Netherlands | 57 | |
| 91-IXFrankfurt, Germany | 53 | |
| RUDAKI-IXKiev, Ukraine | 53 | |
| Equinix AmsterdamAmsterdam, Netherlands | 51 | |
| Giganet IXN FrankfurtFrankfurt, Germany | 50 | |
| PyramIXCairo, Egypt | 48 | |
| Giganet IXN AmsterdamAmsterdam, Netherlands | 47 | |
| TurkIX SofiaSofia, Bulgaria | 47 | |
| SOX SerbiaBelgrade/Serbia, Serbia | 46 | |
| RoNIXBucharest, Romania | 43 | |
| Clue-IXAmsterdam, Netherlands | 36 | |
| Equinix MilanMilan, Italy | 35 | |
| GIBIRIXİstanbul, Türkiye | 28 | |
| 1-DE FREEFrankfurt, Germany | 27 | |
| Asteroid AmsterdamAmsterdam, Netherlands | 27 | |
| Community-IXBerlin, Frankfurt, Germany | 25 | |
| nine - six in ParisParis, France | 24 | |
| SFINXParis, France | 23 | |
| 1-BG FREESofia, Bulgaria | 22 | |
| MegaIX SofiaSofia, Bulgaria | 20 | |
| OpenCarrier OCIXDuesseldorf, Germany | 20 | |
| NL-ix 2Amsterdam, Netherlands | 19 | |
| RegPEXAnkara, Türkiye | 19 | |
| DSIXBucharest, Romania | 18 | |
| 1-FR FREEParis, France | 14 | |
| ERA-IX ParisParis, France | 14 | |
| EuroRhine-IXStrasbourg, France | 14 | |
| MAINPORT Peer-ExchangeFrankfurt am Main, Germany | 14 | |
| NVL-IXAthens, Greece | 14 | |
| NSIX AmsterdamAmsterdam, Netherlands | 13 | |
| AKIXZurich, Switzerland | 11 | |
| T-CIXSofia, Bulgaria | 9 | |
| NIX.CZ FENIXPrague, Czechia | 8 | |
| City-IX FrankfurtFrankfurt, Germany | 7 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| France-IX Paris EssentielParis, France | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| STACIXFrankfurt, Germany | 5 | |
| TMW-iXFrankfurt am Main, Germany | 5 | |
| Noord-IXLeeuwarden, Netherlands | 4 | |
| TievoluIXFrankfurt, Germany | 4 |
Facilities (25)
The buildings Telehouse lists in PeeringDB, and how many of the exchanges in each it's on.
Recent changes Search them
- Nov 14, 2026 [PDB] AS57344 Telehouse now in PeeringDB at BIX
- Nov 14, 2026 [PDB] AS57344 Telehouse no longer in PeeringDB at BIX (still on its IX-F list and on its website's members list)
- Oct 14, 2026 [PDB] AS57344 Telehouse added to GNM-IX UA