Observed topology
AS209810 NETCORESERVICES Netcore services s.r.o.
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS209810: 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 |
|---|---|---|---|---|
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 222 |
| AS39392 | SH.cz s.r.o. | Hosting | IPv4 IPv6 | 131 |
| AS1764 | Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH | Unclassified | IPv4 IPv6 | 7 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 7 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 7 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 7 |
| AS20562 | Broadband Hosting B.V. | Hosting | IPv4 | 6 |
| AS43413 | NEW TELEKOM, spol. s r.o. | Unclassified | IPv4 IPv6 | 6 |
Transit
Downstream networks
Networks for which AS209810 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39736 | ICT Support, s.r.o. | Unclassified | IPv4 IPv6 | 210 |
| AS207187 | TKR Jasek, s.r.o. | Unclassified | IPv4 | 162 |
| AS62405 | Brouzdal, s.r.o. | Unclassified | IPv4 IPv6 | 92 |
| AS201116 | Vybezek.NET s.r.o. | Unclassified | IPv4 IPv6 | 92 |
| AS31349 | a-net Liberec s.r.o. | Residential | IPv4 | 82 |
| AS210061 | Ladislav Kepl | Unclassified | IPv4 | 59 |
| AS199490 | INTERCONNECT s.r.o. | Residential | IPv4 | 24 |
| AS210111 | Netcraft Solutions s.r.o. | Unclassified | IPv4 | 5 |
| AS43413 | NEW TELEKOM, spol. s r.o. | Unclassified | IPv4 IPv6 | 3 |
Adjacency
Adjacent networks
Every AS seen directly next to AS209810 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 1,180 |
| AS207187 | TKR Jasek, s.r.o. | Unclassified | IPv4 | 640 |
| AS39392 | SH.cz s.r.o. | Hosting | IPv4 IPv6 | 327 |
| AS39736 | ICT Support, s.r.o. | Unclassified | IPv4 IPv6 | 210 |
| AS62405 | Brouzdal, s.r.o. | Unclassified | IPv4 IPv6 | 92 |
| AS201116 | Vybezek.NET s.r.o. | Unclassified | IPv4 IPv6 | 92 |
| AS31349 | a-net Liberec s.r.o. | Residential | IPv4 | 82 |
| AS210061 | Ladislav Kepl | Unclassified | IPv4 | 59 |
| AS199490 | INTERCONNECT s.r.o. | Residential | IPv4 | 36 |
| AS43413 | NEW TELEKOM, spol. s r.o. | Unclassified | IPv4 IPv6 | 31 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-12 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.36M 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.