Observed topology
AS24739 SEVEREN-TELECOM St.Petersburg, Russia
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS24739: 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 |
|---|---|---|---|---|
| AS35000 | JSC "Severen-Telecom" | Unclassified | IPv4 IPv6 | 5,330 |
Transit
Downstream networks
Networks for which AS24739 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS44174 | Public Joint-Stock-Company Territorial Generating Company-1 | Unclassified | IPv4 | 127 |
| AS201721 | "AKT" LLC | Unclassified | IPv4 | 60 |
| AS203803 | TELVIO, Ltd. | Unclassified | IPv4 | 60 |
| AS205849 | LLC "MP Group Isteit" | Unclassified | IPv4 | 60 |
| AS206403 | Fund of Anatoly Mikhailovich Granov | Unclassified | IPv4 | 60 |
| AS60832 | O`KEY, Limited Liability Company | Unclassified | IPv4 IPv6 | 39 |
| AS48223 | Senator Telecom Ltd. | Unclassified | IPv4 IPv6 | 35 |
| AS201016 | NPF Berkut Ltd | Unclassified | IPv4 | 31 |
| AS201515 | Medical Center XXI century, Autonomous Non-profit organisation | Unclassified | IPv4 | 19 |
| AS57274 | JSC Petersburg Social Commercial Bank | Unclassified | IPv4 | 14 |
Adjacency
Adjacent networks
Every AS seen directly next to AS24739 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35000 | JSC "Severen-Telecom" | Unclassified | IPv4 IPv6 | 5,839 |
| AS44174 | Public Joint-Stock-Company Territorial Generating Company-1 | Unclassified | IPv4 | 127 |
| AS201721 | "AKT" LLC | Unclassified | IPv4 | 60 |
| AS203803 | TELVIO, Ltd. | Unclassified | IPv4 | 60 |
| AS205849 | LLC "MP Group Isteit" | Unclassified | IPv4 | 60 |
| AS206403 | Fund of Anatoly Mikhailovich Granov | Unclassified | IPv4 | 60 |
| AS60832 | O`KEY, Limited Liability Company | Unclassified | IPv4 IPv6 | 39 |
| AS48223 | Senator Telecom Ltd. | Unclassified | IPv4 IPv6 | 36 |
| AS201016 | NPF Berkut Ltd | Unclassified | IPv4 | 31 |
| AS201515 | Medical Center XXI century, Autonomous Non-profit organisation | Unclassified | IPv4 | 19 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.