asn.dev

Observed topology

AS206075 HOLLANDER-JACOBSEN Hollander & Jacobsen UG (haftungsbeschraenkt)

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS206075: 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
AS3257GTT Communications Inc.TransitIPv4 IPv6228
AS212477RoyaleHosting BVHostingIPv4 IPv672

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215960Hollander & Jacobsen UG (haftungsbeschraenkt)UnclassifiedIPv4 IPv6345
AS40663IncogNet LLCVPNIPv4 IPv6330
AS212085Alexander BruegmannUnclassifiedIPv664
AS204789BIZBETA LTDUnclassifiedIPv632
AS206042Suhail HarisUnclassifiedIPv632
AS215956Dennis de Houx trading as All In OneUnclassifiedIPv632
AS200690Junxiao ShiUnclassifiedIPv65

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS3257GTT Communications Inc.TransitIPv4 IPv6513
AS215960Hollander & Jacobsen UG (haftungsbeschraenkt)UnclassifiedIPv4 IPv6345
AS3399Obenet ABUnclassifiedIPv4 IPv6332
AS40663IncogNet LLCVPNIPv4 IPv6330
AS212477RoyaleHosting BVHostingIPv4 IPv6193
AS6939Hurricane Electric LLCTransitIPv4 IPv690
AS212085Alexander BruegmannUnclassifiedIPv664
AS204789BIZBETA LTDUnclassifiedIPv632
AS206042Suhail HarisUnclassifiedIPv632
AS215956Dennis de Houx trading as All In OneUnclassifiedIPv632

All 13 adjacent →

Provenance

Where this comes from

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