Peering Info
| Peering Contacts | Phone | |
|---|---|---|
| Peering | peering@renesys.com | +1 (603) 643-9300 x101 |
| NOC | noc@renesys.com | +1 (603) 643-9300 |
About Renesys peering
Renesys peers for the purposes of route-collection only. We never advertise any routes. We do not have any traffic to send to your network. We operate BGP route-collectors at several locations around the Internet as part of our Internet intelligence services. We have peers who operate networks on every continent (aside from Antarctica—but we're still looking), and sometimes we're willing to take on new peers.
Requirements
Renesys engages in two types of peering, full routes and peer routes:
Full routes
Renesys seeks to peer with ISPs and NSPs who have a “full Internet routing table” for IPv4 that they are willing to send us. In mid 2007, that is about 220,000 routes (although somewhat less or more is obviously fine). We require that our peers operate a registered ASN from the appropriate RIR. Peers must be able to maintain a stable BGP session to us. We prefer peers who are willing to peer with us at multiple locations, from multiple locations on their own network, but single-feed peers may still be accepted. Although we're happy to have default-free and other large-networks peers, we continue to be interested in peering sessions from network operators closer to the edge of the Internet, particularly to edges of the Internet where we currently have little visibility. Peers should not send us null routes, bogons or other non-routable prefixes that they may use to control traffic on their own networks.Peer routes
Renesys has recently started seeking NSPs willing to send us, on a separate session, their “peer routes” or the set of downstream or customer routes that they would normally send to a peer for settlement free interconnection. Those interested in providing peer routes should send an email or add a comment in the form below.
Technical overview
Renesys peers from a private AS: ASN64597. We do this on purpose because we never advertise any routes and if we ever were to, we want them to be easy to find and filter. We operate route collectors that are either administratively prohibited from issuing BGP updates or, in the case of our own route-collection software (bagpipe), do not even have the capability of issuing them. We do most peering multi-hop, since that's the easiest way to pick up the largest, most geographically diverse set of peers.
Benefits
Peers who provide us with a BGP session that meets the requirements stated above are eligible to receive one subscription to our route analysis service. They also get real-time alarms service at a discounted rate. Learn more about Routing Intelligence® here.
Multihop peering
This section covers the steps to set up an external BGP session with our collection router. We never advertise any routes, but a little belt-and-suspenders protection never hurts. Configure your access lists to send us everything and accept nothing from us.
Example configuration (multihop): When you submit a request for peering, you will receive one or more IP addresses from us. Use these real IP address of our BGP router that you received from us in place of the imaginary 10.10.10.10 shown below.
! The basics of silent peering with silent-peering.renesys.com:
neighbor 10.10.10.10 remote-as 64597
neighbor 10.10.10.10 ebgp-multihop
neighbor 10.10.10.10 timers 60 600
! Use your own judgement about access-lists:
neighbor 10.10.10.10 distribute-list 88 in
neighbor 10.10.10.10 distribute-list 99 out
access-list 88 deny any
access-list 99 permit any
Exchange point peering
AMS-IX
Renesys offers Exchange-point peering at AMS-IX in Amsterdam. To peer with us there, use ASN: 64597, IP: 195.69.144.230.
ANY2
Renesys offers Exchange-point peering at the Any2 Exchange in Los Angeles. To peer with us there, use ASN: 64597, IP: 206.223.143.34.
LINX
Renesys offers Exchange-point peering at LINX in London. To peer with us there, use ASN: 64597, IP: 195.66.225.224. We are able to peer on both LANs but will normally only peer on the listed LAN unless requested. Contact us for more information.
NAP of the Americas
Renesys offers Exchange-point peering at NAP of the Americas in Miami. To peer with us there, use ASN: 64597, IP: 198.32.124.108.
Equinix
Renesys offers Exchange-point peering at Equinix in Tokyo. To peer with us there, use ASN: 64597, IP: 203.190.230.21.
We are evaluating additional IXes for peering. Our requirements are simple: ports on the peering LAN should either be free at low speeds or ridiculously cheap, space and bandwidth should be cheap and plentiful and there must be a well-run peering switch with dozens of networks interested in providing routes to us. We require little space (2-8RU depending upon the installation) and are happy to discuss sub-tenancy with organizations that have established installations at interesting locations. Contact us if you have a proposal for anything like this.