ixreport

Avatel Telecom

AS200845 · Avatel Telecom

Avatel Telecom S.A.

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

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

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on Avatel Telecom'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 CATNIX Barcelona, Spain · PeeringDB 62
    ProblemPeeringDB hasThe export has
    Port speed differs10G5G
    • In the entry with IPv4 193.242.98.172: set Speed to 5000 (5G) (now 10000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 80.81.192.199: set Speed to 100000 (100G) (now 10000).

Exchanges over time

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

Map

Where Avatel Telecom'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 430G across 7 exchanges.

Spain 1-ES FREE Madrid, Spain 91.213.73.72 2001:7f8:175::72 100G Yes PeeringDB
Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 185.0.43.87 2001:7f8:115:1::1:87 100G Yes Both
Spain CATNIX Barcelona, Spain 193.242.98.172 2001:7f8:2a:0:3:1:20:845 10G Yes Both Speed differs
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.192.199 2001:7f8::3:108d:0:1 10G 561 routes Both Speed differs
Spain DE-CIX Madrid Madrid, Spain 185.1.192.76 2001:7f8:a0:0:3:108d:0:1 100G 564 routes Both
Spain ESpanix Madrid Lower LAN Madrid, Spain 193.149.1.170 2001:7f8:f::170 100G Yes PeeringDB
Spain IXPlay Global Peers Madrid, Spain 185.1.90.92 2001:7f8:b2:0:724:20:845:0 10G Yes PeeringDB

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

These exchanges have a switch in a facility where Avatel Telecom lists itself in PeeringDB, but don't have Avatel Telecom 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 Avatel Telecom lists in PeeringDB, and how many of the exchanges in each it's on.

Spain Digital Realty Madrid MAD1-2Madrid 5 of 8
Spain Templus DC Barcelona BCN01L'Hospitalet de Llobregat 1 of 5
Spain NIXVAL DatacenterPaterna 0 of 2
Spain Digital Realty Madrid MAD3Madrid 0 of 1
Spain Templus DC Málaga MAL01Málaga 1 of 1

Recent changes Search them

  • Nov 6, 2026 [PDB] AS200845 Avatel Telecom no longer in PeeringDB at CATNIX (still on its IX-F list)