Observed topology
AS48422 IT-STARCOM-AS www.itstarcom.net
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS48422: 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 | 796 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 157 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 | 33 |
| AS6663 | Euroweb Romania S.R.L. | Unclassified | IPv6 | 32 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 18 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 17 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 16 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 6 |
| AS12859 | BIT BV | Hosting | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS48422 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS52180 | Nikolay Victorovich Kucheruk PE | Unclassified | IPv4 | 469 |
| AS43110 | Joint Ukrainian-American enterprise Ewropol with legal form Ltd | Unclassified | IPv4 | 408 |
| AS52103 | FOP Molodnyak Ruslan Petrovich | Unclassified | IPv4 | 320 |
| AS44416 | Satellite Net Service LLC | Residential | IPv4 | 306 |
| AS56812 | CHP Zarko Alexandr Ivanovich | Unclassified | IPv4 | 295 |
| AS29443 | PP Technical Company Mega | Unclassified | IPv4 | 253 |
| AS44673 | FOP Vitaly Podkhalyuzin Evgenyevich | Unclassified | IPv4 | 195 |
| AS56526 | PC Media Zmijov | Unclassified | IPv4 | 171 |
| AS25143 | Company "Zagalni Merezhi" Ltd | Unclassified | IPv4 | 156 |
| AS209117 | FOP ZEIDA VLADISLAV BORISOVICH | Unclassified | IPv4 | 147 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48422 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 4,488 |
| AS43110 | Joint Ukrainian-American enterprise Ewropol with legal form Ltd | Unclassified | IPv4 | 1,003 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 540 |
| AS52180 | Nikolay Victorovich Kucheruk PE | Unclassified | IPv4 | 469 |
| AS44416 | Satellite Net Service LLC | Residential | IPv4 | 341 |
| AS52103 | FOP Molodnyak Ruslan Petrovich | Unclassified | IPv4 | 320 |
| AS29443 | PP Technical Company Mega | Unclassified | IPv4 | 318 |
| AS56812 | CHP Zarko Alexandr Ivanovich | Unclassified | IPv4 | 295 |
| AS25143 | Company "Zagalni Merezhi" Ltd | Unclassified | IPv4 | 208 |
| AS44673 | FOP Vitaly Podkhalyuzin Evgenyevich | Unclassified | IPv4 | 195 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-17 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.18M 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.