Redcentric is listed in PeeringDB, which is the industry standard database for peering information for
network service operators. Redcentric currently maintains 4 ASN’s in the Peering DB. The main ASN is 13009.
We are currently in the process of migrating ASN’s 5552, 8419 and 30914 into the network.
We are actively encouraging peering with AS13009. ASN’s 5552,8419 and 30914 will shortly be ceased..
Redcentric has an open peering policy, subject to certain technical, commercial and legal requirements. Technical requirements for peering are below:
In general Redcentric will ONLY announce prefixes of those and it’s directly connected peers. We expect peering partners to run a similar policy. Redcentric will NOT announce peering partners routes to other providers thereby acting as transit, unless they are a customer of Redcentric. Again peering partners will be expected to run a similar policy. This is not applicable to Transit peeering. Longer prefixes than those advertised via the route objects in the organisations route registry entries are not permitted unless with prior agreement.
Redcentric carries customer traffic over it’s network as close to it’s customers as possible. It is advisable that peering partners adopt a similar policy. Redcentric therefore suggest that where multiple peering points are present, the peering relationship take advantage of these.
The current version of this document suggest that peering partners set a max-prefix limit for IPv4 of 100 routes and a max-prefix limit of 25 for IPv6 routes.
Redcentric advises that in the interests of Internet security, MD5 passwords and TTL hop count limitations are used. Although this is not enforced as a policy it is strongly suggested peering partners consider these additional requirements.
If you wish to setup peering with Redcentric please send and email to email@example.com stating the peering points where you would like to peer and a link to your PeeringDB object.