asn.dev

Observed topology

AS25250 GAMTEL-AS

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS25250: 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
AS174Cogent Communications, LLCTransitIPv41,164
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6245
AS37649SAGA AFRICA HOLDINGS LIMITEDResidentialIPv4114

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS328488DK Telecom LtdUnclassifiedIPv459
AS37552Comium Gambia Ltd.UnclassifiedIPv418
AS37503Unique Solutions Company LimitedUnclassifiedIPv46
AS37323Netpage Company LimitedUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv41,223
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6245
AS37649SAGA AFRICA HOLDINGS LIMITEDResidentialIPv4122
AS328488DK Telecom LtdUnclassifiedIPv459
AS8346IDDQD-ASResidentialIPv418
AS37552Comium Gambia Ltd.UnclassifiedIPv418
AS37503Unique Solutions Company LimitedUnclassifiedIPv46
AS37323Netpage Company LimitedUnclassifiedIPv42

Provenance

Where this comes from

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