asn.dev

Observed topology

AS12087 SALSGIVER - Salsgiver, Inc.

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12087: 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
AS3356Level 3 Parent, LLCTransitIPv4480
AS174Cogent Communications, LLCTransitIPv4419
AS6939Hurricane Electric LLCTransitIPv4144
AS701Verizon BusinessResidentialIPv460

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS23130Diamond Pharmacy ServicesUnclassifiedIPv458
AS46881ACMH HospitalUnclassifiedIPv451
AS55118Value Drug Company Inc.UnclassifiedIPv45

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4538
AS174Cogent Communications, LLCTransitIPv4457
AS6939Hurricane Electric LLCTransitIPv4160
AS701Verizon BusinessResidentialIPv462
AS23130Diamond Pharmacy ServicesUnclassifiedIPv458
AS46881ACMH HospitalUnclassifiedIPv451
AS55118Value Drug Company Inc.UnclassifiedIPv45

Provenance

Where this comes from

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