colocatel-inc
AS213438 · Colocatel Network.
ColocaTel Inc.
Tools: Where can I peer with colocatel-inc? · Where should colocatel-inc peer next? · Compare colocatel-inc with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
5 things to fix in colocatel-inc's PeeringDB record, from what its exchanges publish: 1 to add, 4 to correct. As of 2026-11-19 18:41 UTC.
Make the changes on colocatel-inc'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 (1)
On the exchange's own member list, but not in colocatel-inc's PeeringDB record. Add one entry per connection with these values.
-
1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From its website members list
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Correct these entries (4)
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 IPv6 address missing from PeeringDB none 2001:7f8:12a::13 - In the entry with IPv4 185.1.240.13: set IPv6 to 2001:7f8:12a::13 (now empty).
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 IPv6 address missing from PeeringDB none 2001:7f8:10f::3:41be:300 - In the entry with IPv4 185.1.161.45: set IPv6 to 2001:7f8:10f::3:41be:300 (now empty).
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 IPv6 address missing from PeeringDB none 2a03:5f80:4:2::237:102 - In the entry with IPv4 178.18.237.102: set IPv6 to 2a03:5f80:4:2::237:102 (now empty).
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 IPv6 address missing from PeeringDB none 2001:7f8:134::7a - In the entry with IPv4 185.1.184.142: set IPv6 to 2001:7f8:134::7a (now empty).
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 | 6 |
| Nov 18, 2026 | 6 |
| Nov 17, 2026 | 6 |
| Nov 16, 2026 | 6 |
| Nov 15, 2026 | 6 |
| Nov 14, 2026 | 6 |
| Nov 13, 2026 | 6 |
| Nov 12, 2026 | 6 |
| Nov 11, 2026 | 6 |
| Nov 10, 2026 | 6 |
| Nov 9, 2026 | 6 |
| Nov 8, 2026 | 6 |
| Nov 7, 2026 | 6 |
| Nov 6, 2026 | 6 |
| Nov 5, 2026 | 6 |
| Nov 4, 2026 | 6 |
| Nov 3, 2026 | 6 |
| Nov 2, 2026 | 6 |
| Nov 1, 2026 | 6 |
| Oct 31, 2026 | 6 |
| Oct 30, 2026 | 6 |
| Oct 29, 2026 | 6 |
| Oct 28, 2026 | 6 |
| Oct 27, 2026 | 6 |
| Oct 26, 2026 | 6 |
| Oct 25, 2026 | 6 |
| Oct 24, 2026 | 6 |
| Oct 23, 2026 | 6 |
| Oct 22, 2026 | 6 |
| Oct 21, 2026 | 6 |
| Oct 20, 2026 | 6 |
| Oct 19, 2026 | 6 |
| Oct 18, 2026 | 6 |
| Oct 17, 2026 | 5 |
| Oct 16, 2026 | 5 |
| Oct 15, 2026 | 5 |
| Oct 14, 2026 | 5 |
| Oct 13, 2026 | 6 |
| Oct 12, 2026 | 6 |
| Oct 11, 2026 | 6 |
| Oct 10, 2026 | 6 |
| Oct 9, 2026 | 6 |
| Oct 8, 2026 | 6 |
| Oct 7, 2026 | 6 |
| Oct 6, 2026 | 6 |
| Oct 5, 2026 | 6 |
| Oct 4, 2026 | 6 |
| Oct 3, 2026 | 6 |
Map
Where colocatel-inc'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-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | Not in PeeringDB | ||
| 1-NL FREE Amsterdam, Netherlands | 100G | PeeringDB | |
| ERA-IX Amsterdam Amsterdam, Netherlands | 100G | Both IPv6 not in PeeringDB | |
| Frys-IX Fryslân, Netherlands | 100G | Both IPv6 not in PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 100G | Both IPv6 not in PeeringDB | |
| INTERIX Amsterdam, Netherlands | 100G | Both IPv6 not in PeeringDB |
These exchanges have a switch in a facility where colocatel-inc lists itself in PeeringDB, but don't have colocatel-inc 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.
| AMS-IXAmsterdam, Netherlands | 921 | |
| NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 672 | |
| FogIXPAvers, Switzerland | 532 | |
| Speed-IXDronten, Netherlands | 289 | |
| Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine | 268 | |
| NetIXSofia, Bulgaria | 204 | |
| ixFabric - AmsterdamAmsterdam, Netherlands | 181 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| LSIXAmsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands | 105 | |
| HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France | 58 | |
| FogIXP AmsterdamAmsterdam, Netherlands | 57 | |
| PyramIXCairo, Egypt | 48 | |
| Giganet IXN AmsterdamAmsterdam, Netherlands | 47 | |
| Clue-IXAmsterdam, Netherlands | 36 | |
| Asteroid AmsterdamAmsterdam, Netherlands | 27 | |
| RegPEXAnkara, Türkiye | 19 | |
| NSIX AmsterdamAmsterdam, Netherlands | 13 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| TMW-iXFrankfurt am Main, Germany | 5 | |
| Noord-IXLeeuwarden, Netherlands | 4 |
Facilities (2)
The buildings colocatel-inc lists in PeeringDB, and how many of the exchanges in each it's on.
| NIKHEF AmsterdamAmsterdam | 6 of 28 | |
| SkyLink Data Center BVEygelshoven | No exchange |
Recent changes Search them
- Oct 20, 2026 [PDB] AS213438 colocatel-inc now in PeeringDB at GNM-IX
- Oct 18, 2026 [IXF] AS213438 colocatel-inc added to GNM-IX
- Oct 14, 2026 [PDB] AS213438 colocatel-inc left GNM-IX
- Oct 12, 2026 [IXF] AS213438 colocatel-inc dropped from GNM-IX's IX-F list (still in PeeringDB)