asn.dev

Observed topology

AS44444 Forcepoint-Cloud-AS Forcepoint UK Limited

Hosting RIPE NSP

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

Transit

Upstream networks

All 41

Networks observed carrying traffic for AS44444: 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, LLCTransitIPv44,471
AS1299Arelion Sweden ABTransitIPv4 IPv62,208
AS6939Hurricane Electric LLCTransitIPv4 IPv61,340
AS13237euNetworks GmbHUnclassifiedIPv41,043
AS4637Telstra GlobalUnclassifiedIPv4570
AS9583Sify LimitedUnclassifiedIPv4279
AS21859Zenlayer IncHostingIPv4279
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4261
AS7195EDGEUNO S.A.SUnclassifiedIPv4194
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4163

All 41 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS42465Forcepoint UK LimitedUnclassifiedIPv460

Adjacency

Adjacent networks

All 44

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv44,477
AS1299Arelion Sweden ABTransitIPv4 IPv62,225
AS6939Hurricane Electric LLCTransitIPv4 IPv61,348
AS13237euNetworks GmbHUnclassifiedIPv41,043
AS4637Telstra GlobalUnclassifiedIPv4579
AS9583Sify LimitedUnclassifiedIPv4279
AS21859Zenlayer IncHostingIPv4279
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4262
AS7195EDGEUNO S.A.SUnclassifiedIPv4194
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4163

All 44 adjacent →

Provenance

Where this comes from

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