Observed topology
AS21430 WIA-AS WIA spol. s.r.o.
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS21430: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 1,505 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 766 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 720 |
| AS39392 | SH.cz s.r.o. | Hosting | IPv4 IPv6 | 399 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 387 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 70 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 70 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 66 |
| AS8218 | Zayo Infrastructure France SA | Unclassified | IPv4 IPv6 | 11 |
| AS1764 | Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH | Unclassified | IPv4 IPv6 | 10 |
Transit
Downstream networks
Networks for which AS21430 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS203376 | Mailkit s.r.o. | Unclassified | IPv4 IPv6 | 147 |
| AS33943 | Quadruple a.s. | Unclassified | IPv4 IPv6 | 91 |
| AS15614 | Dragon Internet a.s. | Residential | IPv4 | 82 |
| AS204183 | Omnivery s.r.o. | Unclassified | IPv4 | 60 |
| AS209369 | The Cloud Provider s.r.o. | Hosting | IPv4 | 46 |
| AS48451 | Prazska energetika, a.s. | Unclassified | IPv4 IPv6 | 37 |
| AS42189 | Druzstvo EUROSIGNAL | Unclassified | IPv4 | 35 |
| AS12608 | IGLG Network CZ s.r.o. | Hosting | IPv4 IPv6 | 29 |
| AS39761 | ABAK, Co.Ltd. | Unclassified | IPv4 | 20 |
Adjacency
Adjacent networks
Every AS seen directly next to AS21430 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 1,634 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 979 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 775 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 518 |
| AS39392 | SH.cz s.r.o. | Hosting | IPv4 IPv6 | 465 |
| AS203376 | Mailkit s.r.o. | Unclassified | IPv4 IPv6 | 147 |
| AS15614 | Dragon Internet a.s. | Residential | IPv4 | 127 |
| AS33943 | Quadruple a.s. | Unclassified | IPv4 IPv6 | 91 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 81 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 79 |
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.