Observed topology

AS48294 CC-AS

Residential RIPE

Upstreams 19 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 20

Adjacent (IPv6) 0

Upstream graph Who carries AS48294, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS48294 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS48294: 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.

AS	Network	Type	Families	Paths seen
AS6461	Zayo Bandwidth	Transit	IPv4	423
AS6939	Hurricane Electric LLC	Transit	IPv4	140
AS3356	Level 3 Parent, LLC	Transit	IPv4	46
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	45
AS50304	Blix Solutions AS	Unclassified	IPv4	30
AS3741	Dimension Data	Unclassified	IPv4	15
AS12552	GlobalConnect AB	Unclassified	IPv4	15
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4	15
AS24482	SG.GS	Hosting	IPv4	15
AS31500	Global Network Management Inc	Unclassified	IPv4	15

All 19 upstreams →

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS211678	Michaelston y Fedw Internet CIC	Unclassified	IPv4	50

Adjacency

Adjacent networks

All 20

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

AS	Network	Type	Families	Paths seen
AS6461	Zayo Bandwidth	Transit	IPv4	451
AS6939	Hurricane Electric LLC	Transit	IPv4	158
AS211678	Michaelston y Fedw Internet CIC	Unclassified	IPv4	50
AS3356	Level 3 Parent, LLC	Transit	IPv4	46
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	45
AS50304	Blix Solutions AS	Unclassified	IPv4	30
AS24482	SG.GS	Hosting	IPv4	17
AS50300	CustodianDC Limited	Unclassified	IPv4	17
AS3741	Dimension Data	Unclassified	IPv4	15
AS12552	GlobalConnect AB	Unclassified	IPv4	15

All 20 adjacent →

Provenance

Where this comes from

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