IP Transit

IP Transit

High capacity connectivity to the global internet


Elisa IP Transit Service provides global internet connectivity for IT integrators, information service providers and internet service providers who need reliable, high-capacity global internet connectivity. The service is based on Elisa’s domestic and international IP network and peering agreements with a large number of IP backbone providers and major international content delivery networks.
Elisa IP Transit provides connectivity to the internet, including domestic traffic. Domestic and international traffic are not calculated separately. Elisa IP Transit is also suitable for customers who wish to build a redundant and fault tolerant routing environment by purchasing IP transit from multiple sources.


Elisa IP Transit with low-latency and high-performance backbone network


Elisa IP also supports IP version 6, which it has done now for over a decade. In addition to domestic and international peering arrangements, Elisa IP is connected to multiple global Tier 1 and Tier 2 networks. Through these arrangements our customers’ networking environments join the global internet community. Elisa can flexibly use its domestic and international infrastructure when finding a suitable physical peering point for the customers. Elisa’s strong presence in Finland, the Baltics and Scandinavia makes it possible for Elisa to hand over the service in  hundreds of different street addresses. The last mile fibre for connectivity to customer premises can also be added to the service as an extra component.


IP Transit Service Description

Our network

Elisa's international backbone is a network with exchange points in Helsinki, Stockholm, Amsterdam, Oslo, Copenhagen, New York, London and Frankfurt.


We use the following physical connections:

  • Helsinki 2 - Stockholm 1
  • Espoo - Stockholm 4
  • Espoo - Tallinn 2
  • Helsinki 2 - Tallinn 1
  • Stockholm 1 - Amsterdam
  • Stockholm 4 - Frankfurt 2
  • Amsterdam - London
  • London - Frankfurt
  • Amsterdam - Frankfurt 2
  • Tallinn - Riga
  • Riga - Vilnius
  • Vilnius - Frankfurt 2
  • Helsinki 2 - St. Ptersburg
  • St. Petersburg - Moscow
  • Moscow - Frankfurt 2

Exchange points


Peering Agreement

The exchange of routes will be over BGPv4.

  • We will annouce the routes that are registered for the Autonomous Systems listed on the Réseaux IP Européen s as-macro object AS-EUNETIP and RS-EUNETIP.
  • Neither party will send traffic to destinations not announced by the other party through the other party's Internet Network. This also means that neither party will establish a default route directed towards the other.
  • The peering is based on good will and best effort. Neither party is liable to the other party for losses or damage from interruption of peering for any period of time.
  • Both parties acknowledge that this peering agreement is not legally binding, nor is it intended to be.


A legally binding and detailed peering agreement can be separately agreed upon. If you are interested in peering, please contact peering(at)elisa.fi


Peering Policy


If you are interested in peering, please contact peering(at)elisa.fi.
Elisa Peering Policy in Finland.
The document is in Finnish.

Routing Policy

This is how our routing works:

  • We usually announce our own routes summarized the way that we received the IP blocks from Réseaux IP Européens.
  • We announce our AS customers' routes the way they announce them to us, unless the customer requests proxy aggregation. We will make effort to ensure that the customers' routes are efficiently aggregated though. We also take protective measures to prevent harm originating from our customers to the global routing system.
  • We do not redistribute our IGP into BGP (nor do we redistribute BGP into the IGP.)
  • We follow RIPE's dampening regulations thus we do not damp routes.
  • We will filter routes and traffic to illegal destinations such as IANA reserved networks. We won't accept traffic that should originate from within our own network. We protect ourselves from over specific routes and accept them only on a case by case basis. Please refer to our other documents about filtering etc.
  • Our AS at all exchanges is AS6667 and we announce the ASes listed in the Réseaux IP Européens AS macros AS-EUNETIP and RS-EUNETIP.


Peering Locations

Elisa Exchange Point Connections



Route and Packet Filtering

AS6667 filters routes considered harmful at the border. These can be of the following types:

Our own IP blocks
IANA reserved IP blocks
Prefixes longer than /24 (netmask
Prefixes longer than /22 (netmask

We will never accept prefixes more specific than /24. We will always accept /24 routes within The Swamp ( Outside that range the default filter will get rid of prefixes longer than /22.

If a peer's routes are otherwise well behaved, but they have a few legitimate routes that would get caught by the default filter, we will use a more lenient filter. Should we ever give a peer subnets from our own CIDR allocations (such as if a customer with a large continuous chunk of address space moved to another provider), there's also a filter that lets almost anything through.


AS6667 filters packets with source or destination addresses considered harmful at the border. These would be either our own IP addresses or those reserved for special purposes by IANA.

BGP Communities

These communities are recognized and used by AS6667

NOTE: These communities will evolve with changes in transit providers and exchange points. If you are having problems with the communities, check here first to see if a community has been changed or removed. We will try to not change the meaning of a community unless the new meaning is a direct replacement.


Local Preference


The communities that set the local preference within our network are usable by all customers and peers. The default local preference for customers is 101 and for peers it is 100. The default local preference for transits is 90. Local preference of 80 is meant for backup provided by a customer or peer to someone else and the local preference of 110 is meant for overriding routing to choose a certain path over others. Peers can't set a preference of 110.


Community Effect
6667:80 Set LOCAL_PREF to 80
6667:90 Set LOCAL_PREF to 90
6667:100 Set LOCAL_PREF to 100
6667:110 Set LOCAL_PREF to 110


Announce Route


The communities that control route announcement to peers and transits are only available to customers. The x specifies what the action for the said target is:

0 Announce as is ..
1 Announce with 6667 prepended to as-path ...
2 Announce with 6667 6667 prepended to as-path ...
3 Announce with 6667 6667 6667 prepended to as-path ...
9 Don't announce ... (default and takes precedence if present)

We will also let external communities through from customers. This will enable customers to use similar communities of our peers and transits. Some pages describing these communities have been collected at the end of the page.


Community Effect
6667:90x to all AS6667 customers
6667:100x to all transits
6667:101x to AS3356 CenturyLink
6667:102x to AS174 Cogent
6667:107x to AS3257 GTT Communications
6667:109x to AS1299 TSIC
X:200x to all peers
X:201x to peers in Helsinki Finland and at Ficix
719:202x to peers in Tampere Finland
790:202x to peers in Tampere Finland
6667:202x to peers in Stockholm Sweden and at Netnod-stockholm (Netnod)
6667:203x to peers in London UK and at LINX
6667:204x to peers in Frankfurt Germany and at DECIX
6667:206x to peers in Copenhagen Denmark and at DIX
6667:207x to peers in Oslo Norway and at NIX
6667:208x to peers in Amsterdam Netherlands and at AMSIX
6667:209x to peers in New York USA and at NYIIX
6667:210x to peer AS8359 (Comstar)
6667:211x to peer AS3249 (Elion)



Route Origins


These communities are tagged on all routes to distinguish their origins. They are sent to everyone but not excepted from outside. They are there to let customers filter routes based on route source.

Standard customers announce all their routes to us with communities 6667:900, 6667:1000 and 6667:2000. When Elisa receives the routes, they are tagged with 6667:300x and the local location community (6667:4xxx.)


Community Effect
X:3000 Internal or customer
X:3001 Public peering
X:3003 Private peering
X:3004 Transit
X:4000 Tampere, Finland
X:4001 Turku, Finland
X:4002 Helsinki, Finland
X:4003 Oulu, Finland
6667:4003 Stockholm, Sweden
6667:4004 London, United Kingdom
6667:4005 Frankfurt, Germany
6667:4007 Copenhagen, Denmark
6667:4008 Oslo, Norway
6667:4009 Amsterdam, The Netherlands
6667:4010 New York, United States
6667:4011 Tallinn, Estonia