Observed topology
AS20632 PETERSTAR-AS Saint-Petersburg
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS20632: 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 |
|---|---|---|---|---|
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 3,909 |
Transit
Downstream networks
Networks for which AS20632 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS200123 | Kola Geological Information Laboratory Centre OJSC | Unclassified | IPv4 | 120 |
| AS60623 | ATCOM Joint Stock Company | Unclassified | IPv4 | 96 |
| AS42340 | JSC "TVSZ" | Unclassified | IPv4 | 60 |
| AS44665 | PAO Sovcomflot | Unclassified | IPv4 | 60 |
| AS49994 | RIC-Info Ltd | Unclassified | IPv4 | 60 |
| AS51723 | TKB Investment Partners (JSC) | Unclassified | IPv4 | 60 |
| AS57451 | SITILAYN Ltd. | Unclassified | IPv4 | 60 |
| AS57573 | JSC "Greenatom" | Unclassified | IPv4 | 60 |
| AS198626 | Limited Liability Company "Northern Capital Gateway" | Unclassified | IPv4 | 60 |
| AS201913 | Theorema Telecom Limited | Unclassified | IPv4 | 60 |
Adjacency
Adjacent networks
Every AS seen directly next to AS20632 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 5,656 |
| AS200123 | Kola Geological Information Laboratory Centre OJSC | Unclassified | IPv4 | 120 |
| AS60623 | ATCOM Joint Stock Company | Unclassified | IPv4 | 96 |
| AS42340 | JSC "TVSZ" | Unclassified | IPv4 | 60 |
| AS44665 | PAO Sovcomflot | Unclassified | IPv4 | 60 |
| AS49994 | RIC-Info Ltd | Unclassified | IPv4 | 60 |
| AS51723 | TKB Investment Partners (JSC) | Unclassified | IPv4 | 60 |
| AS57451 | SITILAYN Ltd. | Unclassified | IPv4 | 60 |
| AS57573 | JSC "Greenatom" | Unclassified | IPv4 | 60 |
| AS198626 | Limited Liability Company "Northern Capital Gateway" | Unclassified | IPv4 | 60 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-01 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.48M 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.