asn.dev

Observed topology

AS203410 COLOBIX COLOBIX LTD

Unclassified RIPE

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

Transit

Upstream networks

All 37

Networks observed carrying traffic for AS203410: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6366
AS6939Hurricane Electric LLCTransitIPv4 IPv6162
AS3257GTT Communications Inc.TransitIPv4 IPv6138
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6100
AS5511Orange S.A.TransitIPv4 IPv645
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv625
AS3356Level 3 Parent, LLCTransitIPv424
AS9002RETN LimitedUnclassifiedIPv424
AS174Cogent Communications, LLCTransitIPv4 IPv622
AS1403EBOXResidentialIPv4 IPv614

All 37 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57242FOP Martyinchuk Aleksandr VasilevichUnclassifiedIPv4423

Adjacency

Adjacent networks

All 38

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6576
AS57242FOP Martyinchuk Aleksandr VasilevichUnclassifiedIPv4423
AS6939Hurricane Electric LLCTransitIPv4 IPv6200
AS3257GTT Communications Inc.TransitIPv4 IPv6181
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6158
AS5511Orange S.A.TransitIPv4 IPv657
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv640
AS3356Level 3 Parent, LLCTransitIPv424
AS9002RETN LimitedUnclassifiedIPv424
AS174Cogent Communications, LLCTransitIPv4 IPv622

All 38 adjacent →

Provenance

Where this comes from

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