Yixi Meta AS202338 Peering Policy

Yixi Meta AS202338 Peering and Acceptable Use Policy

This version is published on and will become valid immediately. (PDF: Peering Policy AS202338.pdf). Historical versions can be found here.


  • This Peering Policy applies to networks willing to peer with Yixi Meta Network (AS202338);
  • The network should have public ASN and publicly routable address space;
  • The network maintains up-to-date routing registry and PeeringDB entry;
  • The network operates a 24×7 NOC;
  • The network should maintain peering with Yixi Meta;
  • The peering is settlement free for both parties;
  • Peering on multiple geographical locations are not required but are preferred.


This policy applies to peering session with Yixi Meta (AS202338). Meeting the peering requirements described in this documents does not guarantee an establishment of a peering relationship. Yixi Meta reserves the right not to enter into a peering agreement after evaluating various business factors.

Peering Requirements

We are willing to peer (IPv4 and IPv6) with you at one or more mutually presented exchange points (IXP) or with private interconnect.

Through BGP4 we will announce to you routes which we carry and will listen to routes that you carry. By default, RPKI validation is implanted and any invalid route are denied. In addition, bogon filters (table 1) will be applied to the received routes. The bogon filters may also include unassigned addresses / ASNs. We therefore suggest you not to send any above mentioned traffic to us since they will not be accepted. However, upon special agreement, we may void/alter our filter that applies to the received routes from you.

Table 1: Default Bogon Filter for Received Routes
Internet resources Address space Action
IPv4 Address defined in RFC 1122, RFC 1918, RFC 2544, RFC 3927, RFC 5737, RFC 5771, RFC 6598 and RFC 7526 DENY
IPv6 Address defined in RFC 3701, RFC 3849, RFC 3879, RFC 4193, RFC 4291, RFC 4843, RFC 5180, RFC 6666 and RFC 7526 DENY
ASN ASN defined in RFC 7607, RFC 4893, RFC 5398, RFC 6996, RFC 7300, RFC 5398, RFC 6996, RFC 7300;
AS65552-AS131071 (Reserved by IANA)

We expect the following from you as our peering partner:

  • Only send us traffic that is destined for the prefixes we announce to you. Do not point default at us or use static routes to send us traffic that does not match the routes we announce to you;
  • Yixi Meta will announce consistent routes with possible variation (due to localisation) at each exchange point;
  • Yixi Meta expects you to peer at all exchange fabrics we have in common if we peer with you via public exchanges or all facilities we have in common if we peer via private interconnect with you;
  • You accept our Peering Acceptable Use Policy.

Requesting Peering to AS202338

Any network with public ASN and publicly routable address space is welcome to discuss peering with us via email at noc@yiximeta.com. Please include your ASN and peering point locations.

Changes to the Peering Policy and Existing Peering

Existing peers of AS202338 will have their peering status reviewed periodically to ensure joint capacity planning and to ensure that all criteria continue to be met.

Yixi Meta reserves the right to terminate peering for convenience, upon a 1 month prior notice or with peers who do not meet the criteria described above.

Periodic review of this policy will be conducted to ensure that the criteria and eligibility requirements are consistent with Yixi Meta business needs. Yixi Meta may modify this peering policy at any time.

Applicable Law

Interpretation of this Peering Policy and Resolution of any disputes will be done according Dutch Law and the courts of Gelderland located in Nijmegen (Rechtbank Gelderland, locatie Nijmegen) in the Netherlands shall have exclusive jurisdiction.