ixreport

TeenTelecom

AS34304 · Teen

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

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on TeenTelecom'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. Romania InterLAN-IX Bucharest, Romania · PeeringDB 270
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDB2001:7f8:64:225:0:3:4304:12001:7f8:64:225:0:3:4304:1 2001:7f8:64:225:0:3:4304:2
    Port speed differs2 × 10G10G + 1G
    • In the entry with IPv4 86.104.125.182: set IPv6 to 2001:7f8:64:225:0:3:4304:2 (now empty); set Speed to 1000 (1G) (now 10000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

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

In the last 30 days TeenTelecom joined 1 exchange and left 0. Growing networks

Joined

  • RoNIX Bucharest Nov 9, 2026 PeeringDB only

Map

Where TeenTelecom'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 40G across 3 exchanges.

Romania Balcan-IX Bucharest, Romania 80.97.248.28 10G Yes PeeringDB
Romania InterLAN-IX Bucharest, Romania 86.104.125.82
86.104.125.182
2001:7f8:64:225:0:3:4304:1 2 × 10G Yes Both IPv6 not in PeeringDBSpeed differs
Romania RoNIX Bucharest, Romania 185.1.103.40 2001:7f8:49::40 10G Yes PeeringDB

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

These exchanges have a switch in a facility where TeenTelecom lists itself in PeeringDB, but don't have TeenTelecom 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 NXDATA-1 Bucharest (BUH1)
Bulgaria NetIXSofia, Bulgaria 204 NXDATA-1 Bucharest (BUH1)
Netherlands Global-IXAmsterdam, Netherlands 138 NXDATA-1 Bucharest (BUH1)
Bulgaria B-IXSofia, Bulgaria 77 NXDATA-1 Bucharest (BUH1); NXDATA-2 Bucharest (BUH2)
Romania DSIXBucharest, Romania 18 NXDATA-2 Bucharest (BUH2)
Türkiye EURASIA-IX.NETIstanbul, Türkiye 6 NXDATA-1 Bucharest (BUH1)
United States Global Peer ExchangeWashington, United States 6 NXDATA-2 Bucharest (BUH2)
Facilities (2)

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

Romania NXDATA-1 Bucharest (BUH1)Bucharest 3 of 8
Romania NXDATA-2 Bucharest (BUH2)Bucharest 3 of 6

Recent changes Search them

  • Nov 9, 2026 [PDB] AS34304 TeenTelecom added to RoNIX