Observed topology
AS12615 GCN-AS GCN AD - Sofia, Bulgaria
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS12615: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 572 |
| AS57463 | NetIX Communications JSC | Unclassified | IPv4 IPv6 | 476 |
| AS44901 | Belcloud LTD | Hosting | IPv4 | 340 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 282 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 264 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 168 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 148 |
| AS1273 | IDDQD-AS | Business | IPv4 | 134 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 48 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 48 |
Transit
Downstream networks
Networks for which AS12615 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39401 | Link+ Ltd | Unclassified | IPv4 | 742 |
| AS49040 | K and G UNISAT -TV LLC | Unclassified | IPv4 | 560 |
| AS38932 | Rimex Ltd. | Unclassified | IPv4 | 432 |
| AS29622 | ICON Ltd | Unclassified | IPv4 | 418 |
| AS205352 | KABELNET LTD | Unclassified | IPv4 | 413 |
| AS42086 | RO&NI EOOD | Unclassified | IPv4 IPv6 | 276 |
| AS49849 | MG 2002 LTD. | Unclassified | IPv4 | 232 |
| AS35773 | iConnect Ltd. | Residential | IPv4 IPv6 | 220 |
| AS44313 | Set Service Ltd. | Residential | IPv4 | 208 |
| AS199191 | Dimitar Vasilev-9 EOOD | Unclassified | IPv4 | 177 |
Adjacency
Adjacent networks
Every AS seen directly next to AS12615 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,286 |
| AS39401 | Link+ Ltd | Unclassified | IPv4 | 1,118 |
| AS57463 | NetIX Communications JSC | Unclassified | IPv4 IPv6 | 1,028 |
| AS44901 | Belcloud LTD | Hosting | IPv4 | 981 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 943 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 696 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 669 |
| AS1273 | IDDQD-AS | Business | IPv4 | 648 |
| AS49040 | K and G UNISAT -TV LLC | Unclassified | IPv4 | 560 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 439 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.