Observed topology

AS28140 AS28140 - G2G INTERNET E SERVICOS DE TELECOM LTDA

Residential LACNIC Cable/DSL/ISP

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28140: 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
AS52571	G2G COM PROD ELETRO E SERV LTDA	Unclassified	IPv4 IPv6	853
AS268624	Gamers Club Ltda	Unclassified	IPv4 IPv6	533
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	331
AS52468	UFINET PANAMA S.A.	Unclassified	IPv4	72
AS24482	SG.GS	Hosting	IPv4 IPv6	27

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS266346	G2G NETWORKS SERVICOS DE COMUNICACAO	Unclassified	IPv4 IPv6	35

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS52571	G2G COM PROD ELETRO E SERV LTDA	Unclassified	IPv4 IPv6	853
AS268624	Gamers Club Ltda	Unclassified	IPv4 IPv6	533
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	352
AS52468	UFINET PANAMA S.A.	Unclassified	IPv4	86
AS266346	G2G NETWORKS SERVICOS DE COMUNICACAO	Unclassified	IPv4 IPv6	35
AS24482	SG.GS	Hosting	IPv4 IPv6	27

Provenance

Where this comes from

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