This document describes the peering policies for DigitalOcean (AS14061).
An Internet Exchange (IX) is a location where ISPs and network operators come together to peer directly or indirectly. Most often these peerings are settlement-free. Peering enables us to provide better experience for customers by interfacing with the networks directly rather than via transit paths.
DigitalOcean will peer with network operators at IXs where traffic levels meet a specified minimum. Our preference is to setup multiple peering sessions for redundancy wherever and whenever possible. DigitalOcean will also peer with route servers on all IXs where we are present.
Peering eligibility will be reviewed to determine if the traffic exchanged between both parties justifies the necessity to establish a direct BGP session at an IX. If it is determined that there is no traffic currently exchanged and or very low amounts of traffic is exchanged then we will recommend that the peering requester use the IX route servers instead. We do not require any peering contracts or formal agreements with our peering partners.
DigitalOcean will review its peering policy quarterly and reserves the right to modify this policy at any time. We may also filter any routes which we determine should not be advertised to DigitalOcean over the agreed upon peering session. We will by default filter any bogon prefixes (i.e. IP space allocated by RFCs 1918, 5735, and 6598).
Routes advertised by DigitalOcean (AS14061) are tagged with BGP Large communities which identify the location from where the prefix is originated. Please note the use of these communities may be modified without any prior notice.
Community | Country of Orgin |
---|---|
14061:2:036 | Australia |
14061:2:124 | Canada |
14061:2:276 | Germany |
14061:2:356 | India |
14061:2:528 | Netherlands |
14061:2:702 | Singapore |
14061:2:826 | United Kingdom |
14061:2:840 | United States |