Observed topology
AS21453 FLEX-AS
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS21453: 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 |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 339 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 226 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 109 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 106 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 86 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 IPv6 | 83 |
| AS8641 | LLC "Nauka-Svyaz" | Unclassified | IPv4 IPv6 | 46 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 | 36 |
| AS29076 | Citytelecom LLC | Hosting | IPv6 | 29 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 19 |
Transit
Downstream networks
Networks for which AS21453 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS48149 | Ivanteevskie telecommunicacii Ltd | Unclassified | IPv4 IPv6 | 292 |
| AS34975 | Azimut-R Ltd. | Unclassified | IPv4 | 189 |
| AS201646 | Flex-l Ltd | Unclassified | IPv4 IPv6 | 163 |
| AS57489 | LLC "Telecom-Uslugi" | Unclassified | IPv4 | 145 |
| AS43567 | UG-TELECOM Ltd. | Unclassified | IPv4 | 100 |
| AS41783 | Informational technologies and electronic communications LLC | Unclassified | IPv4 IPv6 | 99 |
| AS35271 | JSC "AVIEL" | Unclassified | IPv4 IPv6 | 43 |
| AS50449 | Limited Liability Company "Kvant" | Unclassified | IPv4 | 38 |
| AS49893 | Bitrace telecom Ltd. | Unclassified | IPv4 | 32 |
| AS216335 | OOO Kalibr SB | Unclassified | IPv4 | 28 |
Adjacency
Adjacent networks
Every AS seen directly next to AS21453 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 811 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 308 |
| AS48149 | Ivanteevskie telecommunicacii Ltd | Unclassified | IPv4 IPv6 | 299 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 IPv6 | 225 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 210 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 197 |
| AS34975 | Azimut-R Ltd. | Unclassified | IPv4 | 189 |
| AS8641 | LLC "Nauka-Svyaz" | Unclassified | IPv4 IPv6 | 175 |
| AS201646 | Flex-l Ltd | Unclassified | IPv4 IPv6 | 163 |
| AS49893 | Bitrace telecom Ltd. | Unclassified | IPv4 | 158 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-24 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.94M 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.