asn.dev

Observed topology

AS37276 VOFFICE

Residential AFRINIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS37276: 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
AS37271Workonline Communications(Pty) LtdUnclassifiedIPv4 IPv61,408
AS6939Hurricane Electric LLCTransitIPv4321
AS3741Dimension DataUnclassifiedIPv432
AS37721Virtual Technologies & SolutionsResidentialIPv431

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS328917Sonic Computers & Wi-Fi ccUnclassifiedIPv4384
AS328359Gironet (PTY) LTDUnclassifiedIPv460
AS329237Snowvalley CommunicationsUnclassifiedIPv46

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS37271Workonline Communications(Pty) LtdUnclassifiedIPv4 IPv61,837
AS328917Sonic Computers & Wi-Fi ccUnclassifiedIPv4384
AS6939Hurricane Electric LLCTransitIPv4332
AS328359Gironet (PTY) LTDUnclassifiedIPv460
AS3741Dimension DataUnclassifiedIPv441
AS37721Virtual Technologies & SolutionsResidentialIPv432
AS329237Snowvalley CommunicationsUnclassifiedIPv46

Provenance

Where this comes from

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