asn.dev

Observed topology

AS328950 Green Telecom Limited - Green Telecom Limited

Unclassified AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS328950: 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
AS30844Liquid Telecommunications LtdUnclassifiedIPv4 IPv6149
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv4106
AS329677Telxer Enterprise LimitedUnclassifiedIPv498

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS327885Viettel Tanzania PLCResidentialIPv4837
AS329529Kinetic Networks LimitedUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS327885Viettel Tanzania PLCResidentialIPv4837
AS58453China Mobile International LimitedUnclassifiedIPv4502
AS329677Telxer Enterprise LimitedUnclassifiedIPv4360
AS30844Liquid Telecommunications LtdUnclassifiedIPv4 IPv6283
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv4106
AS329529Kinetic Networks LimitedUnclassifiedIPv461

Provenance

Where this comes from

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