Observed topology

AS48813 ENIX-AS

Unclassified RIPE

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48813: 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
AS47160	MOJI SAS	Residential	IPv4 IPv6	168
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	94
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	59
AS204092	Association GRIFON	Unclassified	IPv4 IPv6	6
AS6696	VERIXI SA	Unclassified	IPv4	5
AS5511	Orange S.A.	Transit	IPv6	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS51888	Pilot Systems Consulting SARL	Unclassified	IPv4	60

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS47160	MOJI SAS	Residential	IPv4 IPv6	200
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	111
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	66
AS51888	Pilot Systems Consulting SARL	Unclassified	IPv4	60
AS204092	Association GRIFON	Unclassified	IPv4 IPv6	7
AS6696	VERIXI SA	Unclassified	IPv4	6
AS5511	Orange S.A.	Transit	IPv4 IPv6	4

Provenance

Where this comes from

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