Observed topology

AS270703 AS270703 - ALLTEC INTERNET

Unclassified LACNIC

Upstreams 4 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270703: 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
AS263384	WordNet Internet Banda Larga	Unclassified	IPv6	128
AS28283	Adylnet Telecom	Residential	IPv4 IPv6	69
AS265098	Oria Eliza Hugo Carrasco-ME	Unclassified	IPv6	16
AS271206	Ch Informatica Ltda	Unclassified	IPv4	11

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS274565	NET GRUPPO TELECOMUNICACAO LTDA	Unclassified	IPv6	99
AS265098	Oria Eliza Hugo Carrasco-ME	Unclassified	IPv4	18

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS28283	Adylnet Telecom	Residential	IPv4 IPv6	197
AS274565	NET GRUPPO TELECOMUNICACAO LTDA	Unclassified	IPv4 IPv6	140
AS263384	WordNet Internet Banda Larga	Unclassified	IPv6	128
AS271206	Ch Informatica Ltda	Unclassified	IPv4 IPv6	41
AS265098	Oria Eliza Hugo Carrasco-ME	Unclassified	IPv4 IPv6	34

Provenance

Where this comes from

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