asn.dev

Observed topology

AS268655 SERGIO MURILO DOS SANTOS ME

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268655: 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
AS264531HET INTERNET LTDAUnclassifiedIPv4 IPv6297
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv4 IPv6293

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271301GLINK TELECOM LTDAUnclassifiedIPv4 IPv6154
AS271192Acess.Net Telecomunicacoes LTDAResidentialIPv4 IPv693
AS268314EWERTON DA SILVA LOPES TELECOMUNICACOESUnclassifiedIPv460
AS265335PLANETA NET TELECOMUnclassifiedIPv4 IPv64

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS264531HET INTERNET LTDAUnclassifiedIPv4 IPv6451
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv4 IPv6450
AS271301GLINK TELECOM LTDAUnclassifiedIPv4 IPv6154
AS271192Acess.Net Telecomunicacoes LTDAResidentialIPv4 IPv693
AS268314EWERTON DA SILVA LOPES TELECOMUNICACOESUnclassifiedIPv460
AS265335PLANETA NET TELECOMUnclassifiedIPv4 IPv64

Provenance

Where this comes from

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