Observed topology
AS31430 TEL-NET-AS
Residential APNIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS31430: 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,225 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 IPv6 | 497 |
| AS8732 | JSC Comcor | Unclassified | IPv4 IPv6 | 66 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 44 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 | 34 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 33 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 32 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 32 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 29 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv6 | 17 |
Transit
Downstream networks
Networks for which AS31430 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS200293 | ES TELECOM LLC | Unclassified | IPv4 | 310 |
| AS52201 | OOO Suntel | Hosting | IPv4 IPv6 | 277 |
| AS56705 | OSM-Telecom LLC | Unclassified | IPv4 | 186 |
| AS35301 | OOO CCCMOS GROUP RUS | Unclassified | IPv4 | 124 |
| AS20826 | LLC AST-ENGINEERING | Unclassified | IPv4 | 62 |
| AS42911 | Iskra-VEKT Ltd. | Unclassified | IPv4 | 62 |
| AS50739 | OOO Suntel | Unclassified | IPv4 | 62 |
| AS58019 | A.P.R. Limited Liability Company | Unclassified | IPv4 | 62 |
| AS48991 | Nikitin Maxim Sergeevich | Unclassified | IPv4 | 61 |
| AS206630 | "Standard Telecom" LLC | Unclassified | IPv4 | 46 |
Adjacency
Adjacent networks
Every AS seen directly next to AS31430 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 2,039 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 IPv6 | 853 |
| AS52201 | OOO Suntel | Hosting | IPv4 IPv6 | 335 |
| AS200293 | ES TELECOM LLC | Unclassified | IPv4 | 310 |
| AS56705 | OSM-Telecom LLC | Unclassified | IPv4 | 186 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 IPv6 | 129 |
| AS35301 | OOO CCCMOS GROUP RUS | Unclassified | IPv4 | 124 |
| AS8732 | JSC Comcor | Unclassified | IPv4 IPv6 | 84 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 73 |
| AS20826 | LLC AST-ENGINEERING | Unclassified | IPv4 | 62 |
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.