Observed topology

AS60725 O3B-AS SES Networks - Internet Service Provider operating GEO and MEO satellite constellation

Unclassified RIPE Cable/DSL/ISP

Upstreams 4 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60725: 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
AS12684	SES ASTRA S.A.	Residential	IPv4	671
AS12956	TELEFONICA GLOBAL SOLUTIONS SL	Transit	IPv4	234
AS36149	Hawaiian Telcom Services Company, Inc.	Residential	IPv4	228
AS3549	Level 3 Parent, LLC	Transit	IPv4	32

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS12684	SES ASTRA S.A.	Residential	IPv4	278
AS327802	MILLICOM CHAD SA	Unclassified	IPv4	118
AS37460	Orange Centreafrique	Unclassified	IPv4	48

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12684	SES ASTRA S.A.	Residential	IPv4	1,156
AS36149	Hawaiian Telcom Services Company, Inc.	Residential	IPv4	459
AS12956	TELEFONICA GLOBAL SOLUTIONS SL	Transit	IPv4	293
AS327802	MILLICOM CHAD SA	Unclassified	IPv4	118
AS3549	Level 3 Parent, LLC	Transit	IPv4	61
AS37460	Orange Centreafrique	Unclassified	IPv4	48

Provenance

Where this comes from

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