Observed topology
AS42000 KAORA Futruy s.r.o.
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS42000: 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 IPv6 | 225 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 87 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 6 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 6 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 5 |
| AS39392 | SH.cz s.r.o. | Hosting | IPv4 | 5 |
| AS1764 | Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH | Unclassified | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS42000 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS200918 | Pavel Zizka | Unclassified | IPv4 IPv6 | 455 |
| AS199657 | TNtech, s.r.o. | Residential | IPv4 IPv6 | 274 |
| AS51586 | ServerZone s.r.o. | Unclassified | IPv4 IPv6 | 192 |
| AS62298 | Computer Systems Consulting s.r.o. | Unclassified | IPv4 IPv6 | 97 |
| AS57081 | Scarfbot Technologies, s.r.o. | Unclassified | IPv4 IPv6 | 96 |
| AS60086 | Valvera s.r.o. | Unclassified | IPv4 IPv6 | 44 |
| AS26431 | Happy Telecommunications LLC | Hosting | IPv4 | 42 |
| AS49985 | IP4ISP z.s.p.o | Unclassified | IPv4 IPv6 | 33 |
| AS204332 | TKC system s.r.o. | Residential | IPv6 | 30 |
| AS9080 | Ipex A.S | Unclassified | IPv6 | 26 |
Adjacency
Adjacent networks
Every AS seen directly next to AS42000 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,030 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 910 |
| AS200918 | Pavel Zizka | Unclassified | IPv4 IPv6 | 455 |
| AS199657 | TNtech, s.r.o. | Residential | IPv4 IPv6 | 308 |
| AS197019 | WEDOS Internet, a.s. | Hosting | IPv4 IPv6 | 245 |
| AS26431 | Happy Telecommunications LLC | Hosting | IPv4 IPv6 | 194 |
| AS51586 | ServerZone s.r.o. | Unclassified | IPv4 IPv6 | 192 |
| AS62298 | Computer Systems Consulting s.r.o. | Unclassified | IPv4 IPv6 | 99 |
| AS57081 | Scarfbot Technologies, s.r.o. | Unclassified | IPv4 IPv6 | 96 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 55 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-01 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.48M 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.