Skip to main content

AS52545

ASN52545

BJ NET Provedor de Internet Ltda. - ME

Registry

Authoritative registration data

AS number
52545
Name
ASN52545
Organisation
BJ NET Provedor de Internet Ltda. - ME
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

14

IPv6 prefixes

10

Total announced

24

Announced prefixes

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

Prefixes announced by AS52545
131.72.48.0/22 IPv4 /22 RPKI valid
168.121.168.0/22 IPv4 /22 not checked
170.82.168.0/22 IPv4 /22 RPKI valid
179.107.80.0/22 IPv4 /22 not checked
131.72.48.0/23 IPv4 /23 not checked
131.72.50.0/23 IPv4 /23 not checked
168.121.168.0/23 IPv4 /23 RPKI valid
168.121.170.0/23 IPv4 /23 not checked
170.82.168.0/23 IPv4 /23 not checked
170.82.170.0/23 IPv4 /23 not checked
179.107.80.0/23 IPv4 /23 not checked
179.107.82.0/23 IPv4 /23 not checked
179.107.80.0/24 IPv4 /24 not checked
179.107.81.0/24 IPv4 /24 RPKI not found
2804:e1c::/32 IPv6 /32 not checked
2804:e1c:8000::/33 IPv6 /33 RPKI valid
2804:e1c::/33 IPv6 /33 RPKI valid
2804:e1c:4000::/34 IPv6 /34 RPKI valid
2804:e1c:8000::/34 IPv6 /34 RPKI valid
2804:e1c::/34 IPv6 /34 not checked
2804:e1c:c000::/34 IPv6 /34 not checked
2804:e1c:fb00::/40 IPv6 /40 not checked
2804:e1c:1::/48 IPv6 /48 RPKI valid
2804:e1c::/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 AS52545
Address families
IX.br (PTT.br) Curitiba: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Florianópolis: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Londrina: ATM/MPLA 5,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Porto Alegre: ATM/MPLA 5,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Rio de Janeiro: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 40,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 AS52545 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS52545 in AS paths

Observed upstreams
Families
AS2914 NTT-DATA-2914 173 1,369
v4 v6
AS6939 HURRICANE 180 1,092
v4 v6
AS53062 ASN53062 199 1,061
v4 v6
AS174 COGENT-174 35 328
v4 v6
AS16735 ASN16735 30 109
v4 v6
AS6057 6057 11 87
v4 v6
AS35280 F5 7 50
v4 v6
AS7195 7195 3 14
v4 v6
AS61626 ASN61626 2 5
v4 v6
AS1031 PEER1-1031 1 2
v4
AS61568 ASN61568 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS52545 in AS paths

Observed downstreams
Families
AS270504 ASN270504 271 696
v4 v6
AS272220 ASN272220 129 378
v6
AS267353 53 116
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

21 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.