asn.dev

Observed topology

AS264991 BOMFIM E SOUSA LTDA

Unclassified LACNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264991: 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
AS265269MEGA TELE INFORMATICAUnclassifiedIPv4309
AS6939Hurricane Electric LLCTransitIPv4 IPv681
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv434
AS24482SG.GSHostingIPv4 IPv68
AS35280F5 Networks SARLHostingIPv61
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268314EWERTON DA SILVA LOPES TELECOMUNICACOESUnclassifiedIPv4 IPv678
AS266273LINKMNET LTDAUnclassifiedIPv424
AS266361JARBAS PASCHOAL BRAZIL JUNIOR INFORMATICAUnclassifiedIPv410

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS265269MEGA TELE INFORMATICAUnclassifiedIPv4358
AS6939Hurricane Electric LLCTransitIPv4 IPv6115
AS268314EWERTON DA SILVA LOPES TELECOMUNICACOESUnclassifiedIPv4 IPv678
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv458
AS266273LINKMNET LTDAUnclassifiedIPv424
AS24482SG.GSHostingIPv4 IPv611
AS266361JARBAS PASCHOAL BRAZIL JUNIOR INFORMATICAUnclassifiedIPv410
AS35280F5 Networks SARLHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv62

Provenance

Where this comes from

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