SUBNET.IM

AS266003Brasileiro Telecom

BrazilRegistryLACNIC

At a glance

IPv4 prefixes

14

IPv6 prefixes

23

IPv4 addresses

6.1k

IPv6 /64s

17.2B

Upstream graph

The networks AS266003 is seen behind, one and two hops out, drawn from real AS paths.

AS266003Toward the internet core
Upstream graph for AS266003: 12 neighbouring networks observed beyond it across 2 levels. The same networks are listed in the tables below.AS266003Brasileiro TelecomThis networkAS1000LINK AMERICANAS6939Hurricane Electri…AS14537Continent 8 LLCAS14840BR.DIGITALAS61618VIVA TECNOLOGIA T…AS6453TATA Communicatio…AS18106Viewqwest Pte LtdAS20130Depaul UniversityAS174Cogent Communicat…AS2914NTT America, Inc.AS3356Lumen (Level 3)AS263903INFORBARRA TELECOM

Networks observed one and two hops upstream of AS266003 in real AS paths. A thicker line means more vantage points saw that adjacency, so weight tracks how well attested it is — not how much traffic it carries. Adjacency is an observation; whether it is a transit purchase or a settlement-free peering is an inference, and is labelled as one wherever we show it.

Neighbouring networks

63

adjacent networks

Upstreams
914%
Peers
5181%
Downstreams
35%

Networks carrying this one's traffic toward the rest of the internet.

Upstreams of AS266003
NetworkCountryRelationshipPathsVantage pts
AS6939Hurricane Electric LLCUSPeer62432
AS14840BR.DIGITAL BRPeer33391
AS61618VIVA TECNOLOGIA TELECOM LTDABRPeer15647
AS14537Continent 8 LLCUSPeer234
AS1000LINK AMERICANUSPeer132
AS32590Valve CorporationUSPeer132
AS266213PLANETCLICK TELECOMUNICACOES LTDABRPeer132
AS137409GSL Networks Pty LTDAUPeer102
AS1031PEER 1031 LLCUSPeer41

Prefixes

All 37

The largest blocks AS266003 originates, widest first.

Largest prefixes originated by AS266003
PrefixAddressesVisibility
45.173.64.0/221k79/80
181.191.96.0/221k79/80
45.173.64.0/2351219/80
45.173.66.0/2351219/80
181.191.96.0/2351219/80
181.191.98.0/2351219/80
45.173.64.0/2425612/80
45.173.65.0/2425612/80
45.173.66.0/2425612/80
45.173.67.0/2425612/80

Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.