asn.dev

Observed topology

AS206575 DATABOX-AS

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS206575: 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
AS174Cogent Communications, LLCTransitIPv4592
AS6939Hurricane Electric LLCTransitIPv4400
AS1299Arelion Sweden ABTransitIPv4126

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS25277POSLuH d.o.o, za informaticke usluge i trgovinuHostingIPv4198
AS209463Spar Business Services GmbHUnclassifiedIPv463
AS218649Alca Zagreb d.o.o.UnclassifiedIPv461
AS199106Mireo d.d.UnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4699
AS174Cogent Communications, LLCTransitIPv4612
AS25277POSLuH d.o.o, za informaticke usluge i trgovinuHostingIPv4198
AS1299Arelion Sweden ABTransitIPv4184
AS209463Spar Business Services GmbHUnclassifiedIPv463
AS218649Alca Zagreb d.o.o.UnclassifiedIPv461
AS199106Mireo d.d.UnclassifiedIPv458
AS205714Telemach Hrvatska d.o.o.UnclassifiedIPv43

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.