Quick info:
-
We operate a hot potato routing policy.
-
RPKI invalids are filtered.
-
RPF is employed on all internet-facing interfaces.
General policy:
- Peer must NOT direct any static routes, defaults, targets that are not announced or
otherwise at any location towards Web3Tech.
- Peer must NOT modify or otherwise reset attributes such as next-hop, communities, et al.
- Peer must maintain an up to date PeeringDB entry as our configuration is built from
said DB.
- Peer must send all prefixes they wish to source traffic from. Web3Tech may, at its
discretion, actively filter ingress traffic according to received prefixes.
- Peer must maintain sessions at all common exchange points.
- Peer must consistently announce the same prefix set at all locations unless regional
announcements have been agreed with the peering policy team.
- Peer must operate a staffed NOC contactable via email without auto responders or ticket systems that could generate loops or excessive notifications.
Further:
-
Web3Tech offers peering on a best effort basis only;
-
Web3Tech will not establish sessions with peers who use so called remote peering, or are in a different locality to our router on a given exchange;
-
Web3Tech will not under any circumstances sign a peering agreement, contract or honour any SLA and;
-
Web3Tech reserves the right to unilaterally terminate any peering sessions for any, or no reason.