ixreport

Altecom

AS16030 · ALTECOM

Alta Tecnologia en Comunicacions, S.L.

3Exchanges
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
3Using the route servers
3To fix in PeeringDB
5Facilities in PeeringDB

Tools: Where can I peer with Altecom? · Where should Altecom peer next? · Compare Altecom with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in Altecom's PeeringDB record, from what its exchanges publish: 2 to correct, 1 to check. As of 2026-11-19 12:40 UTC.

Make the changes on Altecom'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 (2)

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. Spain DE-CIX Barcelona Barcelona, Spain · PeeringDB 3446
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 185.1.119.17: set Speed to 1000 (1G) (now 10000).
  2. Spain DE-CIX Madrid Madrid, Spain · PeeringDB 1277
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 185.1.192.7: set Speed to 1000 (1G) (now 10000).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Altecom has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Spain CATNIX Barcelona, Spain · PeeringDB 62Not on its IX-F export
    IPv4193.242.98.4
    IPv62001:7f8:2a:0:1:1:1:6030
    Speed10000 Mbps (10G)

Exchanges over time

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

Map

Where Altecom'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 30G across 3 exchanges.

Spain CATNIX Barcelona, Spain 193.242.98.4 2001:7f8:2a:0:1:1:1:6030 10G Yes PeeringDB only
Spain DE-CIX Barcelona Barcelona, Spain 185.1.119.17 2001:7f8:10a::3e9e:0:1 10G Down Both Speed differs
Spain DE-CIX Madrid Madrid, Spain 185.1.192.7 2001:7f8:a0::79f0:0:1 10G Down Both Speed differs

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

These exchanges have a switch in a facility where Altecom lists itself in PeeringDB, but don't have Altecom 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.

Facilities (5)

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

Spain Digital Realty Madrid MAD1-2Madrid 1 of 8
Spain Templus DC Barcelona BCN01L'Hospitalet de Llobregat 2 of 5
Spain Equinix MD2 - MadridAlcobendas 1 of 4
Spain Equinix BA1 - BarcelonaBarcelona 2 of 3
Spain CSUC Campus NordBarcelona 1 of 1