Peering Policy for Yuwan Networks (AS212259)

# 1. Peering Requirements (General)

• Partner must have a registered public Autonomous System (AS) number.
• Partner must publish valid contact information and up-to-date IXP presence data via PeeringDB.
• Partner must maintain valid IRR records (route/route6 and as-set) for announced prefixes.
• Partner should publish valid RPKI ROAs for announced prefixes.
• Accepted prefix lengths: IPv4 /9 to /24, IPv6 /17 to /48.
• Interconnection type is bilateral peering only (no transit or third-party traffic exchange).

# 2. Filtering

• Static and/or default routes are not accepted and will be discarded.
• Private IP space (RFC 1918) and bogon prefixes are filtered.
• Any route whose AS_PATH contains private ASNs, AS0, or AS_SET is discarded.
• Routes with RPKI state Invalid are rejected.
• Prefixes without valid IRR authorization may be filtered.

# 3. Public Peering Exchange Points

Our details are as follows:

• IPv4: 203.190.230.93
• IPv6: 2001:de8:5::3:6530:1
• ASN: AS36530
• Facility: Equinix Tokyo
• IPv4: 36.255.57.194
• IPv6: 2001:de8:7::3:6530:1
• ASN: AS36530
• Facility: Equinix Hong Kong
• IPv4 prefix limit: 1000
• IPv6 prefix limit: 5000
• Peering DB: as36530.peeringdb.com

# 4. Interconnection Facilities

Yuwan Networks has infrastructure in the following facilities and offers private interconnects there:

• Equinix HK1 (Hong Kong, Tsuen Wan)
• Equinix HK2 (Hong Kong, Kwai Chung)
• Equinix TY1 (Japan, Tokyo)
• Equinix TY8 (Japan, Tokyo)
• Note: AS212259 is used only in Japan (TY1/TY8). Hong Kong peering sessions use AS36530.

# 5. Contact Information

• Abuse Reports: abuse@lain.sh
• Peering Requests: peering@lain.sh
• Network/NOC Support: noc@lain.sh

---