asn.dev

Observed topology

AS51790 SIEL SIEL, d.o.o.

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51790: 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 IPv6939
AS3356Level 3 Parent, LLCTransitIPv4 IPv6118
AS3212Telemach Slovenija d.o.o.ResidentialIPv4 IPv6117
AS3223Voxility LLPHostingIPv4116
AS36236NetActuate, IncHostingIPv4 IPv6103
AS174Cogent Communications, LLCTransitIPv475
AS44306OMONIA d.o.o.UnclassifiedIPv462
AS3303Swisscom (Schweiz) AGResidentialIPv419
AS5511Orange S.A.TransitIPv416

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS52035D1, informacijske tehnologije, d.o.o.UnclassifiedIPv4 IPv6101
AS44615PRO PLUS, d.o.o.UnclassifiedIPv466
AS49618ERA d.o.o.UnclassifiedIPv465
AS60114SIEL, d.o.o.UnclassifiedIPv636

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,149
AS3356Level 3 Parent, LLCTransitIPv4 IPv6135
AS3223Voxility LLPHostingIPv4124
AS3212Telemach Slovenija d.o.o.ResidentialIPv4 IPv6117
AS36236NetActuate, IncHostingIPv4 IPv6103
AS52035D1, informacijske tehnologije, d.o.o.UnclassifiedIPv4 IPv6101
AS174Cogent Communications, LLCTransitIPv491
AS44306OMONIA d.o.o.UnclassifiedIPv473
AS44615PRO PLUS, d.o.o.UnclassifiedIPv466
AS49618ERA d.o.o.UnclassifiedIPv465

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.