Observed topology

AS43100 France IX Services SASU

Unclassified RIPE

Upstreams 0 carry this network

Downstreams 14 this network carries

Adjacent (IPv4) 13

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

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

All 14

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

AS	Network	Type	Families	Paths seen
AS5416	B.S.C.	Unclassified	IPv4	51
AS206874	Kyxar SARL	Residential	IPv4	8
AS199660	LTI NETWORKS SASU	Unclassified	IPv4	6
AS197036	Destiny France Entreprises SAS	Unclassified	IPv4	5
AS197696	Evolix SARL	Unclassified	IPv4	5
AS60983	LIOPEN SARL	Unclassified	IPv4	4
AS212895	Johannes Ernst	Unclassified	IPv6	4
AS28768	Alpilink Cloud S.A.S.	Hosting	IPv4	3
AS60595	Neptune Internet Services SAS	Unclassified	IPv4	3
AS199881	Association Auvergne Wireless	Unclassified	IPv4	2

All 14 downstreams →

Adjacency

Adjacent networks

All 16

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

AS	Network	Type	Families	Paths seen
AS37100	SEACOM Limited	Unclassified	IPv4	95
AS5416	B.S.C.	Unclassified	IPv4	51
AS199660	LTI NETWORKS SASU	Unclassified	IPv4	9
AS206874	Kyxar SARL	Residential	IPv4	8
AS6939	Hurricane Electric LLC	Transit	IPv6	5
AS197036	Destiny France Entreprises SAS	Unclassified	IPv4	5
AS197696	Evolix SARL	Unclassified	IPv4	5
AS28768	Alpilink Cloud S.A.S.	Hosting	IPv4	4
AS60983	LIOPEN SARL	Unclassified	IPv4	4
AS212895	Johannes Ernst	Unclassified	IPv6	4

All 16 adjacent →

Provenance

Where this comes from

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