asn.dev

Internet exchange

Tampere Region Exchange

active Tampere, Finland TMP

Recorded members 68 addresses on file
Connected ports 27 across all participants
Peak traffic 7.8 Mbps peak, as recorded
Peering LANs 2 shared subnets

Overview

What this is

recorded

An internet exchange is shared switching where networks interconnect directly instead of paying a transit provider to carry traffic between them. Members take a port on the fabric and an address on the peering LANs below, then agree bilaterally (or through a route server) about which routes to exchange. Turning up at one is a deliberate choice about how a network wants to be reached, which is why exchange presence says something a routing table cannot.

Location
Tampere, Finland
Region
Europe
Airport code
TMP
Status
Active
PCH record updated
2018-04-02

Everything on this page is what Packet Clearing House had recorded when the directory was collected, not a live view of the fabric. Member counts in particular lag reality, and around 45% of the exchanges in this dataset publish no participant list at all.

Fabric

Peering LANs

2 on file

The shared subnets members take an address on. A network with an interface in one of these blocks is at this exchange by definition, which is what makes exchange presence a recorded fact rather than an inference. Most exchanges run one IPv4 and one IPv6 LAN; extra blocks are usually growth or a migration.

PrefixFamilyStatusParticipants
195.140.192.0/24IPv4Active26
2001:7f8:1d:4::/64IPv6Active27

Deprecated and retired blocks are listed rather than dropped. A decommissioned LAN still records how this fabric used to be reached, and filtering it would quietly rewrite the exchange's history.

Participants

Member networks

27 networks · 68 addresses

Every network PCH records with an address on one of the peering LANs above, ordered as the source ranks them: the most-connected participants first. Each network's addresses on the fabric are listed together, IPv4 first. Typing in the box narrows the rows below; Search looks through all 68 recorded addresses.

ASNetworkAddressesrDNSPolicy
AS12552GlobalConnect AB195.140.192.36195.140.192.372001:7f8:1d:4::3108:22001:7f8:1d:4::3108:1globalconnect1.tampere.trex.figlobalconnect2.tampere.trex.figlobalconnect2.tampere.trex.figlobalconnect1.tampere.trex.fiSelective
AS42708Glesys AB195.140.192.532001:7f8:1d:4::a6d4:1glesys2.tampere.trex.figlesys2.tampere.trex.fiSelective
AS42WoodyNet, Inc.195.140.192.282001:7f8:1d:4::2a:1pch42.tampere.trex.fipch42.tampere.trex.fiOpen
AS47605FNE-Finland Oy195.140.192.22195.140.192.252001:7f8:1d:4::b9f5:2fne1.tampere.trex.fifne2.tampere.trex.fifne2.tampere.trex.fiOpen
AS719Elisa Oyj195.140.192.10195.140.192.182001:7f8:1d:4::2cf:1trex1.tampere.trex.fielisa1.tampere.trex.fielisa1.tampere.trex.fiOpen
AS1759Telia Finland Oyj195.140.192.43195.140.192.442001:7f8:1d:4::6df:12001:7f8:1d:4::6df:2telia1.tampere.trex.fitelia2.tampere.trex.fitelia1.tampere.trex.fitelia2.tampere.trex.fiSelective
AS2603NORDUnet195.140.192.152001:7f8:1d:4::a2b:1nordunet.tampere.trex.finordunet.tampere.trex.fiSelective
AS3856Packet Clearing House, Inc.195.140.192.292001:7f8:1d:4::f10:1pch3856.tampere.trex.fipch3856.tampere.trex.fiOpen
AS1921ipcom GmbH195.140.192.482001:7f8:1d:4::781:1rcode0.tampere.trex.fircode0.tampere.trex.fiOpen
AS16302Suomi Communications Oy195.140.192.312001:7f8:1d:4::3fae:1suomicom.tampere.trex.fisuomicom.tampere.trex.fiOpen
AS112DNS-OARC195.140.192.1122001:7f8:1d:4::70:1as112.tampere.trex.fias112.tampere.trex.fiOpen
AS20904Cinia Oy195.140.192.35195.140.192.342001:7f8:1d:4::51a8:12001:7f8:1d:4::51a8:2cinia2.tampere.trex.ficinia1.tampere.trex.ficinia1.tampere.trex.ficinia2.tampere.trex.fiSelective
AS39699Lounea Palvelut Oy195.140.192.492001:7f8:1d:4::9b13:1lounea1.tampere.trex.filounea1.tampere.trex.fiSelective
AS42909Community DNS Limited195.140.192.242001:7f8:1d:4::a79d:1cdns.tampere.trex.ficdns.tampere.trex.fiOpen
AS199508S1 Networks Oy195.140.192.452001:7f8:1d:4:0:3:b54:1s1networks.tampere.trex.fis1networks.tampere.trex.fiOpen
AS1741Tieteen tietotekniikan keskus Oy195.140.192.172001:7f8:1d:4::6cd:1funet1.tampere.trex.fifunet1.tampere.trex.fiOpen
AS58003Planeetta Internet Oy195.140.192.302001:7f8:1d:4::e293:1planeetta.tampere.trex.fiplaneetta.tampere.trex.fiOpen
AS207003Web1 Oy195.140.192.472001:7f8:1d:4:0:3:289b:1web1.tampere.trex.fiweb1.tampere.trex.fiOpen
AS29243Domainkeskus Oy195.140.192.12195.140.192.112001:7f8:1d:4::723b:12001:7f8:1d:4::723b:2mmdnet2.tampere.trex.fimmdnet1.tampere.trex.fimmdnet1.tampere.trex.fimmdnet2.tampere.trex.fiOpen
AS215250Tobias Fiebig2001:7f8:1d:4:0:3:48d2:1v4less1.tampere.trex.fiOpen
AS39242Seclan Oy195.140.192.262001:7f8:1d:4::994a:1seclan1.tampere.trex.fiseclan1.tampere.trex.fiOpen
AS51164Knowit Solutions Oy195.140.192.20195.140.192.212001:7f8:1d:4::c7dc:12001:7f8:1d:4::c7dc:2——knowit1.tampere.trex.fiknowit2.tampere.trex.fi—
AS29432TREX Regional Exchanges Oy195.140.192.92001:7f8:1d:4::72f8:12001:7f8:1d:4::72f8:2trex2.tampere.trex.fitrex1.tampere.trex.fitrex2.tampere.trex.fiOpen
AS35382Glesys AB195.140.192.232001:7f8:1d:4::8a36:1glesys1.tampere.trex.figlesys1.tampere.trex.fiSelective
AS60414Baytems Holdings Oy195.140.192.522001:7f8:1d:4::ebfe:1netinch1.tampere.trex.finetinch1.tampere.trex.fiOpen
AS20569RIPE NETWORK COORDINATION CENTRE195.140.192.332001:7f8:1d:4::5059:1—ainacom.tampere.trex.fi—
AS197032TREX REGIONAL EXCHANGES OY195.140.192.1195.140.192.22001:7f8:1d:4::22001:7f8:1d:4::1mlpa1.route-server.trex.fimlpa2.route-server.trex.fimlpa2.route-server.trex.fimlpa1.route-server.trex.fiOpen

Peering policy is what the network declared to PCH, not something anyone verified, and an open policy is an invitation rather than a commitment. Absence of a network here means PCH has no record of it at this exchange, not that it is not present.

Provenance

Where this comes from

Exchange records come from the directory collected 2026-10-28 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,347 exchanges and 97,763 recorded member addresses, licensed CC BY-NC-SA 3.0.

This is a snapshot, not a live view. Members join and leave continuously, and the figures above are what PCH had on file on the collection date. PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.