Skip to main content

AS53184

ASN53184

VERO S.A

Registry

Authoritative registration data

AS number
53184
Name
ASN53184
Organisation
VERO S.A
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

52

IPv6 prefixes

12

Total announced

64

Announced prefixes

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

Prefixes announced by AS53184
177.73.0.0/21 IPv4 /21 RPKI valid
177.74.120.0/21 IPv4 /21 not checked
138.118.84.0/22 IPv4 /22 RPKI valid
143.0.228.0/22 IPv4 /22 RPKI valid
168.0.148.0/22 IPv4 /22 RPKI valid
168.196.180.0/22 IPv4 /22 RPKI valid
177.129.24.0/22 IPv4 /22 not checked
177.155.248.0/22 IPv4 /22 not checked
177.39.64.0/22 IPv4 /22 RPKI valid
177.39.68.0/22 IPv4 /22 RPKI valid
177.73.0.0/22 IPv4 /22 RPKI valid
177.73.4.0/22 IPv4 /22 not checked
177.74.120.0/22 IPv4 /22 RPKI valid
177.74.124.0/22 IPv4 /22 not checked
177.87.32.0/22 IPv4 /22 not checked
186.232.48.0/22 IPv4 /22 not checked
186.232.52.0/22 IPv4 /22 RPKI valid
138.118.84.0/23 IPv4 /23 RPKI valid
138.118.86.0/23 IPv4 /23 not checked
143.0.228.0/23 IPv4 /23 RPKI valid
143.0.230.0/23 IPv4 /23 not checked
168.0.148.0/23 IPv4 /23 RPKI valid
168.0.150.0/23 IPv4 /23 not checked
168.196.180.0/23 IPv4 /23 RPKI valid
168.196.182.0/23 IPv4 /23 not checked
170.239.232.0/23 IPv4 /23 not checked
170.239.234.0/23 IPv4 /23 not checked
177.129.24.0/23 IPv4 /23 RPKI valid
177.129.26.0/23 IPv4 /23 RPKI valid
177.155.248.0/23 IPv4 /23 RPKI valid
177.155.250.0/23 IPv4 /23 not checked
177.39.64.0/23 IPv4 /23 not checked
177.39.66.0/23 IPv4 /23 RPKI valid
177.39.68.0/23 IPv4 /23 RPKI valid
177.39.70.0/23 IPv4 /23 RPKI valid
177.73.0.0/23 IPv4 /23 RPKI valid
177.73.4.0/23 IPv4 /23 RPKI valid
177.73.6.0/23 IPv4 /23 RPKI valid
177.74.120.0/23 IPv4 /23 RPKI valid
177.74.122.0/23 IPv4 /23 RPKI valid
177.74.124.0/23 IPv4 /23 RPKI valid
177.74.126.0/23 IPv4 /23 not checked
177.87.32.0/23 IPv4 /23 RPKI valid
177.87.34.0/23 IPv4 /23 not checked
186.232.48.0/23 IPv4 /23 not checked
186.232.50.0/23 IPv4 /23 RPKI valid
186.232.52.0/23 IPv4 /23 RPKI valid
186.232.54.0/23 IPv4 /23 not checked
170.239.235.0/24 IPv4 /24 RPKI valid
186.232.49.0/24 IPv4 /24 RPKI valid
186.232.50.0/24 IPv4 /24 RPKI valid
186.232.51.0/24 IPv4 /24 RPKI valid
2804:1c8::/32 IPv6 /32 RPKI valid
2804:2984::/32 IPv6 /32 RPKI valid
2804:1c8:100::/40 IPv6 /40 not checked
2804:2984:9000::/40 IPv6 /40 RPKI valid
2804:2984:9500::/40 IPv6 /40 RPKI valid
2804:2984:9700::/40 IPv6 /40 RPKI valid
2804:2984:9900::/40 IPv6 /40 RPKI valid
2804:1c8:100::/41 IPv6 /41 RPKI valid
2804:2984:500::/41 IPv6 /41 not checked
2804:2984:9100::/44 IPv6 /44 RPKI valid
2804:2984:9600::/44 IPv6 /44 RPKI valid
2804:2984:9800::/44 IPv6 /44 RPKI valid

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 AS53184
Address families
IX.br (PTT.br) Porto Alegre: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 20,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 AS53184 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS53184 in AS paths

Observed upstreams
Families
AS13786 SEABORN 685 4,901
v4 v6
AS28258 ASN28258 642 3,835
v4 v6
AS35280 F5 10 342
v4 v6
AS14840 ASN14840 5 225
v4 v6
AS137409 GSLNETWORKS-AS-AP 9 222
v4 v6
AS6939 HURRICANE 98 124
v6
AS6057 6057 6 110
v4 v6
AS61626 ASN61626 1 50
v4 v6
AS39120 CONVERGENZE-AS 1 29
v4
AS7195 7195 5 9
v4 v6
AS1031 PEER1-1031 2 5
v4
AS61568 ASN61568 2 5
v4

No rows match “”.

Showing – of

Observed downstreams

4 networks seen after AS53184 in AS paths

Observed downstreams
Families
AS28669 ASN28669 219 789
v4
AS53085 ASN53085 116 178
v4 v6
AS273474 ASN273474 10 15
v6
AS262794 ASN262794 8 11
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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