Skip to main content

AS266353

ASN266353

REDE BJNET TELECOMUNICAÇÕES LTDA-ME

Registry

Authoritative registration data

AS number
266353
Name
ASN266353
Organisation
REDE BJNET TELECOMUNICAÇÕES LTDA-ME
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

4

Total announced

11

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS266353
170.239.140.0/22 IPv4 /22 not checked
170.239.140.0/23 IPv4 /23 not checked
170.239.142.0/23 IPv4 /23 not checked
170.239.140.0/24 IPv4 /24 not checked
170.239.141.0/24 IPv4 /24 not checked
170.239.142.0/24 IPv4 /24 not checked
170.239.143.0/24 IPv4 /24 not checked
2804:3684::/32 IPv6 /32 RPKI valid
2804:3684:1472::/48 IPv6 /48 RPKI valid
2804:3684:cd00::/48 IPv6 /48 not checked
2804:3684:ce00::/48 IPv6 /48 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS266353
Address families
IX.br (PTT.br) Fortaleza: ATM/MPLA 5,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 5,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS266353 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS266353 in AS paths

Observed upstreams
Families
AS265269 ASN265269 1,242 4,817
v4 v6
AS61832 ASN61832 378 898
v4 v6
AS273744 ASN273744 274 368
v4
AS6939 HURRICANE 94 200
v4 v6
AS28368 ASN28368 10 11
v4 v6
AS6057 6057 2 8
v4 v6
AS137409 GSLNETWORKS-AS-AP 2 5
v4 v6
AS61626 ASN61626 1 3
v4 v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS266353 in AS paths

Observed downstreams
Families
AS268518 ASN268518 790 2,523
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

17 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.