ixreport

Beltelecom

AS6697

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

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

5 things to fix in Beltelecom's PeeringDB record, from what its exchanges publish: 3 to add, 2 to correct. As of 2026-11-19 12:40 UTC.

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

Add these exchanges (3)

On the exchange's own member list, but not in Beltelecom's PeeringDB record. Add one entry per connection with these values.

  1. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214From its IX-F export and website members list
    IPv4185.1.170.38
    IPv62001:7f8:9e::1a29:0:1
    Speed100000 Mbps (100G)
    RS peerYes
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74From its IX-F export and website members list
    IPv4185.1.210.45
    IPv62001:7f8:3d::1a29:0:1
    Speed100000 Mbps (100G)
    RS peerYes
  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248From its IX-F export and website members list
    IPv4185.1.208.48
    IPv62001:7f8:44::1a29:0:1
    Speed100000 Mbps (100G)
    RS peerYes

Correct these entries (2)

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 differs40G100G
    • In the entry with IPv4 80.81.194.197: set Speed to 100000 (100G) (now 40000).
  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address differs178.18.225.215178.18.227.34
    IPv6 address differs2a03:5f80:4::225:2152a03:5f80:4::227:34
    Port speed differs60G100G
    • In the entry with IPv4 178.18.225.215: set IPv4 to 178.18.227.34 (now 178.18.225.215); set IPv6 to 2a03:5f80:4::227:34 (now 2a03:5f80:4::225:215); set Speed to 100000 (100G) (now 60000).

    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

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 Beltelecom'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 440G across 7 exchanges.

Germany DE-CIX Dusseldorf Düsseldorf, Germany 185.1.170.38 2001:7f8:9e::1a29:0:1 100G 642 routes Not in PeeringDB
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.194.197 2001:7f8::1a29:0:1 40G 717 routes Both Speed differs
Germany DE-CIX Hamburg Hamburg, Germany 185.1.210.45 2001:7f8:3d::1a29:0:1 100G 642 routes Not in PeeringDB
Germany DE-CIX Munich Munich, Germany 185.1.208.48 2001:7f8:44::1a29:0:1 100G 642 routes Not in PeeringDB
Russia Eurasia Peering IX Moscow, Russia 185.232.60.131 2a0d:e180::60:131 10G PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.215 2a03:5f80:4::225:215 60G Yes Both IPv4 differsIPv6 differsSpeed differs
Russia MSK-IX Moscow Moscow, Russia 195.208.209.236 2001:7f8:20:101::209:236 30G Yes Both

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

These exchanges have a switch in a facility where Beltelecom lists itself in PeeringDB, but don't have Beltelecom 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 NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 672 NewTelco Frankfurt
Poland TPIX PLWarsaw, Poland 480 NewTelco Frankfurt
Germany KleyReXFrankfurt, Germany 471 NewTelco Frankfurt
Russia PITER-IX Saint-PetersburgSaint-Petersburg, Russia 246 Moscow M9
Russia PITER-IX MoscowMoscow, Russia 243 Moscow M9
Bulgaria NetIXSofia, Bulgaria 204 NewTelco Frankfurt
Germany PITER-IX FrankfurtFrankfurt, Germany 172 NewTelco Frankfurt
Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9
Russia W-IXMoscow, Russia 66 Moscow M9
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Germany MAINPORT Peer-ExchangeFrankfurt am Main, Germany 14 NewTelco Frankfurt
Germany City-IX FrankfurtFrankfurt, Germany 7 NewTelco Frankfurt
United States Global Peer ExchangeWashington, United States 6 NewTelco Frankfurt
Facilities (2)

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

Russia Moscow M9Moscow 3 of 9
Germany NewTelco FrankfurtFrankfurt 1 of 9