Peering Policy

We want to do peer in open policy. However, it is difficult for nonprofit organizations to pay for peering costs. Therefore, we make the following peering conditions.

As of December 2017, we are not connected to the Internet Exchange, so we will only connect with private peers.

1.Required condition of peering

It is necessary to satisfy all of the following conditions.

  • Operation information is described in the Peering DB.
    • If you are not using Peering DB, information has been disclosed in other ways.
  • Correct object information is registered in IRR
  • Be able to communicate with network engineers about operational problems.

2.Technical conditions

2-1. Circuit

We are peering at some data centers and tunnel.

  • Tunnel connection (use IPv4 or IPv6 Internet)
  • Tunnel connection using NTT FLET ‘S Hikari (NGN IPv6 Option)
    • The tunneling protocol supports IP over IP, GRE, or EtherIP.
  • Cross connect at the following data center
Region Datacenter Remarks
Tokyo Sakura Internet Nishi Shinjuku Data Center  
Osaka NTT Telepark Dojima 2 Building Connectable from 3 buildings and 4 buildings

When you pay the cost of the circuits, it is not limited to the above.

2-2. Traffic condition

The traffic level condition is not defined.

2-3. Routing

  • Advertise
    • Add the MED attribute to the advertised route.
      • It is not essential to use the MED attribute.
    • Advertise routes included in as-set object AS-HOMENOC.
  • Receive
    • Routes longer than /24(IPv4),/48(IPv6) are not accepted.
    • Use MED attribute you attached.
    • Route filtering with MaxPrefix and AS-Path.


We may disconnect the peer if the above conditions apply.

  • There is a bad influence on stable operation of the network.
  • When the peering condition can not be satisfied.

4.Peering Contact

You can refer PeeringDB to get some information. Please feel free to contact us if you have any queries about peering.

Contact: peer[at]