Observed topology

AS263155 AS263155 - NG TELECOM

Unclassified LACNIC Cable/DSL/ISP

Upstreams 2 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263155: 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
AS53115	ISPX Solucoes em Telecomunicacoes SPE Ltda	Unclassified	IPv4 IPv6	365
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	261

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS262286	ALAN MARCELO DA SILVA LTDA	Residential	IPv4 IPv6	92
AS270495	JRD TELECOM LTDA	Unclassified	IPv4	59
AS262906	VOOA Internet para Sempre	Unclassified	IPv6	33
AS274363	BHT TELECOM LTDA	Unclassified	IPv6	25
AS267445	Romagnole Produtos Eletricos S.A.	Unclassified	IPv4	13

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS53115	ISPX Solucoes em Telecomunicacoes SPE Ltda	Unclassified	IPv4 IPv6	441
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	407
AS262286	ALAN MARCELO DA SILVA LTDA	Residential	IPv4 IPv6	92
AS270495	JRD TELECOM LTDA	Unclassified	IPv4	59
AS262906	VOOA Internet para Sempre	Unclassified	IPv6	33
AS274363	BHT TELECOM LTDA	Unclassified	IPv6	25
AS267445	Romagnole Produtos Eletricos S.A.	Unclassified	IPv4	13

Provenance

Where this comes from

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