asn.dev

Observed topology

AS10779 STEPBROBD - StepBroBD, Inc.

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS10779: 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
AS35661VIRTUA SYSTEMS SASUnclassifiedIPv4 IPv668
AS3204xTom OUHostingIPv4 IPv654
AS36236NetActuate, IncHostingIPv4 IPv641
AS20473The Constant Company, LLCHostingIPv4 IPv619
AS21700Neptune Networks, LLCUnclassifiedIPv4 IPv618
AS59105Home NOC Operators GroupUnclassifiedIPv4 IPv614
AS23961Misaka Network, Inc.UnclassifiedIPv66

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS18932StepBroBD, Inc.UnclassifiedIPv6192

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS18932StepBroBD, Inc.UnclassifiedIPv6192
AS36236NetActuate, IncHostingIPv4 IPv6101
AS35661VIRTUA SYSTEMS SASUnclassifiedIPv4 IPv692
AS21700Neptune Networks, LLCUnclassifiedIPv4 IPv666
AS3204xTom OUHostingIPv4 IPv654
AS20473The Constant Company, LLCHostingIPv4 IPv649
AS59105Home NOC Operators GroupUnclassifiedIPv4 IPv644
AS23961Misaka Network, Inc.UnclassifiedIPv66

Provenance

Where this comes from

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