ixreport

colocatel-inc

AS213438 · Colocatel Network.

ColocaTel Inc.

6Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
ContentType
OpenPeering policy
5Using the route servers
5To fix in PeeringDB
2Facilities in PeeringDB

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. Poland 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.

  1. Netherlands ERA-IX Amsterdam Amsterdam, Netherlands · PeeringDB 3789
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001: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.

  2. Netherlands Frys-IX Fryslân, Netherlands · PeeringDB 3512
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001: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.

  3. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2a03: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.

  4. Netherlands INTERIX Amsterdam, Netherlands · PeeringDB 3990
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001: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

0246Oct 3, 2026Nov 19, 20266
Show as a table
DateExchanges
Nov 19, 20266
Nov 18, 20266
Nov 17, 20266
Nov 16, 20266
Nov 15, 20266
Nov 14, 20266
Nov 13, 20266
Nov 12, 20266
Nov 11, 20266
Nov 10, 20266
Nov 9, 20266
Nov 8, 20266
Nov 7, 20266
Nov 6, 20266
Nov 5, 20266
Nov 4, 20266
Nov 3, 20266
Nov 2, 20266
Nov 1, 20266
Oct 31, 20266
Oct 30, 20266
Oct 29, 20266
Oct 28, 20266
Oct 27, 20266
Oct 26, 20266
Oct 25, 20266
Oct 24, 20266
Oct 23, 20266
Oct 22, 20266
Oct 21, 20266
Oct 20, 20266
Oct 19, 20266
Oct 18, 20266
Oct 17, 20265
Oct 16, 20265
Oct 15, 20265
Oct 14, 20265
Oct 13, 20266
Oct 12, 20266
Oct 11, 20266
Oct 10, 20266
Oct 9, 20266
Oct 8, 20266
Oct 7, 20266
Oct 6, 20266
Oct 5, 20266
Oct 4, 20266
Oct 3, 20266

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.

Exchanges

Total port capacity 500G, at the 5 of 6 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland Not in PeeringDB
Netherlands 1-NL FREE Amsterdam, Netherlands 185.0.2.25 100G Yes PeeringDB
Netherlands ERA-IX Amsterdam Amsterdam, Netherlands 185.1.240.13 100G Yes Both IPv6 not in PeeringDB
Netherlands Frys-IX Fryslân, Netherlands 185.1.161.45 100G Yes Both IPv6 not in PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.237.102 100G Yes Both IPv6 not in PeeringDB
Netherlands INTERIX Amsterdam, Netherlands 185.1.184.142 100G 56 routes Both IPv6 not in PeeringDB

Exchanges in its buildings that it isn't on (22)

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.

Netherlands AMS-IXAmsterdam, Netherlands 921 NIKHEF Amsterdam
Netherlands NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 672 NIKHEF Amsterdam
Switzerland FogIXPAvers, Switzerland 532 NIKHEF Amsterdam
Netherlands Speed-IXDronten, Netherlands 289 NIKHEF Amsterdam
Ukraine Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine 268 NIKHEF Amsterdam
Bulgaria NetIXSofia, Bulgaria 204 NIKHEF Amsterdam
Netherlands ixFabric - AmsterdamAmsterdam, Netherlands 181 NIKHEF Amsterdam
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 NIKHEF Amsterdam
Netherlands Global-IXAmsterdam, Netherlands 138 NIKHEF Amsterdam
Netherlands LSIXAmsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands 105 NIKHEF Amsterdam
France HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France 58 NIKHEF Amsterdam
Netherlands FogIXP AmsterdamAmsterdam, Netherlands 57 NIKHEF Amsterdam
Egypt PyramIXCairo, Egypt 48 NIKHEF Amsterdam
Netherlands Giganet IXN AmsterdamAmsterdam, Netherlands 47 NIKHEF Amsterdam
Netherlands Clue-IXAmsterdam, Netherlands 36 NIKHEF Amsterdam
Netherlands Asteroid AmsterdamAmsterdam, Netherlands 27 NIKHEF Amsterdam
Türkiye RegPEXAnkara, Türkiye 19 NIKHEF Amsterdam
Netherlands NSIX AmsterdamAmsterdam, Netherlands 13 NIKHEF Amsterdam
Türkiye EURASIA-IX.NETIstanbul, Türkiye 6 NIKHEF Amsterdam
United States Global Peer ExchangeWashington, United States 6 NIKHEF Amsterdam
Germany TMW-iXFrankfurt am Main, Germany 5 NIKHEF Amsterdam
Netherlands Noord-IXLeeuwarden, Netherlands 4 NIKHEF Amsterdam
Facilities (2)

The buildings colocatel-inc lists in PeeringDB, and how many of the exchanges in each it's on.

Netherlands NIKHEF AmsterdamAmsterdam 6 of 28
Netherlands 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)