Observed topology
AS20723 MGI AVONET, s.r.o.
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS20723: 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 |
|---|---|---|---|---|
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 167 |
| AS30058 | FDCservers.net | Unclassified | IPv4 | 119 |
| AS47232 | ISP Alliance a.s. | Residential | IPv4 IPv6 | 71 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 57 |
| AS16019 | Vodafone Czech Republic a.s. | Unclassified | IPv4 | 12 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 8 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 8 |
| AS8218 | Zayo Infrastructure France SA | Unclassified | IPv4 | 7 |
| AS1764 | Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH | Unclassified | IPv4 | 6 |
Transit
Downstream networks
Networks for which AS20723 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS204405 | Durnet.cz sro | Unclassified | IPv6 | 36 |
Adjacency
Adjacent networks
Every AS seen directly next to AS20723 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 192 |
| AS30058 | FDCservers.net | Unclassified | IPv4 | 119 |
| AS47232 | ISP Alliance a.s. | Residential | IPv4 IPv6 | 100 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 57 |
| AS204405 | Durnet.cz sro | Unclassified | IPv6 | 36 |
| AS2852 | CESNET z.s.p.o. | Education | IPv4 | 20 |
| AS16019 | Vodafone Czech Republic a.s. | Unclassified | IPv4 | 12 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 9 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 9 |
| AS8218 | Zayo Infrastructure France SA | Unclassified | IPv4 | 7 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.