asn.dev

Observed topology

AS37727 iNET Communications Limited - iNET Communications Limited

Unclassified AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS37727: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6928
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv6105
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv641
AS24482SG.GSHostingIPv4 IPv625
AS25091IP-Max SAUnclassifiedIPv617
AS33891Core-Backbone GmbHHostingIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS328770SIMBA MEDIA GHANA LIMITEDUnclassifiedIPv465
AS30997Ghana Internet Exchange AssociationUnclassifiedIPv446

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,022
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv6117
AS328770SIMBA MEDIA GHANA LIMITEDUnclassifiedIPv465
AS30997Ghana Internet Exchange AssociationUnclassifiedIPv446
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv644
AS24482SG.GSHostingIPv4 IPv626
AS25091IP-Max SAUnclassifiedIPv617
AS33891Core-Backbone GmbHHostingIPv49

Provenance

Where this comes from

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