asn.dev

Observed topology

AS48851 radware Radware Ltd

Unclassified RIPE

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

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS48851: 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 IPv65,843
AS36351IBM CloudHostingIPv4 IPv6443
AS1299Arelion Sweden ABTransitIPv4 IPv6353
AS2914NTT America, Inc.TransitIPv4 IPv6192
AS25773RADWARE INC.UnclassifiedIPv4173
AS3356Level 3 Parent, LLCTransitIPv4150
AS36866Jamii Telecommunications LimitedUnclassifiedIPv4 IPv6147
AS1680Cellcom Fixed Line Communication L.PMobileIPv4126
AS45796UIH / BB ConnectUnclassifiedIPv4 IPv698
AS23352DEFT.COMHostingIPv4 IPv684

All 18 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS198949Radware LtdUnclassifiedIPv4 IPv65,843
AS36351IBM CloudHostingIPv4 IPv6443
AS1299Arelion Sweden ABTransitIPv4 IPv6353
AS2914NTT America, Inc.TransitIPv4 IPv6192
AS25773RADWARE INC.UnclassifiedIPv4173
AS3356Level 3 Parent, LLCTransitIPv4150
AS36866Jamii Telecommunications LimitedUnclassifiedIPv4 IPv6147
AS1680Cellcom Fixed Line Communication L.PMobileIPv4126
AS45796UIH / BB ConnectUnclassifiedIPv4 IPv698
AS23352DEFT.COMHostingIPv4 IPv684

All 18 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.