asn.dev

Observed topology

AS25773 RADWARE-CLOUD-SERVICES

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS25773: 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
AS198949Radware LtdUnclassifiedIPv4 IPv64,863
AS1299Arelion Sweden ABTransitIPv4 IPv61,049
AS2914NTT America, Inc.TransitIPv4 IPv6638
AS23352DEFT.COMHostingIPv4 IPv6536
AS36351IBM CloudHostingIPv4 IPv6382
AS3491PCCW Global HK Ltd.TransitIPv4 IPv6145
AS3257GTT Communications Inc.TransitIPv470
AS6429Chile Internet S.A.UnclassifiedIPv634
AS24482SG.GSHostingIPv4 IPv64
AS55720Gigabit Hosting Sdn BhdHostingIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS48851Radware LtdUnclassifiedIPv4 IPv6173
AS198949Radware LtdUnclassifiedIPv434

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS198949Radware LtdUnclassifiedIPv4 IPv65,095
AS1299Arelion Sweden ABTransitIPv4 IPv61,049
AS2914NTT America, Inc.TransitIPv4 IPv6638
AS23352DEFT.COMHostingIPv4 IPv6536
AS36351IBM CloudHostingIPv4 IPv6382
AS48851Radware LtdUnclassifiedIPv4 IPv6173
AS3491PCCW Global HK Ltd.TransitIPv4 IPv6145
AS17408AboveNet Communications TaiwanUnclassifiedIPv4 IPv6124
AS6429Chile Internet S.A.UnclassifiedIPv4 IPv699
AS3257GTT Communications Inc.TransitIPv470

All 13 adjacent →

Provenance

Where this comes from

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