AS47447

AS47447 is the network managed by 23M.com. General information for peering requests:

• External parties requesting peering must have an up-to-date and fully completed entry with PeeringDB.
• All peering requests should be made via email to peering@23m.com. 23M reviews peering requests on a case-by-case basis, taking into account the rules of the peering policy below.
• 23M aims to answer peering requests in a timely manner.

Peering Policy

• 23M has a selective peering policy which is generally open.
• Peers must have public and visible ASN which is registered on one of the five internet registries.
• In case of multiple existing connections at an IX, peers must establish BGP sessions with all neighbors and enable multipath routing.
• 23M does not have a minimum bandwidth requirement for establishing peering.
• For filtering puposes both parties are expected to have their routes registered in a public Internet Routing Registry (IRR) database. This information shall be updated regularly.
• Either party may accept or reject peering requests as network management needs require.
• Peers must not abuse the peering relationship by doing the following: point default route, reset next hop, sell or give the next hop to third parties, etc.
• Both parties must maintain an up-to-date PeeringDB entry, including a 24/7 NOC contact.
• Both parties will only exchange IPv4/IPv6 Unicast routes.
• 23M does not require the use of an MD5 key. Upon request we can do it.
• 23M requires the other party to register their routes in the RPKI repository using Route Object Authorization (ROA) objects.
• Peers are encouraged to implement Mutually Agreed Norms for Routing Security (MANRS).
• For PNIs we require a minimum traffic of 1 Gbit/s on a regular basis.

Meeting the criteria specified here does not guarantee that 23M will establish a peering relationship with the applicant.

Please see our PeeringDB entry for further details.