Observed topology
AS51331 MODERNTV
Hosting RIPE Content
Transit
Upstream networks
Networks observed carrying traffic for AS51331: 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 |
|---|---|---|---|---|
| AS25512 | CD-Telematika a.s. | Unclassified | IPv4 IPv6 | 170 |
| AS42000 | Futruy s.r.o. | Unclassified | IPv6 | 87 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 66 |
| AS25248 | RADIOKOMUNIKACE a.s. | Unclassified | IPv4 IPv6 | 62 |
| AS8778 | Slovanet a.s. | Residential | IPv4 | 59 |
| AS8251 | FreeTel, s.r.o. | Hosting | IPv4 | 47 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 9 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 9 |
| AS20562 | Broadband Hosting B.V. | Hosting | IPv4 | 6 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 6 |
Transit
Downstream networks
Networks for which AS51331 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS198813 | SychrovNET s.r.o | Unclassified | IPv4 | 21 |
Adjacency
Adjacent networks
Every AS seen directly next to AS51331 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS25512 | CD-Telematika a.s. | Unclassified | IPv4 IPv6 | 170 |
| AS42000 | Futruy s.r.o. | Unclassified | IPv6 | 87 |
| AS25248 | RADIOKOMUNIKACE a.s. | Unclassified | IPv4 IPv6 | 86 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 66 |
| AS8778 | Slovanet a.s. | Residential | IPv4 | 59 |
| AS8251 | FreeTel, s.r.o. | Hosting | IPv4 | 47 |
| AS198813 | SychrovNET s.r.o | Unclassified | IPv4 | 28 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 10 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 9 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 9 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M 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.