asn.dev

Observed topology

AS203323 OPENSENT

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS203323: 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
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6113
AS6939Hurricane Electric LLCTransitIPv48
AS50304Blix Solutions ASUnclassifiedIPv42
AS12859BIT BVHostingIPv41
AS20764CJSC RASCOMUnclassifiedIPv41
AS24482SG.GSHostingIPv41
AS34927iFog GmbHHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207994Blockchain Creek B.V.HostingIPv464
AS53356Free Range Cloud Hosting Inc.HostingIPv413

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6195
AS207994Blockchain Creek B.V.HostingIPv478
AS53356Free Range Cloud Hosting Inc.HostingIPv426
AS50304Blix Solutions ASUnclassifiedIPv416
AS6939Hurricane Electric LLCTransitIPv48
AS24482SG.GSHostingIPv45
AS34927iFog GmbHHostingIPv45
AS12859BIT BVHostingIPv41
AS20764CJSC RASCOMUnclassifiedIPv41

Provenance

Where this comes from

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