Observed topology

AS5583 Orange S.A.

Unclassified RIPE

Upstreams 0 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 25

Adjacent (IPv6) 9

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

Transit

Upstream networks

inferred

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

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS51964	ORANGE BUSINESS SERVICES U.S. Inc.	Unclassified	IPv4 IPv6	2,317

Adjacency

Adjacent networks

All 27

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

AS	Network	Type	Families	Paths seen
AS51964	ORANGE BUSINESS SERVICES U.S. Inc.	Unclassified	IPv4 IPv6	2,809
AS5511	Orange S.A.	Transit	IPv4 IPv6	1,801
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	371
AS33891	Core-Backbone GmbH	Hosting	IPv4	55
AS37721	Virtual Technologies & Solutions	Residential	IPv4 IPv6	52
AS24482	SG.GS	Hosting	IPv4 IPv6	50
AS42708	Glesys AB	Unclassified	IPv4 IPv6	50
AS3333	Reseaux IP Europeens Network Coordination Centre (RIPE NCC)	Unclassified	IPv4 IPv6	46
AS12552	GlobalConnect AB	Unclassified	IPv4	42
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	40

All 27 adjacent →

Provenance

Where this comes from

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