asn.dev

Observed topology

AS5416 BEYON B.S.C.

Unclassified RIPE

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

Transit

Upstream networks

All 34

Networks observed carrying traffic for AS5416: 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
AS15412Flag Telecom UK LimitedUnclassifiedIPv4 IPv618,475
AS8529Zain Omantel International FZ-LLCUnclassifiedIPv4 IPv612,772
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv4 IPv66,873
AS174Cogent Communications, LLCTransitIPv4 IPv66,009
AS8781Ooredoo Q.S.C.ResidentialIPv4 IPv65,588
AS48237Etihad Etisalat, a joint stock companyUnclassifiedIPv4 IPv63,367
AS39386Saudi Telecom Company JSCUnclassifiedIPv42,858
AS24482SG.GSHostingIPv4 IPv61,524
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv61,523
AS39801France IX Services SASUUnclassifiedIPv4 IPv61,485

All 34 upstreams →

Transit

Downstream networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS51375STC BAHRAIN B.S.C CLOSEDUnclassifiedIPv45,163
AS39273Kalaam Telecom Bahrain B.S.C.ResidentialIPv4 IPv62,293
AS35457Etisalcom Bahrain Company W.L.L.UnclassifiedIPv41,582
AS35729ViaCloud WLLUnclassifiedIPv4537
AS48109Information and eGovernment AuthorityUnclassifiedIPv4528
AS30882The Benefit Company B.S.C. (C)UnclassifiedIPv4198
AS138915Kaopu Cloud HK LimitedHostingIPv4 IPv6167
AS139341ACEHostingIPv4 IPv6102
AS14593Space Exploration Technologies CorporationResidentialIPv4 IPv6101
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv699

All 13 downstreams →

Adjacency

Adjacent networks

All 46

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

ASNetworkTypeFamiliesPaths seen
AS15412Flag Telecom UK LimitedUnclassifiedIPv4 IPv624,849
AS8529Zain Omantel International FZ-LLCUnclassifiedIPv4 IPv614,498
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv4 IPv68,457
AS8781Ooredoo Q.S.C.ResidentialIPv4 IPv67,339
AS174Cogent Communications, LLCTransitIPv4 IPv67,160
AS51375STC BAHRAIN B.S.C CLOSEDUnclassifiedIPv4 IPv66,428
AS39386Saudi Telecom Company JSCUnclassifiedIPv43,593
AS48237Etihad Etisalat, a joint stock companyUnclassifiedIPv4 IPv63,395
AS39273Kalaam Telecom Bahrain B.S.C.ResidentialIPv4 IPv62,545
AS35457Etisalcom Bahrain Company W.L.L.UnclassifiedIPv42,110

All 46 adjacent →

Provenance

Where this comes from

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