asn.dev

Observed topology

AS328479 BULSHO FIBER LINK LIMITED - BULSHO FIBER LINK LIMITED

Residential AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS328479: 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 LLCTransitIPv484
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv467
AS328977Wavex Internet Service Provider LTDResidentialIPv47
AS329562SERVERLINK SOLUTIONS LIMITEDUnclassifiedIPv47

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS329562SERVERLINK SOLUTIONS LIMITEDUnclassifiedIPv499

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv4134
AS6939Hurricane Electric LLCTransitIPv4114
AS329562SERVERLINK SOLUTIONS LIMITEDUnclassifiedIPv4106
AS328977Wavex Internet Service Provider LTDResidentialIPv49

Provenance

Where this comes from

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