jpnap

Service

Optional Services

PI/CUG Services
Implementation of Private Peering on IX

  • JPNAP Tokyo
  • JPNAP Osaka
  • JPNAP Fukuoka
  • JPNAP Sendai
  • JPNAP Sapporo

This service enables secure and private traffic exchange on JPNAP's public network through VLAN, which allows direct connections between two parties through PI (Private Interconnect) and connections among three or more parties through CUG (Closed Users Group).

PI/CUG Services

RouteFEED Services
A route server that facilitates high-efficiency and high-value added peering.

  • JPNAP Tokyo
  • JPNAP Osaka
  • JPNAP Fukuoka
  • JPNAP Sendai
  • JPNAP Sapporo

This service enables connection to JPNAP's route servers. By peering with the route server, you can automatically exchange routes with other RouteFEED service subscribers without individual peering negotiations. It also features secured route filtering based on IRR and RPKI. It is equipped with a Looking Glass function for clients to assess the route server's status and a mechanism to discard attack traffic using RTBH (Remote Triggered Black Hole), among other unique IX functionalities.

RTBH Service
Preventing attack traffic like (D)DoS

  • JPNAP Tokyo
  • JPNAP Osaka
  • JPNAP Fukuoka
  • JPNAP Sendai
  • JPNAP Sapporo

RTBH filtering can drop unnecessary traffic. Frames directed to the blackhole host are discarded on the JPNAP switches before reaching customers' network. This helps you to prevent attack traffic such as DDoS attack. It’s also available on RouteFEED service. The route servers overwrite the NEXT_HOP of the routes with blackhole community to the blackhole host and advertise to other peers. Traffic is redirected and dropped when those routes are received by other peers.

Content Cache Connection Service type A
Receiving Akamai Cache within IX

  • JPNAP Tokyo
  • JPNAP Osaka
  • JPNAP Fukuoka

This service enables the reception of delivery traffic from Akamai Technologies' cache servers within the JPNAP network. It is expected to reduce transit costs and improve responses and stability.
※ Use of RouteFEED service is required.

FIC Connection Services
Implementing Secure Connections to the Cloud and Other Resources

  • JPNAP Tokyo

This service enables connection to the Flexible InterConnect (FIC) service of NTT Communications Corporation's 'Smart Data Platform' via JPNAP services. You can connect to FIC without preparing a dedicated network.
※ A separate contract with NTT Communications Corporation for FIC is required.​

We provide two types of connections: "Cloud Connection Type" and "XaaS Connection Type" tailored to customer usage.

(1) Cloud Connection Type

This is an option for ISPs and data center operators that provide network services to businesses. It offers a broad and stable multi-cloud connection environment for company users to utilize your ISP or data center. This permits the expansion and enhancement of network services.

(2) XaaS Connection Type

This is an option for cloud service providers offering services such as SaaS, PaaS, IaaS (XaaS) to businesses. It enables the provision of a broad and stable closed network connection environment to user companies using NTT Com's network services, facilitating the convenience of connection methods and expanding their capabilities.

About Flexible InterConnect