Peering Policy

We will happy to 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.

Fiber Telecom puts great effort to provide uncongested bandwidth at all exchange points. We constantly monitor the bandwidth used at every location and update the links within reasonable time when the traffic exceeds 70% of available bandwidth.

Fiber Telecom AS41327 has a Selective Peering Policy

We peer direct where it makes sense:

  • if we see your networks behind our transit
  • if there is some traffic to exchange or particular request

We do not care so much about ratios and/or traffic volume that we need to carry to reach the peer.

We usually don't peer with a customer of an existing customers and/or peers.
This has political reasons as it may put existing peering relationships at risk.

If you peer with Fiber Telecom, make sure the following expectations are met

  • Use BGPv4 and BGPv6
  • Only send us traffic destined to our network
  • Don't point default route to us
  • Don't announce prefixes longer than /24 on IPv4 and /48 on IPv6
  • Announce consistent routes at every exchange
  • Have an up-to-date PeeringDB record

Fiber Telecom 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 AS41327 as registered in the Ripe-NCC database
  • We accept only network with AS_PATH starting with peer's own AS
  • We are matching RPKI validation state and reject invalids 'invalid = reject' (since March 2019)

Peering Information

General Peering Information

Public PeeringSelective
Private PeeringOn request
MD5 or AOSupported, not mandatory
IPv4 max prefix limit2000
IPv6 max prefix limit400

Contact Information

Everything Peering Related