The configuration for open peering and EdgeTPIX is the same.
Service configuration
Check the information needed to properly configure the services available through TPIX platform
Open peering and EdgeTPIX
IP addresses of route servers:
| RS1 | IPv4 | 195.149.232.1 | AS29535 |
| RS2 | IPv4 | 195.149.233.1 | AS29535 |
| RS1 | IPv6 | 2001:7f8:27::2:9535:1 | AS29535 |
| RS2 | IPv6 | 2001:7f8:27::2:9535:2 | AS29535 |
AS29535 is used by route servers only to establish BGP sessions and is removed from BGP paths broadcast to open peering participants.
Open peering – communities supported by route servers:
| 0:peer – Do not announce to a specific peer |
| 29535:0:peer – Do not announce to a specific peer (large community) |
| 29535:peer – Announce to a specific peer |
| 29535:1:peer – Announce to a specific peer (large community) |
| 0:29535 – Do not announce to anybody |
| 29535:0:0 – Do not announce to anybody (large community) |
| 29535:29535 – Announce to all (default) |
| 0:65001 – Do not announce to GGC |
29535:997 – blackholing for a single IP /32
65050:190 – set localpref=190 (instead of default 200) at the interface Open peering – Internet.optimum
List of prefixes reachable in TPIX open peering
State as on 2025-10-30
Prefixes of carriers participating in open peering
Records reported by carriers having BGP sessions with open peering route servers
Looking Glass of TPIX platform
Shows routes available through TPIX open peering and routes through Tier-1 or other IXs, as long as the prefixes in question are not available in TPIX open peering
Private peering
Establishing direct traffic exchange with content providers present on the TPIX platform allows you to significantly increase traffic in open peering, improve the quality and reduce the costs of purchasing transit services. Proximity to content sources and the ability to use them is also of great importance to the end user.
We are constantly increasing the number and quality of sources on the TPIX platform. Some of them do not use connections to RS (Route Server) TPIX, so their traffic does not automatically appear on your connection to TPIX open peering.
To exchange traffic with a given content provider, it is necessary to establish a private BGP session with it, in accordance with its peering policy. We set up sessions based on the same VLAN open peering, where – as a TPIX participant – you have a BGP session with TPIX Route Servers and exchange traffic with typical TPIX participants.
How to set up private peering?
-
Correctly register or verify your network description (ASN) in Peering DB.
-
Create or verify a route record in the RIPE Database to link your prefixes to your ASN.
-
Create or verify an AS-SET record in the RIPE database to list all the ASNs whose prefixes you want to broadcast.
-
Prepare your ASN and IPv4 and IPv6 addresses at the TPIX interface, which you will send to the peering partner so that it knows with whom to establish a BGP session.
-
Send an email or fill out the form according to the rules listed next to it and appropriate for the given provider (for Microsoft via Azure account, etc.), providing all the information from the points above and requesting to establish a peering session in TPIX (ASN 29535).
Amazon addressing in TPIX:
-
IPv4: 195.149.232.79
-
IPv6: 2001:7f8:27::1:6509
Amazon peering policy:
-
Before starting the peering setup process, please read the provider’s peering policy: https://aws.amazon.com/peering/policy
-
In the matter of set up traffic exchange, please contact the provider directly: by e-mail at peering-emea@amazon.com or in accordance with the instructions specified in the peering policy.
Cloudflare addressing in TPIX:
-
IP v4: 195.149.232.128
-
IP v6: 2001:7f8:27::1:3335:1
Cloudflare peering policy:
-
Before starting the peering setup process, please read the provider’s peering policy: https://www.cloudflare.com/peering -policy
-
Private peering with Cloudflare must be configured yourself. A link to the self-configuration page is available in the Cloudflare description record in PeeringDB AS13335 – Cloudflare – PeeringDB
Meta Platforms (Facebook) addressing in TPIX:
-
IPv4: 195.149.233.217, 195.149.232.104
-
IPv6: 2001:7f8:27::3:2934:1, 2001:7f8:27::3:2934:2
Meta Platforms (Facebook) peering policy:
-
To establish private peering with Meta Platforms, follow the instructions on the website: https://www.facebook.com/peering
Microsoft addressing in TPIX:
-
IP v4: 195.149.232.105
-
IP v4: 195.149.232.50
-
IP v6: 2001:7f8:27::8075:1
-
IP v6: 2001:7f8:27::8075:3
Microsoft peering policy:
-
https://docs.microsoft.com/pl-pl/azure/internet-peering/policy
-
To establish peering, follow the instructions on the website.
Internet.optimum
Internet.optimum AS29535 is a Tier-2 transit service that has Arelion (AS1299), Open Transit (AS5511), Hurricane Electric (AS6939), DE-CIX, TPIX and PLIX as traffic sources.
AS29535 also has direct contact with AS5617. In the Internet.optimum service traffic volume toward AS5617 is limited to 30% of the ordered bandwidth.
Communities in Internet.optimum
Arelion – AS1299
| 29535:1100 – do not advertise to AS1299 |
| 29535:1101 – prepend 1x |
| 29535:1102 – prepend 2x |
| 29535:1103 – prepend 3x |
OTI – AS5511
| 29535:1200 – do not advertise to AS5511 |
| 29535:1201 – prepend 1x |
| 29535:1202 – prepend 2x |
| 29535:1203 – prepend 3x |
Hurricane Electric – AS6939
| 29535:4510 – do not advertise to AS6939 |
| 29535:4511 – prepend 1x |
| 29535:4512 – prepend 2x |
| 29535:4513 – prepend 3x |
Inter.Link – AS5405
| 29535:4580 – do not advertise to AS5405 |
| 29535:4581 – prepend 1x |
| 29535:4582 – prepend 2x |
| 29535:4583 – prepend 3x |
ZAYO – AS6461
| 29535:4590 – do not advertise to AS6461 |
| 29535:4591 – prepend 1x |
| 29535:4592 – prepend 2x |
| 29535:4593 – prepend 3x |
DE-CIX
| 29535:4100 – do not advertise to DE-CIX |
| 29535:4101 – prepend 1x |
| 29535:4102 – prepend 2x |
| 29535:4103 – prepend 3x |
PLIX
| 29535:4300 – do not advertise to PLIX |
| 29535:4301 – prepend 1x |
| 29535:4302 – prepend 2x |
| 29535:4303 – prepend 3x |
THINX
| 29535:4400 – do not advertise to THINX |
| 29535:4401 – prepend 1x |
| 29535:4402 – prepend 2x |
| 29535:4403 – prepend 3x |
TPIX
| 29535:4900 – do not advertise to TPIX |
| 29535:4901 – prepend 1x |
| 29535:4902 – prepend 2x |
| 29535:4903 – prepend 3x |
29535:997 – blackholing for single IPs /32
29535:9190 – set localpref=190 (instead of default 200)
List of Internet.optimum customers
AS29535:as-mix2
Looking Glass AS29535
Shows routes available through TPIX open peering and routes through Tier-1 or other IXs, as long as the prefixes in question are not available in TPIX open peering
Internet.world/TPNET
Internet.world AS5617 is a Tier-2 transit service that has Arelion (AS1299) and Open Transit (AS5511) as traffic sources.
It provides direct peering with AS5617, but with bandwidth of traffic towards this ASN limited to 50%.
For higher bandwidth limits, there are dedicated TPNET peering services with a different pricing model, but with the same community, looking glass, etc.
Communities in Internet.world/TPNET
Arelion – AS1299
| 5617:1100 – do not advertise to AS1299 |
| 5617:1101 – prepend 1x |
| 5617:1102 – prepend 2x |
| 5617:1103 – prepend 3x |
5617:997 – blackholing for single IPs /32
OTI – AS5511
| 5617:1200 – do not advertise to AS5511 |
| 5617:1201 – prepend 1x |
| 5617:1202 – prepend 2x |
| 5617:1203 – prepend 3x |
List of Internet.world/TPNET customers (AS5617:as-world-transit)
List of customers of Internet.world and TPNET peering with access to foreign routes
List of Internet.world/TPNET customers (AS5617:as-pl-transit)
List of customers of TPNET peering without access to foreign routes
Looking Glass AS5617
Shows routes available in AS5617
Multicast
Access to TV package providers – SGT, EVIO, Korbank and Nasza-Wizja. Using Multicast, you can power your own TV service for end users.
Korbank, Nasza-Wizja
Connections to Korbank and Nasza-Wizja are made via a direct VLAN in any access technology.
EVIO, SGT
Connections to Evio and SGT are made via VLAN in any access technology from anywhere in the country.
VLANs are terminated on TPIX router in Warsaw with the PIM protocol.
Specifics of PIM connection:
| BPG session on private AS numbers as routing protocol |
| Set-Top-Box addressing assigned by the content provider (Evio, SGT) |
