Observed topology
AS136787 PACKETHUBSA-AS-AP - PacketHub S.A.
VPN APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS136787: 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 |
|---|---|---|---|---|
| AS60068 | Datacamp Limited | Hosting | IPv4 IPv6 | 38,402 |
| AS62240 | Clouvider Limited | Hosting | IPv4 | 4,353 |
| AS9009 | M247 Europe SRL | Hosting | IPv4 | 2,700 |
| AS25369 | Hydra Communications Ltd | Hosting | IPv4 | 580 |
| AS49453 | Global Layer B.V. | Hosting | IPv4 | 360 |
| AS49981 | WorldStream B.V. | Hosting | IPv4 | 300 |
| AS136557 | Host Universal Pty Ltd | Unclassified | IPv4 | 177 |
| AS6424 | EDGOO NETWORKS UNIPESSOAL LDA | Hosting | IPv4 | 115 |
| AS42831 | UK Dedicated Servers Limited | Hosting | IPv4 | 107 |
| AS35200 | TransitX Ltd | Unclassified | IPv4 | 82 |
Transit
Downstream networks
Networks for which AS136787 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS272096 | PACKETHUB S.A. | Unclassified | IPv4 | 57,544 |
Adjacency
Adjacent networks
Every AS seen directly next to AS136787 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS60068 | Datacamp Limited | Hosting | IPv4 IPv6 | 95,946 |
| AS272096 | PACKETHUB S.A. | Unclassified | IPv4 | 57,544 |
| AS62240 | Clouvider Limited | Hosting | IPv4 | 4,353 |
| AS9009 | M247 Europe SRL | Hosting | IPv4 | 2,700 |
| AS25369 | Hydra Communications Ltd | Hosting | IPv4 | 580 |
| AS49453 | Global Layer B.V. | Hosting | IPv4 | 360 |
| AS49981 | WorldStream B.V. | Hosting | IPv4 | 300 |
| AS136557 | Host Universal Pty Ltd | Unclassified | IPv4 | 177 |
| AS6424 | EDGOO NETWORKS UNIPESSOAL LDA | Hosting | IPv4 | 115 |
| AS42831 | UK Dedicated Servers Limited | Hosting | IPv4 | 107 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.