asn.dev

Observed topology

AS37738 HOSTOWEB

Hosting AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS37738: 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, LLCTransitIPv4 IPv6432
AS6939Hurricane Electric LLCTransitIPv4 IPv6237
AS36925MEDITELECOMUnclassifiedIPv4 IPv6151
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv637
AS24482SG.GSHostingIPv4 IPv615
AS33891Core-Backbone GmbHHostingIPv412
AS37721Virtual Technologies & SolutionsResidentialIPv411
AS25091IP-Max SAUnclassifiedIPv64
AS4230CLARO S.A.ResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS136258BrainStorm Network, IncUnclassifiedIPv4 IPv691
AS138627Cato Networks, Inc.UnclassifiedIPv459

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6488
AS6939Hurricane Electric LLCTransitIPv4 IPv6261
AS36925MEDITELECOMUnclassifiedIPv4 IPv6210
AS136258BrainStorm Network, IncUnclassifiedIPv4 IPv691
AS138627Cato Networks, Inc.UnclassifiedIPv459
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv642
AS24482SG.GSHostingIPv4 IPv617
AS33891Core-Backbone GmbHHostingIPv413
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv613
AS25091IP-Max SAUnclassifiedIPv65

All 11 adjacent →

Provenance

Where this comes from

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