Observed topology
AS47232 ISPALLIANCE
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS47232: 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 | 330 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 308 |
| AS39392 | SH.cz s.r.o. | Hosting | IPv4 IPv6 | 82 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 30 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 16 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 16 |
| AS1764 | Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH | Unclassified | IPv4 | 10 |
| AS20562 | Broadband Hosting B.V. | Hosting | IPv4 | 10 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 10 |
Transit
Downstream networks
Networks for which AS47232 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS201476 | ISP Alliance a.s. | Unclassified | IPv4 IPv6 | 841 |
| AS16276 | OVH SAS | Hosting | IPv4 | 688 |
| AS44002 | Sys-DataCom s.r.o. | Residential | IPv4 IPv6 | 480 |
| AS210712 | ISP Alliance a.s. | Unclassified | IPv4 IPv6 | 449 |
| AS204666 | Jiri Tlapak | Unclassified | IPv4 IPv6 | 427 |
| AS204064 | CEZNET s.r.o. | Unclassified | IPv4 IPv6 | 332 |
| AS207886 | ECOMP spol s r.o. | Unclassified | IPv4 IPv6 | 310 |
| AS197296 | United Networks SE | Unclassified | IPv4 IPv6 | 273 |
| AS197879 | HelaPC s.r.o. | Unclassified | IPv4 IPv6 | 245 |
| AS33883 | TRIOPTIMUM s.r.o. | Unclassified | IPv4 IPv6 | 214 |
Adjacency
Adjacent networks
Every AS seen directly next to AS47232 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS202297 | Skylon Solutions Limited | Unclassified | IPv4 | 5,602 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 4,552 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,906 |
| AS16276 | OVH SAS | Hosting | IPv4 | 1,168 |
| AS39392 | SH.cz s.r.o. | Hosting | IPv4 IPv6 | 907 |
| AS201476 | ISP Alliance a.s. | Unclassified | IPv4 IPv6 | 841 |
| AS201053 | Stowarzyszenie e-Poludnie | Unclassified | IPv4 | 762 |
| AS16019 | Vodafone Czech Republic a.s. | Unclassified | IPv4 | 501 |
| AS44002 | Sys-DataCom s.r.o. | Residential | IPv4 IPv6 | 480 |
| AS204666 | Jiri Tlapak | Unclassified | IPv4 IPv6 | 462 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.