Observed topology
AS42861 FOTONTELECOM-TRANSIT-AS FOTONTELECOM ISP
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS42861: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 156 |
| AS8732 | JSC Comcor | Unclassified | IPv4 | 137 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 15 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 15 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 12 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 10 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 10 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 9 |
| AS25091 | IP-Max SA | Unclassified | IPv4 IPv6 | 9 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 9 |
Transit
Downstream networks
Networks for which AS42861 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS206066 | Teledom LLC | Unclassified | IPv4 | 261 |
| AS58024 | Isaev Kamil Magomedovich | Unclassified | IPv4 | 244 |
| AS49373 | Foton Telecom CJSC | Unclassified | IPv4 IPv6 | 222 |
| AS47954 | Alpha Net Telecom Ltd | Unclassified | IPv4 | 198 |
| AS44705 | Obyedinennye Nakhabinskie seti LLC | Unclassified | IPv4 | 123 |
| AS49381 | Com-Site Ltd | Unclassified | IPv4 | 122 |
| AS62459 | Dubrovka Telecom LLC | Unclassified | IPv4 | 90 |
| AS57661 | Deil Ltd. | Unclassified | IPv4 | 81 |
| AS59637 | RamSvyazInvest LLC | Unclassified | IPv4 | 60 |
| AS43287 | OOO "VIT" | Unclassified | IPv4 | 40 |
Adjacency
Adjacent networks
Every AS seen directly next to AS42861 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8732 | JSC Comcor | Unclassified | IPv4 | 835 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 333 |
| AS206066 | Teledom LLC | Unclassified | IPv4 | 261 |
| AS58024 | Isaev Kamil Magomedovich | Unclassified | IPv4 | 244 |
| AS49373 | Foton Telecom CJSC | Unclassified | IPv4 IPv6 | 222 |
| AS47954 | Alpha Net Telecom Ltd | Unclassified | IPv4 | 198 |
| AS44705 | Obyedinennye Nakhabinskie seti LLC | Unclassified | IPv4 | 126 |
| AS49381 | Com-Site Ltd | Unclassified | IPv4 | 122 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 113 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 99 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.