bgpreport

Network · data from 2026-11-12

AS53190 AS53190 - VERO S.A

Registry name: AS53190 - VERO S.A, BR · not in PeeringDB

21IPv4 routes 100.0% RPKI valid · 85.7% with a route object
2IPv6 routes 100.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 5 with no route object for this origin
11Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS53190, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS53190, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

2804:21a4::/32 Valid None 631 99% 67
2804:21a4:1800::/37 Valid None 328 52% 65
138.36.48.0/23 Valid Nonecovered by 138.36.48.0/22 127 19% 44
138.36.50.0/23 Valid Nonecovered by 138.36.48.0/22 127 19% 44
138.36.50.0/24 Valid Nonecovered by 138.36.48.0/22 5 1%low visibility 3
138.36.48.0/22 Valid Other IRR onlyRADB 667 99% 67
186.232.112.0/21 Valid Other IRR onlyTC 667 99% 67
186.232.112.0/22 Valid Other IRR onlyRADB 667 99% 67
186.232.116.0/22 Valid Other IRR onlyRADB 667 99% 67
186.232.112.0/23 Valid Other IRR onlyRADB 127 19% 44
186.232.114.0/23 Valid Other IRR onlyRADB 127 19% 44
186.232.116.0/23 Valid Other IRR onlyRADB 127 19% 44
186.232.118.0/23 Valid Other IRR onlyRADB 127 19% 44
138.36.48.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
138.36.49.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
138.36.51.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
186.232.112.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
186.232.114.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
186.232.115.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
186.232.116.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
186.232.117.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
186.232.118.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
186.232.119.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3

AS-SET

AS53190 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 24 are in fix.csv.

  • Route object: none5
  • Route object: RIR18
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2804:21a4::/32No route object for it. Add a route object with origin AS53190 in the RIR database for the space.631 of 636
Route object: none2804:21a4:1800::/37No route object for it. Add a route object with origin AS53190 in the RIR database for the space.328 of 636
Route object: none138.36.48.0/23No route object for it. A route object for 138.36.48.0/22 with origin AS53190 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53190 in the RIR database for the space.127 of 673
Route object: none138.36.50.0/23No route object for it. A route object for 138.36.48.0/22 with origin AS53190 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53190 in the RIR database for the space.127 of 673
Route object: none138.36.50.0/24No route object for it. A route object for 138.36.48.0/22 with origin AS53190 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53190 in the RIR database for the space.5 of 673
Route object: RIR138.36.48.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.232.112.0/21Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR186.232.112.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.232.116.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.232.112.0/23Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR186.232.114.0/23Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR186.232.116.0/23Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR186.232.118.0/23Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR138.36.48.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR138.36.49.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR138.36.51.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR186.232.112.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR186.232.114.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR186.232.115.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR186.232.116.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR186.232.117.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR186.232.118.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR186.232.119.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673

Route objects not announced

Route objects with origin AS53190 whose prefix no peer sees AS53190 announce. Many are kept on purpose (backup routes, space announced only in some places).

186.232.113.0/24RADBValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.