Peering Policy

Axera SpA has a Selective peering policy.

We peer with Route Servers at every location. We will happily peer directly with any network with which we have a common exchange presence if both of these conditions are met:

Your network is not visible via the exchange Route Servers;
Your network is not reachable via an existing Axera SpA Customer or Peer.

If multiple exchanges, we prefer to peer at every location.

The peering is based on good will and effort, therefore neither party is liable to the other party for losses or damage from interruption of peering for any period of time.

If a more formal/written agreement is needed on your side, please contact us (see below) for an arrangement.

Axera SpA puts great effort to provide uncongested bandwidth at all exchange points. We costantly monitor the bandwidth used at every location and update the links within reasonable time when the traffic exceedes 80% of available bandwith.

Axera SpA supports MD5 and TTL Security (not mandatory) and rfc8326 community.

Axera SpA (AS34758) deployed RPKI validation on all its routers and drops INVALID routes since April 2020.

Axera SpA (AS34758) is a MANRS partecipant.

If you peer with Axera SpA, make sure the following expectations are met

Be Dual Stack! We require IPv4 and IPv6 for each new peering session!
Use BGPv4;
Only send us traffic destined to our network;
Don't point default route to us;
Don't announce prefixes longer than /24;
Announce consistent routes at every exchange;
Have an up-to-date peeringdb record.

Axera SpA applies the following to every peering connection

We filter RFC1918 addresses, both inbound and outbound;
We filter BOGON addresses, both inbound and outbound;
We apply BCP38 filtering;
We announce only networks with AS_PATH starting with our own AS (34758 or 13097) as registered in the Ripe-NCC database;
We accept only network with AS_PATH starting with peer's own AS;
We announce the same networks/routes at every exchange.
We implement strict RPKI validation and filtering

Peering Information

General Peering Information

AS34758
Public Peering	Selective
Private Peering	On request
MD5	Supported, not mandatory
IPv4 prefix limit	100
IPv6 prefix limit	20

AS13097
Public Peering	Selective
Private Peering	On request
MD5	Supported, not mandatory
IPv4 prefix limit	100
IPv6 prefix limit	20

Peering Locations

AS34758
Exchange	IPv4	IPv6
MIX-IT	217.29.66.172	2001:7f8:b:100:1d1:a5d3:4758:172
DE-CIX Frankfurt	80.81.195.8	2001:7f8:0::87c6:0:1
TOP-IX	194.116.96.159	2001:7f8:23:ffff::159
VSIX	95.140.128.26	2001:7f8:5f:ffff::26
NAMEX	193.201.28.148	2001:7f8:10::3:4758

AS13097
Exchange	IPv4	IPv6
MIX-IT	217.29.66.176	2001:7f8:b:100:1d1:a5d1:3097:1
MINAP Milan	185.1.114.71	2001:7f8:c5::a501:3097:1