Observed topology
AS48858 Milecom-as JSC "ER-Telecom Holding"
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS48858: 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 |
|---|---|---|---|---|
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 IPv6 | 144 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 107 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 | 20 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 14 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 5 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 5 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 5 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 5 |
| AS6797 | GlobalConnect AB | Unclassified | IPv4 | 4 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 4 |
Transit
Downstream networks
Networks for which AS48858 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39785 | Axioma, LLC | Residential | IPv4 | 353 |
| AS31695 | Limited Company "Intermedia" | Unclassified | IPv4 | 286 |
| AS56451 | Telekey-S Ltd | Unclassified | IPv4 | 282 |
| AS50029 | Telecom Ltd. | Unclassified | IPv4 | 279 |
| AS12418 | Quantum CJSC | Unclassified | IPv4 | 276 |
| AS47909 | BAIKAL TELECOM LLC | Unclassified | IPv4 IPv6 | 272 |
| AS203493 | Egor Timoshenko | Hosting | IPv4 IPv6 | 262 |
| AS61031 | ESCOMTEL BACKGROUND COMMUNICATION NETWORKS Ltd. | Residential | IPv4 | 182 |
| AS31257 | Orion Telecom LLC | Residential | IPv4 IPv6 | 134 |
| AS42574 | Novaya Sibir Plus Ltd. | Unclassified | IPv4 | 118 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48858 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,464 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 IPv6 | 987 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 | 827 |
| AS203493 | Egor Timoshenko | Hosting | IPv4 IPv6 | 647 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 376 |
| AS39785 | Axioma, LLC | Residential | IPv4 | 353 |
| AS47909 | BAIKAL TELECOM LLC | Unclassified | IPv4 IPv6 | 290 |
| AS31695 | Limited Company "Intermedia" | Unclassified | IPv4 | 286 |
| AS56451 | Telekey-S Ltd | Unclassified | IPv4 | 282 |
| AS50029 | Telecom Ltd. | Unclassified | IPv4 | 279 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.