Observed topology

AS268251 WORLD CONNECT TELECOMUNICACOES DO BRASIL EIRELI-ME

Unclassified LACNIC NSP

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 4

Upstream graph Who carries AS268251, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS268251 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268251: 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.

AS	Network	Type	Families	Paths seen
AS11432	Telecomunicacoes Ltda	Hosting	IPv4 IPv6	134
AS263966	ME	Residential	IPv4	60
AS274593	PROVEDOR DE INTERNET LTDA	Unclassified	IPv4	60
AS52468	PANAMA S.A.	Unclassified	IPv4 IPv6	40
AS6939	Hurricane Electric LLC	Transit	IPv6	15
AS24482	SG.GS	Hosting	IPv4 IPv6	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS267993	FIBRA SERVICOS DE COMUNICACAO MULTIMIDIA SCM	Residential	IPv4	32

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS11432	Telecomunicacoes Ltda	Hosting	IPv4 IPv6	156
AS263966	ME	Residential	IPv4	60
AS274593	PROVEDOR DE INTERNET LTDA	Unclassified	IPv4	60
AS52468	PANAMA S.A.	Unclassified	IPv4 IPv6	40
AS267993	FIBRA SERVICOS DE COMUNICACAO MULTIMIDIA SCM	Residential	IPv4	32
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	25
AS24482	SG.GS	Hosting	IPv4 IPv6	3

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-26 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.