asn.dev

Observed topology

AS203380 DAInternationalGroup DA International Group Ltd.

Unclassified RIPE

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS203380: 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
AS9002RETN LimitedUnclassifiedIPv4812
AS6204INTERKVM HOST SRLUnclassifiedIPv4784
AS57344Telehouse ADResidentialIPv4 IPv6651
AS33891Core-Backbone GmbHHostingIPv4 IPv6568
AS26548PureVoltage Hosting Inc.HostingIPv4 IPv6300
AS6939Hurricane Electric LLCTransitIPv4248
AS62240Clouvider LimitedHostingIPv4240
AS60068Datacamp LimitedHostingIPv4 IPv6150
AS29802HIVELOCITY, Inc.HostingIPv4 IPv698
AS24482SG.GSHostingIPv438

All 16 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS211507Julian AchterUnclassifiedIPv4 IPv6156
AS40663IncogNet LLCVPNIPv4 IPv696

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4874
AS57344Telehouse ADResidentialIPv4 IPv6841
AS6204INTERKVM HOST SRLUnclassifiedIPv4784
AS33891Core-Backbone GmbHHostingIPv4 IPv6568
AS26548PureVoltage Hosting Inc.HostingIPv4 IPv6300
AS6939Hurricane Electric LLCTransitIPv4248
AS62240Clouvider LimitedHostingIPv4240
AS211507Julian AchterUnclassifiedIPv4 IPv6156
AS60068Datacamp LimitedHostingIPv4 IPv6150
AS29802HIVELOCITY, Inc.HostingIPv4 IPv698

All 18 adjacent →

Provenance

Where this comes from

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