asn.dev

Observed topology

AS55547 WOODSNET-PH Unit D,E,F,G 28th Floor

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS55547: 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
AS9304HGC Global Communications LimitedHostingIPv4 IPv66,359
AS4637Telstra GlobalUnclassifiedIPv4 IPv64,180
AS6939Hurricane Electric LLCTransitIPv43,103
AS3491PCCW Global (HK) Ltd.TransitIPv41,297
AS58453China Mobile International LimitedUnclassifiedIPv61,175
AS9505Taiwan Internet GatewayUnclassifiedIPv4 IPv6928
AS19551Incapsula IncHostingIPv4 IPv6705
AS32787Akamai Technologies, Inc.HostingIPv4477

Transit

Downstream networks

inferred

Networks for which AS55547 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS9304HGC Global Communications LimitedHostingIPv4 IPv66,359
AS4637Telstra GlobalUnclassifiedIPv4 IPv64,180
AS6939Hurricane Electric LLCTransitIPv43,103
AS3491PCCW Global (HK) Ltd.TransitIPv41,297
AS58453China Mobile International LimitedUnclassifiedIPv61,175
AS9505Taiwan Internet GatewayUnclassifiedIPv4 IPv6928
AS19551Incapsula IncHostingIPv4 IPv6705
AS32787Akamai Technologies, Inc.HostingIPv4477

Provenance

Where this comes from

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