asn.dev

Observed topology

AS61211 SETCOR SETCOR d.o.o.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61211: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6346
AS3223Voxility LLPHostingIPv475
AS174Cogent Communications, LLCTransitIPv467
AS6939Hurricane Electric LLCTransitIPv432
AS3303Swisscom (Schweiz) AGResidentialIPv46
AS33891Core-Backbone GmbHHostingIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS43804IMENIK d.o.oUnclassifiedIPv460
AS210190NetLogic d.o.o.UnclassifiedIPv4 IPv65
AS208983RTL Hrvatska d.o.o.UnclassifiedIPv44
AS34540mStart plus d.o.o.UnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6436
AS174Cogent Communications, LLCTransitIPv4 IPv6120
AS3223Voxility LLPHostingIPv475
AS34540mStart plus d.o.o.UnclassifiedIPv474
AS43804IMENIK d.o.oUnclassifiedIPv460
AS6939Hurricane Electric LLCTransitIPv432
AS3303Swisscom (Schweiz) AGResidentialIPv46
AS210190NetLogic d.o.o.UnclassifiedIPv4 IPv65
AS33891Core-Backbone GmbHHostingIPv44
AS208983RTL Hrvatska d.o.o.UnclassifiedIPv44

Provenance

Where this comes from

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