asn.dev

Observed topology

AS48500 IRPNET-AS Irpinia Net-Com SRL

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48500: 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 LLCTransitIPv4350
AS174Cogent Communications, LLCTransitIPv498
AS24482SG.GSHostingIPv47
AS59919Brainbox S.r.l.ResidentialIPv47

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210869GLC NETCOM S.R.LUnclassifiedIPv4116
AS199039CAMPANIACOM SPAUnclassifiedIPv466
AS206952Flyfibra SRLUnclassifiedIPv414

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4526
AS210869GLC NETCOM S.R.LUnclassifiedIPv4116
AS174Cogent Communications, LLCTransitIPv4115
AS199039CAMPANIACOM SPAUnclassifiedIPv466
AS206952Flyfibra SRLUnclassifiedIPv414
AS59919Brainbox S.r.l.ResidentialIPv49
AS24482SG.GSHostingIPv48

Provenance

Where this comes from

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