asn.dev

Observed topology

AS206260 SVORKA Svorka AS

Unclassified RIPE Cable/DSL/ISP

Upstreams 7 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 8
Upstream graph Who carries AS206260, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS206260 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS206260: 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.

ASNetworkTypeFamiliesPaths seen
AS34087NTE TELEKOM ASResidentialIPv4 IPv6318
AS2116GLOBALCONNECT ASResidentialIPv4 IPv6156
AS6939Hurricane Electric LLCTransitIPv4 IPv6120
AS24482SG.GSHostingIPv4 IPv611
AS34927iFog GmbHHostingIPv4 IPv611
AS57381Daniel HusandUnclassifiedIPv4 IPv611
AS50304Blix Solutions ASUnclassifiedIPv410

Transit

Downstream networks

inferred

Networks for which AS206260 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS60908Sucom ASUnclassifiedIPv4 IPv6516
AS210152Jon Vanvik trading as Vanvik InternetUnclassifiedIPv4 IPv681

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS206260 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS34087NTE TELEKOM ASResidentialIPv4 IPv6665
AS60908Sucom ASUnclassifiedIPv4 IPv6516
AS6939Hurricane Electric LLCTransitIPv4 IPv6293
AS2116GLOBALCONNECT ASResidentialIPv4 IPv6193
AS210152Jon Vanvik trading as Vanvik InternetUnclassifiedIPv4 IPv6106
AS34927iFog GmbHHostingIPv4 IPv628
AS57381Daniel HusandUnclassifiedIPv4 IPv628
AS24482SG.GSHostingIPv4 IPv627
AS50304Blix Solutions ASUnclassifiedIPv424
AS33891Core-Backbone GmbHHostingIPv41

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.46M 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.