asn.dev

Observed topology

AS49367 ASSEFLOW Seflow s.r.l.

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS49367: 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
AS31034Aruba S.p.A.HostingIPv4 IPv61,283
AS59796StormWall s.r.o.UnclassifiedIPv4116
AS6939Hurricane Electric LLCTransitIPv410
AS43298Storm Networks LLCUnclassifiedIPv44
AS8218Zayo Infrastructure France SAUnclassifiedIPv41
AS24482SG.GSHostingIPv41
AS31543myNet GmbHResidentialIPv41
AS59919Brainbox S.r.l.ResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS136258BrainStorm Network, IncUnclassifiedIPv4 IPv6212
AS196749BBANDA S.R.L.ResidentialIPv4 IPv6135
AS16004Milan Internet eXchangeUnclassifiedIPv478
AS9104Clio S.R.LResidentialIPv427

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS31034Aruba S.p.A.HostingIPv4 IPv61,829
AS196749BBANDA S.R.L.ResidentialIPv4 IPv6291
AS136258BrainStorm Network, IncUnclassifiedIPv4 IPv6212
AS59796StormWall s.r.o.UnclassifiedIPv4116
AS16004Milan Internet eXchangeUnclassifiedIPv478
AS6939Hurricane Electric LLCTransitIPv4 IPv668
AS9104Clio S.R.LResidentialIPv427
AS43298Storm Networks LLCUnclassifiedIPv44
AS8218Zayo Infrastructure France SAUnclassifiedIPv42
AS24482SG.GSHostingIPv42

All 12 adjacent →

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.