ixreport

Global Communication Net AD

AS12615 · AS12615

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

Tools: Where can I peer with Global Communication Net AD? · Where should Global Communication Net AD peer next? · Compare Global Communication Net AD with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in Global Communication Net AD's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Global Communication Net AD'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 (3)

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. Bulgaria B-IX Sofia, Bulgaria · PeeringDB 326
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.1.30.16185.1.30.16 185.1.30.131
    • Add an entry: IPv4 185.1.30.131, IPv6 –, speed 10000 (10G), RS peer yes.
  2. Bulgaria BIX.BG Sofia, Bulgaria · PeeringDB 331
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.169.198.156193.169.198.156 193.169.198.157
    IPv6 address missing from PeeringDB2001:7f8:58::3147:0:12001:7f8:58::3147:0:1 2001:7f8:58::3147:0:2
    • Add an entry: IPv4 193.169.198.157, IPv6 2001:7f8:58::3147:0:2.
  3. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.236.48178.18.236.48 178.18.236.127
    IPv6 address missing from PeeringDB2a03:5f80:4:2::236:482a03:5f80:4:2::236:48 2a03:5f80:4:2::236:127
    • Add an entry: IPv4 178.18.236.127, IPv6 2a03:5f80:4:2::236:127, speed 10000 (10G), RS peer yes.

    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

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

Map

Where Global Communication Net AD'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 101G across 5 exchanges.

Bulgaria B-IX Sofia, Bulgaria 185.1.30.16 10G 333 routes Both IPv4 not in PeeringDB
Bulgaria BIX.BG Sofia, Bulgaria 193.169.198.156 2001:7f8:58::3147:0:1 40G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.236.48 2a03:5f80:4:2::236:48 10G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB
Bulgaria NetIX Sofia, Bulgaria 185.1.226.212
185.1.226.213
185.1.226.236
185.1.226.237
2001:67c:29f0::1:2615:1
2001:67c:29f0::1:2615:2
2001:67c:29f0::1:2615:3
2001:67c:29f0::1:2615:4
4 × 10G Yes Both
Bulgaria VarnaIX Varna, Bulgaria 185.1.137.150 2001:7f8:db::1:2615:1 1G Yes PeeringDB

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

These exchanges have a switch in a facility where Global Communication Net AD lists itself in PeeringDB, but don't have Global Communication Net AD 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.

Poland 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 283 TELEPOINT Sofia Centre; Equinix SO1 - Sofia; TELEPOINT Sofia East
Romania InterLAN-IXBucharest, Romania 149 TELEPOINT Sofia Centre
Netherlands Global-IXAmsterdam, Netherlands 138 TELEPOINT Sofia Centre
Ukraine RUDAKI-IXKiev, Ukraine 53 TELEPOINT Sofia East
Bulgaria TurkIX SofiaSofia, Bulgaria 47 TELEPOINT Sofia Centre; Equinix SO1 - Sofia; S3 Company Ltd.
Serbia SOX SerbiaBelgrade/Serbia, Serbia 46 Sofia Data Center (SDC); TELEPOINT Sofia Centre
Romania RoNIXBucharest, Romania 43 TELEPOINT Sofia Centre
Romania Balcan-IXBucharest, Romania 29 TELEPOINT Sofia Centre
Türkiye GIBIRIXİstanbul, Türkiye 28 TELEPOINT Sofia Centre
Bulgaria 1-BG FREESofia, Bulgaria 22 TELEPOINT Sofia Centre; Equinix SO1 - Sofia
Bulgaria MegaIX SofiaSofia, Bulgaria 20 TELEPOINT Sofia Centre; Equinix SO1 - Sofia
Türkiye RegPEXAnkara, Türkiye 19 TELEPOINT Sofia Centre; S3 Company Ltd.
Greece NVL-IXAthens, Greece 14 TELEPOINT Sofia Centre
Bulgaria T-CIXSofia, Bulgaria 9 TELEPOINT Sofia Centre
United States Global Peer ExchangeWashington, United States 6 Sofia Data Center (SDC)
Facilities (5)

The buildings Global Communication Net AD lists in PeeringDB, and how many of the exchanges in each it's on.

Bulgaria TELEPOINT Sofia CentreSofia 4 of 17
Bulgaria Equinix SO1 - SofiaSofia 3 of 7
Bulgaria Sofia Data Center (SDC)Sofia 3 of 5
Bulgaria TELEPOINT Sofia EastSofia 2 of 4
Bulgaria S3 Company Ltd.Sofia 1 of 3