asn.dev

Observed topology

AS61672 Entelvias provedor de internet ltda

Unclassified AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61672: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6187
AS262903Tubaron TelecomUnclassifiedIPv4 IPv6141
AS6939Hurricane Electric LLCTransitIPv4 IPv686
AS14840BR.Digital TelecomUnclassifiedIPv625
AS24482SG.GSHostingIPv4 IPv67
AS35280F5 Networks SARLHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263061PABLO P BORTOLINI MEUnclassifiedIPv427

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6187
AS262903Tubaron TelecomUnclassifiedIPv4 IPv6141
AS6939Hurricane Electric LLCTransitIPv4 IPv686
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv651
AS263061PABLO P BORTOLINI MEUnclassifiedIPv427
AS24482SG.GSHostingIPv4 IPv68
AS35280F5 Networks SARLHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44

Provenance

Where this comes from

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