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, or targets not announced or otherwise at any location towards Web3 Technologies Inc.
• Peer must NOT modify or reset attributes such as next-hop, communities, etc.
• 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. Web3 Technologies Inc 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 autoresponders or ticket systems that generate loops or excessive notifications.

Further:

• Web3 Technologies Inc offers peering on a best-effort basis only.
• Web3 Technologies Inc will not establish sessions with peers who use remote peering or are in a different locality to our router on a given exchange.
• Web3 Technologies Inc will not sign any peering agreement, contract, or honor any SLA.
• Web3 Technologies Inc reserves the right to unilaterally terminate any peering session for any or no reason.