asn.dev

Observed topology

AS56038 RACKCORP-AP - RackCorp

Hosting APNIC

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

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS56038: 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
AS4826Vocus Connect International BackboneUnclassifiedIPv4 IPv6675
AS6939Hurricane Electric LLCTransitIPv4245
AS9507NextHop Pty LtdUnclassifiedIPv4122
AS58430TCC Technology Co., Ltd.UnclassifiedIPv4107
AS8449"ElCat" Ltd.UnclassifiedIPv499
AS3223Voxility LLPHostingIPv484
AS9340INDO Internet, PTResidentialIPv466
AS18059DTPNET NAPHostingIPv465
AS45204GEMNET LLCUnclassifiedIPv459
AS56301National Data Center buildingUnclassifiedIPv459

All 18 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS138466DataMossa Co., Ltd.UnclassifiedIPv4245
AS133050CNCNA Pty LtdUnclassifiedIPv4192

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS4826Vocus Connect International BackboneUnclassifiedIPv4 IPv6956
AS6939Hurricane Electric LLCTransitIPv4347
AS138466DataMossa Co., Ltd.UnclassifiedIPv4291
AS9507NextHop Pty LtdUnclassifiedIPv4200
AS133050CNCNA Pty LtdUnclassifiedIPv4192
AS58430TCC Technology Co., Ltd.UnclassifiedIPv4107
AS3223Voxility LLPHostingIPv4102
AS8449"ElCat" Ltd.UnclassifiedIPv499
AS9340INDO Internet, PTResidentialIPv466
AS18059DTPNET NAPHostingIPv465

All 20 adjacent →

Provenance

Where this comes from

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