Observed topology

AS264962 VOLTEC SERVICO DE AUTOMACAO TELECOM ...

Unclassified ARIN NSP

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264962: 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
AS263009	FORTE TELECOM LTDA.	Hosting	IPv4 IPv6	158
AS6939	Hurricane Electric LLC	Transit	IPv6	80
AS28210	GIGA MAIS FIBRA TELECOMUNICACOES S.A.	Residential	IPv4	43
AS24482	SG.GS	Hosting	IPv4 IPv6	9
AS37721	Virtual Technologies & Solutions	Residential	IPv4 IPv6	8
AS35280	F5 Networks SARL	Hosting	IPv4	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS61752	BATISTA PEREIRA INFORMATICA LTDA.	Residential	IPv4 IPv6	95

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS263009	FORTE TELECOM LTDA.	Hosting	IPv4 IPv6	200
AS61752	BATISTA PEREIRA INFORMATICA LTDA.	Residential	IPv4 IPv6	95
AS28210	GIGA MAIS FIBRA TELECOMUNICACOES S.A.	Residential	IPv4	90
AS6939	Hurricane Electric LLC	Transit	IPv6	80
AS24482	SG.GS	Hosting	IPv4 IPv6	12
AS37721	Virtual Technologies & Solutions	Residential	IPv4 IPv6	11
AS35280	F5 Networks SARL	Hosting	IPv4	3

Provenance

Where this comes from

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