Observed topology
AS35000 SEVEREN-TELECOM_TRANSIT SEVEREN-TELECOM
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS35000: 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 | 1,157 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 503 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 348 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 90 |
| AS24482 | SG.GS | Hosting | IPv4 | 40 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 40 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 40 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 40 |
| AS56655 | Gigahost AS | Unclassified | IPv4 | 40 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 40 |
Transit
Downstream networks
Networks for which AS35000 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS24739 | JSC "Severen-Telecom" | Unclassified | IPv4 IPv6 | 5,329 |
| AS43267 | JSC "Severen-Telecom" | Unclassified | IPv4 | 898 |
| AS35278 | SPRINTHOST.RU LLC | Hosting | IPv4 IPv6 | 664 |
| AS57334 | SPB State Unitary Enterprise "ATS Smolnogo" | Unclassified | IPv4 | 505 |
| AS208178 | Federal State Institution "National Library of Russia (NLR)" | Unclassified | IPv4 IPv6 | 222 |
| AS39749 | Befree Ltd | Unclassified | IPv4 | 163 |
| AS201193 | Internet Projects JSC | Unclassified | IPv4 IPv6 | 129 |
| AS211892 | WaveAccess Nordics ApS | Unclassified | IPv4 IPv6 | 125 |
| AS6858 | JSC "Severen-Telecom" | Unclassified | IPv4 | 120 |
| AS209446 | VAS Experts Ltd | Unclassified | IPv4 IPv6 | 92 |
Adjacency
Adjacent networks
Every AS seen directly next to AS35000 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS24739 | JSC "Severen-Telecom" | Unclassified | IPv4 IPv6 | 5,900 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 4,520 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 3,615 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,595 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 1,572 |
| AS43267 | JSC "Severen-Telecom" | Unclassified | IPv4 | 898 |
| AS35278 | SPRINTHOST.RU LLC | Hosting | IPv4 IPv6 | 664 |
| AS57334 | SPB State Unitary Enterprise "ATS Smolnogo" | Unclassified | IPv4 | 507 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 248 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 245 |
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.