Observed topology
AS25549 AVANTEL-AS JSC "ER-Telecom Holding"
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS25549: 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 |
|---|---|---|---|---|
| AS31200 | Novotelecom Ltd | Unclassified | IPv4 | 1,785 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 IPv6 | 964 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 845 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 91 |
| AS8359 | MTS PJSC | Mobile | IPv4 | 57 |
| AS201706 | SERVICEPIPE LLC | Unclassified | IPv4 | 39 |
| AS1299 | Arelion Sweden AB | Transit | IPv6 | 8 |
Transit
Downstream networks
Networks for which AS25549 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS48679 | Consultant Ltd. | Unclassified | IPv4 | 240 |
| AS44310 | INTERNET TECHNOLOGIES LLC | Unclassified | IPv4 | 79 |
| AS62331 | Media Holding TVK Ltd. | Unclassified | IPv4 | 65 |
| AS211343 | LLC Flex | Unclassified | IPv4 | 62 |
| AS3335 | Federal State Educational Institution of Higher Professional Education "Novosibirsk State University, National Research" | Education | IPv4 | 61 |
| AS50452 | Bank Accept JSC | Unclassified | IPv4 | 60 |
| AS199778 | LLC "Management Company LAMA" | Unclassified | IPv4 | 59 |
| AS41143 | OOO Ob-Telecom | Unclassified | IPv4 | 48 |
| AS214149 | CJSC "Center for Digital Certificates" | Unclassified | IPv4 | 36 |
| AS203514 | ROSSKO-K Ltd. | Unclassified | IPv4 | 31 |
Adjacency
Adjacent networks
Every AS seen directly next to AS25549 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS31200 | Novotelecom Ltd | Unclassified | IPv4 | 1,788 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 IPv6 | 1,496 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 909 |
| AS48679 | Consultant Ltd. | Unclassified | IPv4 | 240 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 93 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 92 |
| AS44310 | INTERNET TECHNOLOGIES LLC | Unclassified | IPv4 | 83 |
| AS25478 | iHome LLC | Unclassified | IPv4 | 65 |
| AS62331 | Media Holding TVK Ltd. | Unclassified | IPv4 | 65 |
| AS201706 | SERVICEPIPE LLC | Unclassified | IPv4 | 65 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-12 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.36M 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.