Observed topology

AS267973 G.V.R. TELECOMUNICACOES E SERVICOS LTDA - ME

Unclassified LACNIC

Upstreams 3 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267973: 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
AS7738	V tal	Unclassified	IPv4	90
AS8167	V tal	Residential	IPv4	78
AS53065	Opcao Telecom	Residential	IPv4	18

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS267621	IFIBER TELECOM	Unclassified	IPv4	218
AS266124	AtivaNet Telecom Ltda	Unclassified	IPv4	140
AS52821	Torres e Anselmi Ltda	Unclassified	IPv4	108
AS270271	High Speed Provedor de Internet Ltda	Unclassified	IPv4 IPv6	76

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS7738	V tal	Unclassified	IPv4	540
AS267621	IFIBER TELECOM	Unclassified	IPv4	218
AS8167	V tal	Residential	IPv4 IPv6	170
AS266124	AtivaNet Telecom Ltda	Unclassified	IPv4	140
AS52821	Torres e Anselmi Ltda	Unclassified	IPv4	108
AS270271	High Speed Provedor de Internet Ltda	Unclassified	IPv4 IPv6	76
AS53065	Opcao Telecom	Residential	IPv4	18

Provenance

Where this comes from

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