Observed topology
AS44444 Forcepoint-Cloud-AS Forcepoint UK Limited
Hosting RIPE
Transit
Upstream networks
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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 4,392 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,233 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,353 |
| AS13237 | euNetworks GmbH | Unclassified | IPv4 | 990 |
| AS4637 | Telstra Global | Unclassified | IPv4 | 546 |
| AS9583 | Sify Limited | Unclassified | IPv4 | 279 |
| AS21859 | Zenlayer Inc | Hosting | IPv4 | 277 |
| AS4755 | TATA Communications formerly VSNL is Leading ISP | Hosting | IPv4 | 252 |
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 | 194 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 157 |
Transit
Downstream networks
Networks for which AS44444 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS42465 | Forcepoint UK Limited | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS44444 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 4,398 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,250 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,361 |
| AS13237 | euNetworks GmbH | Unclassified | IPv4 | 990 |
| AS4637 | Telstra Global | Unclassified | IPv4 | 554 |
| AS9583 | Sify Limited | Unclassified | IPv4 | 279 |
| AS21859 | Zenlayer Inc | Hosting | IPv4 | 277 |
| AS4755 | TATA Communications formerly VSNL is Leading ISP | Hosting | IPv4 | 253 |
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 | 194 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 158 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-07 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.97M 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.