Observed topology
AS47872 SOFIA-CONNECT-AS Sofia Connect EAD
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS47872: 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 |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 196 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 189 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 110 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 94 |
| AS31287 | IPACCT CABLE Ltd | Unclassified | IPv4 | 30 |
| AS8280 | SYNAPSECOM S.A. Provider of Telecommunications and Internet Services | Hosting | IPv4 IPv6 | 7 |
| AS8551 | Bezeq International Ltd. | Unclassified | IPv4 | 7 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 1 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS47872 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS51582 | Cifrova Kabelna Korporacia EOOD | Residential | IPv4 IPv6 | 451 |
| AS20771 | Caucasus Online Ltd. | Unclassified | IPv4 | 258 |
| AS60325 | Optiland Telecommunications I.K.E. | Unclassified | IPv4 | 133 |
| AS202634 | Petar Petrov | Unclassified | IPv4 IPv6 | 122 |
| AS42555 | OPTICCOM- BULGARIA Ltd. | Unclassified | IPv4 | 101 |
| AS209681 | Deltacom Electronics Ltd. | Unclassified | IPv4 IPv6 | 61 |
| AS207094 | Inter Carrier Ltd | Unclassified | IPv4 | 57 |
| AS211128 | Sky Fiber AD | Unclassified | IPv4 | 57 |
| AS204639 | H-Tech EOOD | Unclassified | IPv4 | 46 |
| AS212416 | Proximity EOOD | Unclassified | IPv4 IPv6 | 26 |
Adjacency
Adjacent networks
Every AS seen directly next to AS47872 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 3,872 |
| AS20771 | Caucasus Online Ltd. | Unclassified | IPv4 | 3,502 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 589 |
| AS51582 | Cifrova Kabelna Korporacia EOOD | Residential | IPv4 IPv6 | 451 |
| AS8280 | SYNAPSECOM S.A. Provider of Telecommunications and Internet Services | Hosting | IPv4 IPv6 | 311 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 293 |
| AS42555 | OPTICCOM- BULGARIA Ltd. | Unclassified | IPv4 | 263 |
| AS8551 | Bezeq International Ltd. | Unclassified | IPv4 | 239 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 154 |
| AS60325 | Optiland Telecommunications I.K.E. | Unclassified | IPv4 | 133 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.