Observed topology

AS263424 Fonelight Telecomunicacoes SA

Unclassified LACNIC

Upstreams 4 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263424: 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
AS61712	YUPNET TELECOMUNICACOES LTDA	Residential	IPv4	1,734
AS28306	Voluy Telecom Eireli	Unclassified	IPv4 IPv6	301
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	43
AS28202	MASTER S/A	Unclassified	IPv4	9

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS271444	PREFEITURA DE VARGINHA	Unclassified	IPv4	413
AS272570	ONOFRE DE PAIVA 56881606753	Unclassified	IPv6	17

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS61712	YUPNET TELECOMUNICACOES LTDA	Residential	IPv4	1,734
AS28306	Voluy Telecom Eireli	Unclassified	IPv4 IPv6	707
AS271444	PREFEITURA DE VARGINHA	Unclassified	IPv4	413
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	67
AS272570	ONOFRE DE PAIVA 56881606753	Unclassified	IPv6	17
AS28202	MASTER S/A	Unclassified	IPv4	9

Provenance

Where this comes from

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