Observed topology

AS21003 GPTC-AS

Unclassified AFRINIC

Upstreams 1 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS21003: 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
AS37558	LIBYAN INTERNATIONAL TELECOMMUNICATION COMPANY	Residential	IPv4 IPv6	9,947

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS328073	Ion Telecom and Technology	Unclassified	IPv4	480
AS328611	Libyan Elite Company for Technical Solutions	Unclassified	IPv4	365
AS329678	High Speed Access Company for Telecommunication and Technology	Unclassified	IPv4	121
AS329435	Aljuman Aljadeed Limited Liability company	Unclassified	IPv4	61

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS37558	LIBYAN INTERNATIONAL TELECOMMUNICATION COMPANY	Residential	IPv4 IPv6	11,278
AS328073	Ion Telecom and Technology	Unclassified	IPv4	480
AS328611	Libyan Elite Company for Technical Solutions	Unclassified	IPv4	425
AS327752	RAWAFED LIBYA	Unclassified	IPv4	244
AS329678	High Speed Access Company for Telecommunication and Technology	Unclassified	IPv4	121
AS329435	Aljuman Aljadeed Limited Liability company	Unclassified	IPv4	61

Provenance

Where this comes from

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