Peering Policy

SAKURA internet, Inc. established the following peering policy and is promoting peering based on the policy in order to efficiently distribute traffic and realize a comfortable and high-quality connection.
Please note that this policy is a basic idea for peering.It does not promise peering, and we may change the conditions without prior notice depending on traffic situation, etc.

AS Number

We operate the network using a different AS number for each region as follows:

  • AS9370 (Tokyo)
  • AS9371 (Osaka)
  • AS7684 (Hokkaido/Ishikari)


The following prerequisites must be met for peering.

  • Route object and as-set object are registered on IRR.
  • Contact information is disclosed by, for example, registering on the Peering DB.
  • There is a contact that can respond to technical problems of the network and security, and appropriate engineers can handle them.
  • We recommend that you create an ROA and verify it with RPKI.

Peering through Internet Exchanges

Peering points

  • For the Internet Exchange Points that allow peering, please check the Peering DB.
  • If you have multiple peering points (same region or multiple regions), we recommend that you peer at two or more locations.
  • If there is a peering point both in Tokyo and Osaka, we recommend that you peer in both sites.
  • The peering policy for all Internet exchanges in Japan is open.
  • The peering policy for all Internet exchanges in North America is selective.


Route announced by you
  • Any announcement route smaller than /24 for IPv4 and /48 for IPv6 will not be accepted.
  • The MED(multi exit discriminators) attribute of the route you advertise will not be accepted.
  • Unless otherwise agreed, we recommend that you announce the same route at all peering points.
Route announced by us
  • MED values will be given to our announcement routes. Please note that you do not necessarily assess the MED values that we provide.
  • We will announce the AS route included in the "as-set object AS-SAKURA" that is registered in IRR at all the peering points.
  • The minimum route that we announce will be /24 for IPv4 and /48 for IPv6.
  • For peering through Internet Exchanges, we set the BGP timer for keepalive at 5 seconds and the holdtime at 15 seconds. (North America : keepalive at 10 seconds and the holdtime at 30 seconds) If you need to set greater value for BGP timer, please contact us.
  • Please do not set a StaticRoute or DefaultRoute against the peer and send traffic.
  • We set the Max Prefix for peering through Internet Exchanges. Please let us know the number of routes to be announced in advance or specify it on the Peering DB.
  • In principle, we do not offer MD5 authentication; however, it is possible to set it upon request.
  • No transit or third party routes are to be announced; all routes exchanged must be peer's and peer's customers' routes.
  • If a peer down status is observed for more than 180 days, we may depeer the peer without contacting you.
Traffic requirement
  • Japan
    • There is no minimum traffic requirement at all peering points in Japan.
  • North America
    • Please contact us for traffic volume requirements.
Multilateral peering
  • Japan
    • We are connected to all the Internet Exchange route servers in Japan that are possible to peer. We can exchange the traffic by announcing the route on the route server and receive our route.
  • North America
    • We do not connect to the Internet Exchange route servers in North America.

Private Peering

We will consider private peering if the maximum traffic amount regularly exceeds 1Gbps. In principle, we do not offer private peering in Hokkaido (AS7684) and North America. For details, please contact us from the following link.


If you wish to use the peering or have any other questions, please contact us from the following link.