asn.dev

Observed topology

AS203752 E-CAPS E-CAPS D.O.O

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS203752: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv636
AS1299Arelion Sweden ABTransitIPv4 IPv620
AS44306OMONIA d.o.o.UnclassifiedIPv4 IPv620
AS174Cogent Communications, LLCTransitIPv4 IPv611
AS15958CETIN Ltd. BelgradeUnclassifiedIPv4 IPv67
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv62
AS13030Init7 (Switzerland) Ltd.HostingIPv61

Transit

Downstream networks

inferred

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

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv636
AS1299Arelion Sweden ABTransitIPv4 IPv620
AS44306OMONIA d.o.o.UnclassifiedIPv4 IPv620
AS174Cogent Communications, LLCTransitIPv4 IPv611
AS15958CETIN Ltd. BelgradeUnclassifiedIPv4 IPv67
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv62
AS13030Init7 (Switzerland) Ltd.HostingIPv61

Provenance

Where this comes from

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