asn.dev

Observed topology

AS203273 NetCraftersOU NetCrafters OU

Unclassified Spamhaus ASN-DROP RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS203273: 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
AS30823aurologic GmbHHostingIPv410,510
AS6939Hurricane Electric LLCTransitIPv4 IPv62,492
AS31500Global Network Management IncUnclassifiedIPv4 IPv6861
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6783
AS207208MEVSPACE sp. z o.o.UnclassifiedIPv4 IPv6779
AS9002RETN LimitedUnclassifiedIPv4 IPv6467
AS199599Telecom-Birzha, LLCUnclassifiedIPv4 IPv6200
AS3356Level 3 Parent, LLCTransitIPv4112
AS47122CYBERFIRST LLCUnclassifiedIPv461
AS216246Aeza Group LLCUnclassifiedIPv445

All 13 upstreams →

Transit

Downstream networks

inferred

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

All 13

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

ASNetworkTypeFamiliesPaths seen
AS30823aurologic GmbHHostingIPv410,510
AS6939Hurricane Electric LLCTransitIPv4 IPv62,492
AS31500Global Network Management IncUnclassifiedIPv4 IPv6861
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6783
AS207208MEVSPACE sp. z o.o.UnclassifiedIPv4 IPv6779
AS9002RETN LimitedUnclassifiedIPv4 IPv6467
AS199599Telecom-Birzha, LLCUnclassifiedIPv4 IPv6200
AS3356Level 3 Parent, LLCTransitIPv4112
AS47122CYBERFIRST LLCUnclassifiedIPv461
AS216246Aeza Group LLCUnclassifiedIPv445

All 13 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.