ixreport

RNT

AS34723 · AS-RNT

Real Network and Tel SRL

2Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
2Using the route servers
1To fix in PeeringDB
4Facilities in PeeringDB

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

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on RNT'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 PeeringDBnone2001:7f8:64:225:0:3:4723:1
    • In the entry with IPv4 86.104.125.137: set IPv6 to 2001:7f8:64:225:0:3:4723:1 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

012Oct 3, 2026Nov 19, 20262
Show as a table
DateExchanges
Nov 19, 20262
Nov 18, 20262
Nov 17, 20262
Nov 16, 20262
Nov 15, 20262
Nov 14, 20262
Nov 13, 20262
Nov 12, 20262
Nov 11, 20262
Nov 10, 20262
Nov 9, 20262
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, 20261
Oct 13, 20261
Oct 12, 20261
Oct 11, 20261
Oct 10, 20261
Oct 9, 20261
Oct 8, 20261
Oct 7, 20261
Oct 6, 20261
Oct 5, 20261
Oct 4, 20261
Oct 3, 20261

Map

Where RNT'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 110G across 2 exchanges.

Romania InterLAN-IX Bucharest, Romania 86.104.125.137 10G Yes Both IPv6 not in PeeringDB
Romania RoNIX Bucharest, Romania 2001:7f8:49::35 100G Yes PeeringDB

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

These exchanges have a switch in a facility where RNT lists itself in PeeringDB, but don't have RNT 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 Balcan-IXBucharest, Romania 29 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 (4)

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

Romania NXDATA-1 Bucharest (BUH1)Bucharest 2 of 8
Romania NXDATA-2 Bucharest (BUH2)Bucharest 2 of 6
Romania iNES Datacenter BucharestBucharest 2 of 2
Romania RadiocomBucharest 1 of 1

Recent changes Search them

  • Oct 15, 2026 [PDB] AS34723 RNT added to RoNIX