Observed topology

AS2647 ORANGE-BUSINESS-NAM

Unclassified RIPE NSP

Upstreams 1 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 16

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS2647: 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
AS5511	Orange S.A.	Transit	IPv4	708

Transit

Downstream networks

inferred

Networks for which AS2647 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	4,589
AS26573	Luxoft USA Inc	Unclassified	IPv4	11
AS400692	BASF Corporation	Unclassified	IPv4	11

Adjacency

Adjacent networks

All 16

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

AS	Network	Type	Families	Paths seen
AS51964	ORANGE BUSINESS SERVICES U.S. Inc.	Unclassified	IPv4 IPv6	4,998
AS5511	Orange S.A.	Transit	IPv4 IPv6	2,898
AS6461	Zayo Bandwidth	Transit	IPv4 IPv6	1,451
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	832
AS22652	Videotron Ltee	Residential	IPv4 IPv6	124
AS37721	Virtual Technologies & Solutions	Residential	IPv4	71
AS293	ESnet	Unclassified	IPv4	69
AS24482	SG.GS	Hosting	IPv4	67
AS2497	Internet Initiative Japan Inc.	Unclassified	IPv4	65
AS394256	Tech Futures Interactive Inc.	Unclassified	IPv4	54

All 16 adjacent →

Provenance

Where this comes from

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