asn.dev

Observed topology

AS204538 KHOSTING Kareby Hosting AB

Hosting RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS204538: 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
AS3935131173 Services ABVPNIPv4 IPv6106
AS3399Obenet ABUnclassifiedIPv4 IPv638
AS6939Hurricane Electric LLCTransitIPv4 IPv630
AS24482SG.GSHostingIPv4 IPv64
AS50304Blix Solutions ASUnclassifiedIPv44
AS12552GlobalConnect ABUnclassifiedIPv42
AS20473The Constant Company, LLCHostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS48093Webland ABUnclassifiedIPv4240

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3935131173 Services ABVPNIPv4 IPv6246
AS48093Webland ABUnclassifiedIPv4240
AS3399Obenet ABUnclassifiedIPv4 IPv698
AS6939Hurricane Electric LLCTransitIPv4 IPv654
AS50304Blix Solutions ASUnclassifiedIPv412
AS24482SG.GSHostingIPv4 IPv68
AS12552GlobalConnect ABUnclassifiedIPv46
AS20473The Constant Company, LLCHostingIPv62

Provenance

Where this comes from

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