asn.dev

Observed topology

AS51519 Karabro Karabro AB

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51519: 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 IPv6122
AS6939Hurricane Electric LLCTransitIPv4 IPv626
AS8434Telenor Sverige ABResidentialIPv42
AS12552GlobalConnect ABUnclassifiedIPv42
AS20473The Constant Company, LLCHostingIPv61
AS24482SG.GSHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS212085Alexander BruegmannUnclassifiedIPv668
AS213366Albin HakansonUnclassifiedIPv668
AS43099Curie Point ABUnclassifiedIPv4 IPv661
AS58057Securebit AGUnclassifiedIPv4 IPv642
AS216100Rui LiUnclassifiedIPv638
AS208478Karabro ABUnclassifiedIPv634
AS212079Sweroam ABUnclassifiedIPv4 IPv611
AS202687Mainloop ABHostingIPv4 IPv62

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS3935131173 Services ABVPNIPv4 IPv6350
AS6939Hurricane Electric LLCTransitIPv4 IPv6101
AS212085Alexander BruegmannUnclassifiedIPv668
AS213366Albin HakansonUnclassifiedIPv668
AS43099Curie Point ABUnclassifiedIPv4 IPv661
AS58057Securebit AGUnclassifiedIPv4 IPv642
AS216100Rui LiUnclassifiedIPv638
AS208478Karabro ABUnclassifiedIPv634
AS20473The Constant Company, LLCHostingIPv612
AS212079Sweroam ABUnclassifiedIPv4 IPv611

All 14 adjacent →

Provenance

Where this comes from

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