asn.dev

Observed topology

AS25122 GULFSAT_COMMUNICATIONS-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS25122: 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
AS200612Gulf Bridge International Inc.UnclassifiedIPv4472
AS1299Arelion Sweden ABTransitIPv4 IPv6278
AS3225GULFNET COMMUNICATIONS CO. WLLResidentialIPv4265
AS21050Fast Communication Company LtdResidentialIPv4216
AS9155Quality Net General Trading & Contracting CompanyUnclassifiedIPv4209
AS6866Cyprus Telecommunications AuthorityResidentialIPv4189
AS3356Level 3 Parent, LLCTransitIPv4172
AS174Cogent Communications, LLCTransitIPv4 IPv6143

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS200612Gulf Bridge International Inc.UnclassifiedIPv4472
AS1299Arelion Sweden ABTransitIPv4 IPv6278
AS3225GULFNET COMMUNICATIONS CO. WLLResidentialIPv4265
AS21050Fast Communication Company LtdResidentialIPv4216
AS9155Quality Net General Trading & Contracting CompanyUnclassifiedIPv4209
AS6866Cyprus Telecommunications AuthorityResidentialIPv4189
AS3356Level 3 Parent, LLCTransitIPv4172
AS174Cogent Communications, LLCTransitIPv4 IPv6143

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.