asn.dev

Observed topology

AS205235 LABITAT

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS205235: 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
AS42541Fiberby ApSResidentialIPv4 IPv6130

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205280Jens AndersenUnclassifiedIPv4 IPv6138
AS62113Kracon ApSUnclassifiedIPv4 IPv6132
AS211153Emil PetersenUnclassifiedIPv6111
AS207727Asbjorn Sloth Tonnesen trading as a5nUnclassifiedIPv4 IPv695
AS208327Toke Hoiland-JorgensenUnclassifiedIPv4 IPv695
AS198275Thomas FlummerUnclassifiedIPv637

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS42541Fiberby ApSResidentialIPv4 IPv6738
AS205280Jens AndersenUnclassifiedIPv4 IPv6138
AS62113Kracon ApSUnclassifiedIPv4 IPv6132
AS211153Emil PetersenUnclassifiedIPv6111
AS207727Asbjorn Sloth Tonnesen trading as a5nUnclassifiedIPv4 IPv695
AS208327Toke Hoiland-JorgensenUnclassifiedIPv4 IPv695
AS198275Thomas FlummerUnclassifiedIPv637

Provenance

Where this comes from

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