Peering Portal

About us

AS Number information:
- AS14447 (Main)
- AS-SET: ARIN::AS-INFINITRON

- AS215364 (Legacy)
- AS-SET: AS215364:AS-KKC-NETWORK

- Peering Policy: Open
Contact information:
- 24/7 NOC: [email protected]
- Abuse Report: [email protected]
- Telegram / Discord: @shui_chuan

User already exists. Please login here or use a different email to register.

Your account has been successfully verified.
You can now login.

Verification failed. The verification link is invalid or has already been used.
Please register again or contact support for assistance.

Peering Policy

🌐 Peering Policy

We are open to peering with any network, anywhere in the world.

📍 You can find a list of the physical Internet Exchange Points (IXPs) where we are present on our PeeringDB profile.

🤝 Peering Requirements

• We do not announce bogons or accept bogon prefixes. All routing is filtered to exclude reserved and unallocated IP ranges.
• Peers must maintain up-to-date contact information in PeeringDB.
• Peers must not engage in route leaks or propagate incorrect routing information.
• We expect peers to maintain reliable connectivity and promptly address technical issues.
• We reserve the right to terminate peering at any time for operational reasons.
• We only accept routes that have valid RPKI (Resource Public Key Infrastructure) records. All advertised routes must be filtered to ensure RPKI validation
• We require a minimum of /24 prefixes for IPv4 and /48 prefixes for IPv6 to be advertised.

Routing Policy

🌐 Routing Policy

We accept and advertise routes based on the following criteria:

• We accept routes from our peers that are properly filtered and do not include bogons or reserved IP ranges.
• We advertise our own prefixes and those of our customers, ensuring that all routes are properly filtered and validated.
• We implement RPKI (Resource Public Key Infrastructure) to validate the authenticity of the routes we accept and advertise.
• We implement ROA (Route Origin Authorization) to ensure that only authorized ASes can announce their prefixes.
• We do not accept or advertise routes that are known to be involved in malicious activities, such as DDoS attacks or spam.
• We reserve the right to modify our routing policies as needed to maintain network stability and security.

For each received route, the following rejection tests must be performed:

• Reject if the prefix is a bogon or reserved IP range.
• Reject if the prefix does not have a valid RPKI record.
• Reject if the prefix is shorter than /24 for IPv4 or /48 for IPv6.
• Reject default routes 0.0.0.0/0 and ::/0.
• Reject if the prefix is not in the peer's ROA (Route Origin Authorization).
• Reject AS paths that use BGP AS_SET notation (i.e. [1] or [1 2], etc).
• Reject prefix lengths less than minimum and greater than maximum. For IPv4 this is 8 and 24. For IPv6 this is 16 and 48. Reject bogons (RFC1918, documentation prefix, etc).
• Reject AS paths that use unallocated ASNs between 64496 to 131071 and 1000000 to 4294967295.
• Reject if the prefix is known to be involved in malicious activities.

Your inquires sent successfully.

Contact

• Twitter

Elements

i = 0;

while (!deck.isInOrder()) {
    print 'Iteration ' + i;
    deck.shuffle();
    i++;
}

print 'It took ' + i + ' iterations to sort the deck.';