asn.dev

Observed topology

AS45015 GENY-AS ************ EXPORTS ************

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45015: 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
AS39120Convergenze S.p.A.ResidentialIPv4206
AS174Cogent Communications, LLCTransitIPv484
AS41327Fiber Telecom S.p.A.ResidentialIPv456
AS6939Hurricane Electric LLCTransitIPv442
AS20912Giuliano Claudio Peritore trading as "Panservice s.a.s. di Cuseo Fabrizio & C."ResidentialIPv411
AS24482SG.GSHostingIPv47
AS59919Brainbox S.r.l.ResidentialIPv47

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205498Farecom S.R.L.UnclassifiedIPv4118

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS39120Convergenze S.p.A.ResidentialIPv4266
AS205498Farecom S.R.L.UnclassifiedIPv4118
AS174Cogent Communications, LLCTransitIPv4108
AS41327Fiber Telecom S.p.A.ResidentialIPv472
AS6939Hurricane Electric LLCTransitIPv454
AS20912Giuliano Claudio Peritore trading as "Panservice s.a.s. di Cuseo Fabrizio & C."ResidentialIPv417
AS24482SG.GSHostingIPv47
AS59919Brainbox S.r.l.ResidentialIPv47

Provenance

Where this comes from

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