Observed topology
AS29084 COMNET-AS ComNet Bulgaria
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS29084: 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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,423 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,318 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 2,103 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 1,378 |
| AS8866 | Vivacom Bulgaria EAD | Residential | IPv4 | 694 |
| AS8280 | SYNAPSECOM S.A. Provider of Telecommunications and Internet Services | Hosting | IPv4 IPv6 | 131 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 129 |
| AS57463 | NetIX Communications JSC | Unclassified | IPv6 | 52 |
| AS12615 | Global Communication Net Plc | Unclassified | IPv6 | 2 |
| AS24482 | SG.GS | Hosting | IPv6 | 2 |
Transit
Downstream networks
Networks for which AS29084 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS49849 | MG 2002 LTD. | Unclassified | IPv4 | 180 |
| AS42855 | OMEGA-NET Ltd | Unclassified | IPv4 | 60 |
| AS61975 | "Global Net Technology" AD | Unclassified | IPv4 | 51 |
| AS203484 | ROAD INFRASTRUCTURE AGENCY | Unclassified | IPv4 | 37 |
| AS204266 | CENTRAL PARK BURGAS -EOOD | Unclassified | IPv4 | 33 |
| AS59463 | VISION 2008 Ltd. | Residential | IPv4 | 17 |
| AS203312 | Global Pharma Centre JSC | Unclassified | IPv4 | 11 |
Adjacency
Adjacent networks
Every AS seen directly next to AS29084 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,501 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,437 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 2,147 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 1,397 |
| AS8866 | Vivacom Bulgaria EAD | Residential | IPv4 | 823 |
| AS49849 | MG 2002 LTD. | Unclassified | IPv4 | 180 |
| AS8280 | SYNAPSECOM S.A. Provider of Telecommunications and Internet Services | Hosting | IPv4 IPv6 | 131 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 129 |
| AS42855 | OMEGA-NET Ltd | Unclassified | IPv4 | 60 |
| AS57463 | NetIX Communications JSC | Unclassified | IPv6 | 52 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-20 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.16M 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.