Axera SpA has an Open peering policy.

We will happily connect with any network with which we have a common exchange presence.
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 deployed RPKI validation on all its routers and drops INVALID routes since April 2020.

Axera SpA is a MANRS partecipant.

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

• 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) 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

General Peering Information

Peering Locations

Everything Peering Related

Please see our PeeringDB Record.