ixreport

TENET

AS6876 · TENET

7Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
7Using the route servers
1To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with TENET? · Where should TENET peer next? · Compare TENET with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in TENET's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on TENET's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs40G1.2T
    • In the entry with IPv4 80.81.193.73: set Speed to 1200000 (1.2T) (now 40000).

Exchanges over time

02468Oct 3, 2026Nov 19, 20267
Show as a table
DateExchanges
Nov 19, 20267
Nov 18, 20267
Nov 17, 20267
Nov 16, 20267
Nov 15, 20267
Nov 14, 20267
Nov 13, 20267
Nov 12, 20267
Nov 11, 20267
Nov 10, 20267
Nov 9, 20267
Nov 8, 20267
Nov 7, 20267
Nov 6, 20267
Nov 5, 20267
Nov 4, 20267
Nov 3, 20267
Nov 2, 20267
Nov 1, 20267
Oct 31, 20267
Oct 30, 20267
Oct 29, 20267
Oct 28, 20267
Oct 27, 20267
Oct 26, 20267
Oct 25, 20267
Oct 24, 20267
Oct 23, 20267
Oct 22, 20267
Oct 21, 20267
Oct 20, 20267
Oct 19, 20267
Oct 18, 20267
Oct 17, 20267
Oct 16, 20267
Oct 15, 20267
Oct 14, 20267
Oct 13, 20267
Oct 12, 20267
Oct 11, 20267
Oct 10, 20267
Oct 9, 20267
Oct 8, 20267
Oct 7, 20267
Oct 6, 20267
Oct 5, 20267
Oct 4, 20267
Oct 3, 20267

Map

Where TENET's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 470G across 7 exchanges.

Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 185.0.42.87
185.0.42.95
2001:7f8:115:1::87
2001:7f8:115:1::95
2 × 40G Yes Both
Ukraine 1-IX UA Kyiv, Ukraine 185.1.213.87
185.1.213.95
2001:7f8:14d::87
2001:7f8:14d::95
2 × 40G Yes Both
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.193.73 2001:7f8::1adc:0:1 40G 74 routes Both Speed differs
Ukraine DTEL-IX Kiev, Ukraine 193.25.180.143 2001:7f8:63::8f 40G Yes PeeringDB
Ukraine Giganet IXN Amsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine 185.0.48.38
185.0.48.101
2001:7f8:6c:65::48:38
2001:7f8:6c:65::48:101
100G + 40G Yes PeeringDB
Ukraine Giganet IXN Odesa Odessa, Ukraine 193.34.196.171
193.34.196.172
2001:7f8:6c:3::171 2 × 40G Yes PeeringDB
Ukraine UA-IX Kiev, Ukraine 185.1.50.41 2001:7f8:5d::41 10G Yes Both

Exchanges in its buildings that it isn't on (4)

These exchanges have a switch in a facility where TENET lists itself in PeeringDB, but don't have TENET as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Netherlands GNM-IXAmsterdam, Netherlands 741 OD-IX
Ukraine RUDAKI-IXKiev, Ukraine 53 OD-IX
Poland Giganet IXN WarsawWarsaw, Poland 49 OD-IX
Ukraine Giganet IXN KharkіvKharkiv, Ukraine 13 OD-IX
Facilities (1)

The buildings TENET lists in PeeringDB, and how many of the exchanges in each it's on.

Ukraine OD-IXOdesa 3 of 7