asn.dev

Observed topology

AS24916 ORBITAL-ASN County House, Station Approach

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS24916: 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, LLCTransitIPv4 IPv6278
AS2914NTT America, Inc.TransitIPv4 IPv6277
AS174Cogent Communications, LLCTransitIPv4 IPv6275
AS6939Hurricane Electric LLCTransitIPv4 IPv6224
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv676
AS50304Blix Solutions ASUnclassifiedIPv450
AS24482SG.GSHostingIPv4 IPv626
AS48185team.blue NVUnclassifiedIPv4 IPv626
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv626
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv626

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS24958CYBERFORT LIMITEDHostingIPv4708
AS49829ADM COMPUTER SERVICES LIMITEDUnclassifiedIPv4118

Adjacency

Adjacent networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS24958CYBERFORT LIMITEDHostingIPv4708
AS3356Level 3 Parent, LLCTransitIPv4 IPv6448
AS2914NTT America, Inc.TransitIPv4 IPv6434
AS174Cogent Communications, LLCTransitIPv4 IPv6406
AS6939Hurricane Electric LLCTransitIPv4 IPv6336
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6118
AS49829ADM COMPUTER SERVICES LIMITEDUnclassifiedIPv4118
AS50304Blix Solutions ASUnclassifiedIPv478
AS48185team.blue NVUnclassifiedIPv4 IPv641
AS3741Dimension DataUnclassifiedIPv440

Provenance

Where this comes from

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