Observed topology

AS271208 Stream Net

Unclassified APNIC

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS271208: 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
AS14840	BR.Digital Telecom	Unclassified	IPv4 IPv6	114
AS262532	NET ONDA SERVICOS DE INTERNET LTDA	Residential	IPv4 IPv6	90
AS274338	SuperNet Sistema De internet E Seguranca	Unclassified	IPv4	60
AS275674	A S GOMES TELECOM LTDA	Unclassified	IPv4	6

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS268812	BATISTA E SANTOS LTDA	Unclassified	IPv4 IPv6	87

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS14840	BR.Digital Telecom	Unclassified	IPv4 IPv6	201
AS262532	NET ONDA SERVICOS DE INTERNET LTDA	Residential	IPv4 IPv6	90
AS268812	BATISTA E SANTOS LTDA	Unclassified	IPv4 IPv6	87
AS274338	SuperNet Sistema De internet E Seguranca	Unclassified	IPv4	60
AS275674	A S GOMES TELECOM LTDA	Unclassified	IPv4	6

Provenance

Where this comes from

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