Clearfly Communications (AS27400) Peering Policy
Clearfly Communications (Clearfly) has an open peering policy and evaluates all potential peers on a case-by-case basis.
- Under no circumstances will Clearfly peer with an existing transit customer.
- Peers are expected to filter their sessions to reject unauthorized BGP announcements.
- Peers are expected to aggregate routes as much as possible. Clearfly will not accept any announcement longer than /24.
- Peers must not utilize any form of default route or gateway of last resort that is directed at Clearfly.
- If possible, Clearfly prefers to implement MD5 authentication on BGP peering sessions.
- If possible, Clearfly typically prefers to utilize routes learned via a route server in lieu of establishing direct peering sessions.
- Clearfly reserves the right to suspend peering for an indefinite period of time should any abuse originate from a peer. This includes, but is not limited to:
- Exceeding configured maximum route filters
- Any form of DoS attack
- Unsolicited bulk email (spam)
- Default route directed at Clearfly Communications
- Clearfly reserves the right to suspend peering due to service-affecting instability of peer devices or routes
Peering Email: firstname.lastname@example.org
PeeringDB Record: https://www.peeringdb.com/asn/27400