Observed topology
AS5467 MIPT Non state educational institution "Educational Scientific and Experimental Center of Moscow Institute of Physics and Technology"
Education RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS5467: 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 |
|---|---|---|---|---|
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 | 82 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 82 |
| AS8732 | JSC Comcor | Unclassified | IPv4 | 20 |
| AS24482 | SG.GS | Hosting | IPv4 | 6 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 6 |
| AS25091 | IP-Max SA | Unclassified | IPv4 | 4 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 2 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS5467 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS25100 | Non state educational institution "Educational Scientific and Experimental Center of Moscow Institute of Physics and Technology" | Unclassified | IPv4 | 222 |
| AS51520 | "Datalogika" Ltd. | Unclassified | IPv4 | 26 |
| AS42892 | PE Filimonov Boris Yurievich | Residential | IPv4 | 15 |
| AS61396 | Okno-TV LLC | Unclassified | IPv4 | 8 |
Adjacency
Adjacent networks
Every AS seen directly next to AS5467 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS25100 | Non state educational institution "Educational Scientific and Experimental Center of Moscow Institute of Physics and Technology" | Unclassified | IPv4 | 222 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 170 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 | 144 |
| AS8732 | JSC Comcor | Unclassified | IPv4 | 52 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 33 |
| AS51520 | "Datalogika" Ltd. | Unclassified | IPv4 | 26 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 19 |
| AS24482 | SG.GS | Hosting | IPv4 | 15 |
| AS42892 | PE Filimonov Boris Yurievich | Residential | IPv4 | 15 |
| AS25091 | IP-Max SA | Unclassified | IPv4 | 10 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.