AS211066 | Japan Sakura Network
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
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.
We operate the network using a different AS number for each region
- 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
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
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
If there are multiple peering points, MED values will be given
to our announcement routes as follows. Please note that you do
not necessarily assess the MED values that we provide.
- First priority Internet Exchange: MED100
- Second priority Internet Exchange: MED200
- Third priority Internet Exchange: MED300
- Fourth priority Internet Exchange: MED400
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 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.
There is no minimum traffic requirement at all peering
points in Japan.
- There is no minimum traffic requirement at all peering
- Please contact us for traffic volume requirements.
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.
- We are connected to all the Internet Exchange route servers
We do not connect to the Internet Exchange route servers in
- We do not connect to the Internet Exchange route servers in
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.