asn.dev

Observed topology

AS136787 PACKETHUBSA-AS-AP - PacketHub S.A.

VPN APNIC

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

Transit

Upstream networks

All 16

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.

ASNetworkTypeFamiliesPaths seen
AS60068Datacamp LimitedHostingIPv4 IPv638,402
AS62240Clouvider LimitedHostingIPv44,353
AS9009M247 Europe SRLHostingIPv42,700
AS25369Hydra Communications LtdHostingIPv4580
AS49453Global Layer B.V.HostingIPv4360
AS49981WorldStream B.V.HostingIPv4300
AS136557Host Universal Pty LtdUnclassifiedIPv4177
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv4115
AS42831UK Dedicated Servers LimitedHostingIPv4107
AS35200TransitX LtdUnclassifiedIPv482

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS272096PACKETHUB S.A.UnclassifiedIPv457,544

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS60068Datacamp LimitedHostingIPv4 IPv695,946
AS272096PACKETHUB S.A.UnclassifiedIPv457,544
AS62240Clouvider LimitedHostingIPv44,353
AS9009M247 Europe SRLHostingIPv42,700
AS25369Hydra Communications LtdHostingIPv4580
AS49453Global Layer B.V.HostingIPv4360
AS49981WorldStream B.V.HostingIPv4300
AS136557Host Universal Pty LtdUnclassifiedIPv4177
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv4115
AS42831UK Dedicated Servers LimitedHostingIPv4107

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.