AS8681 – JT : Peering Policy

Home : Peering Policy : IPv6 : BGP Communities via IPv4


JT (AS8681) is the main telecommunications operator on Jersey and a major operator across the Channel Islands.

As a network operator, Jersey Telecom deploys and maintains a European IP network built upon Ten Gigabit Ethernet (10Gbps), STM-64 (10Gbps) and Gigabit Ethernet (1Gbps) links supporting the communications requirements of 160,000 Channel Islands residents and thus generates a large amount of Internet traffic. Jersey Telecom maintains its own transchannel submarine cables.

The corporate JT web site is accessible at:

Minimum requirements

In order to establish either a Public Peering or a Private Interconnect with AS8681, the candidate network should meet the following criteria:

  • The candidate must not be a current or past customer of JT’s Internet products.
  • The candidate must not be a customer of a current customer of JT’s Internet products.
  • The candidate shall be a public or privately held company officially registered in its home country’s trade and/or industry authority.
  • The candidate’s network should justify a certain amount of traffic with AS8681 either originated from its own network or from the networks taking transit from it. The minimum acceptable amount of traffic remains at the discretion of Jersey Telecom’s network authority and will be evaluated on a case-by-case basis.
  • The candidate’s Network Operation Centre (NOC) shall be reachable either by e-mail or phone 24/7/365. Thus the candidate has to provide any operational contact to Jersey Telecom and advertise JT of any change in the contacts’ details.

Public Peering Interconnection (PPI)

AS8681 is available at the following Internet eXchange points:

JT’s peering policy does not require the candidate to establish more than one PPI, but any PPI generating more than 200Mbps of traffic should be protected by means of establishing a second PPI at any other exchange point where both JT and the candidate’s network are also present. However 200Mbps is not a minimal requirement to establish more than one PPI, thus networks generating less than 200Mbps of traffic with JT may set up other PPI.

Private Network Interconnection (PNI)

JT also accepts to establish PNI with other networks when both JT’s network and the candidate’s network are co-located at the same housing facility or when both networks agree to share circuit’s costs if they are not in the same facility, but in the same city. Physical media available to privately interconnect with Jersey Telecom are:

  • 100BaseTX Fast Ethernet.
  • 1000BaseTX Gigabit Ethernet.
  • 1000BaseSX Gigabit Ethernet, multi mode fibre.
  • 1000BaseLX/LH Gigabit Ethernet, single mode fibre.
  • 1000BaseZX Gigabit Ethernet, single mode fibre.
  • 10GBase-SR Ten gigabit Ethernet, multi mode fiber.
  • 10GBase-LX4 Ten Gigabit Ethernet, multi mode fiber.
  • 10GBase-LR Ten Gigabit Ethernet, single mode fibre.
  • 10GBase-ER Ten Gigabit Ethernet, single mode fibre.

The housing facility where to establish the PNI shall be discussed directly with the candidate. JT is present in the following facilities:

  • Telehouse North, London, UK
  • Telehouse East, London, UK
  • Telecity Powergate, London, UK
  • Telecity Harbour Exchange, London, UK
  • France Telecom, Aubervilliers, France

Technical notes

Upon establishing either a PPI or PNI, the candidate SHALL:

  • Advertise fully aggregated prefixes.
  • Advertise at least prefixes for registered route (either at RIPE or IRR) with candidate’s network AS number as origin.
  • Advertise its transit customers either for the region(s) where is (are) the PPI(s) or PNI(s) established if agreed so or worldwide if not specified.
  • Accept all the prefixes sent by JT. Those prefixes are the registered routes object at the RIPE NCC RSPL database ( originated by any AS number declared as member of the AS-JERSEYTELECOM AS-Macro.
  • Accept and route traffic sent by JT to the final destinations for each prefix advertised. No black-holing is allowed except for the purpose of DDoS mitigation.
  • Have its routing policy filed at RIPE or another IRR registry.
  • In case of multiple PPI or PNI, send the traffic to the interconnection JT has chosen, or to the closest exit if not specified (“hot potato” routing).

The candidate shall NOT:

  • Set a default route to JT’s network or set a route to JT’s network to a destination not being a part of the prefixes advertised by JT.
  • Advertise or re-advertise prefixes originated from AS(es) the candidate’s network learned from its own peerings.


  • Shutdown the peering if invalid prefixes are advertised by the candidate’s network to JT.
  • Shutdown the peering if packet-loss or abnormal round-trip time delays are observed.
  • Shutdown the peering in case of BGP session flap.
  • Shutdown the peering if the traffic amount is bellow the agreed level with the candidate upon PPI or PNI opening.
  • Ask the candidate to establish another PPI or PNI if the amount of traffic is above a certain level.
  • Shutdown the peering for a limited amount of time to perform maintenance or upgrades with its peering routers.
  • Send traffic to the candidate’s network to the closest exit (“hot potatoes” routing).

Peering request

If the candidate meets the prerequisites stated in this document or think that establishing a peering session would be beneficial to JT even if it does not, then please send your peering request by e-mail at:

Your request will be carefully evaluated by our peering committee and an answer be returned as quickly as possible.

If your peering policy requires JT to sign a peering agreement, please attach it to your peering request in order our legal department to be able to review it.