asn.dev

Observed topology

AS20776 OUTREMER-AS Outremer Telecom SAS

Unclassified APNIC

Upstreams 4 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 0
Upstream graph Who carries AS20776, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS20776 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv43,769
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv41,924
AS21502SFR SAResidentialIPv4763
AS15557SFR SAResidentialIPv4372

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS5377Marlink ASUnclassifiedIPv4116
AS21502SFR SAResidentialIPv459
AS328728Outremer Telecom Digital Solutions LtdUnclassifiedIPv439

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv44,618
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv42,340
AS21502SFR SAResidentialIPv41,821
AS15557SFR SAResidentialIPv4379
AS5377Marlink ASUnclassifiedIPv4175
AS328728Outremer Telecom Digital Solutions LtdUnclassifiedIPv439

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.