bgpreport

Network · data from 2026-11-12

AS53141 Flys Interativa AS53141

Registry name: AS53141 - FLYS INTERATIVA LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53141, 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.
186.194.138.0/24 Valid Nonecovered by 186.194.136.0/22 670 100% 67
186.194.128.0/24 Valid Nonecovered by 186.194.128.0/21 669 99% 67
186.194.129.0/24 Valid Nonecovered by 186.194.128.0/21 669 99% 67
186.194.130.0/24 Valid Nonecovered by 186.194.128.0/21 669 99% 67
186.194.131.0/24 Valid Nonecovered by 186.194.128.0/21 669 99% 67
186.194.132.0/24 Valid Nonecovered by 186.194.128.0/21 669 99% 67
186.194.133.0/24 Valid Nonecovered by 186.194.128.0/21 669 99% 67
186.194.134.0/24 Valid Nonecovered by 186.194.128.0/21 669 99% 67
186.194.128.0/21 Valid Other IRR onlyRADB 672 100% 66
186.194.136.0/22 Valid Other IRR onlyRADB 670 100% 67
186.194.137.0/24 Valid Other IRR onlyRADB 670 100% 67
2804:7a9c::/32 Valid Other IRR onlyRADB 635 100% 67

AS-SET

AS53141's PeeringDB record names no 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 14 are in fix.csv.

  • Route object: none8
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none186.194.138.0/24No route object for it. A route object for 186.194.136.0/22 with origin AS53141 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53141 in the RIR database for the space.670 of 673
Route object: none186.194.128.0/24No route object for it. A route object for 186.194.128.0/21 with origin AS53141 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53141 in the RIR database for the space.669 of 673
Route object: none186.194.129.0/24No route object for it. A route object for 186.194.128.0/21 with origin AS53141 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53141 in the RIR database for the space.669 of 673
Route object: none186.194.130.0/24No route object for it. A route object for 186.194.128.0/21 with origin AS53141 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53141 in the RIR database for the space.669 of 673
Route object: none186.194.131.0/24No route object for it. A route object for 186.194.128.0/21 with origin AS53141 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53141 in the RIR database for the space.669 of 673
Route object: none186.194.132.0/24No route object for it. A route object for 186.194.128.0/21 with origin AS53141 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53141 in the RIR database for the space.669 of 673
Route object: none186.194.133.0/24No route object for it. A route object for 186.194.128.0/21 with origin AS53141 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53141 in the RIR database for the space.669 of 673
Route object: none186.194.134.0/24No route object for it. A route object for 186.194.128.0/21 with origin AS53141 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53141 in the RIR database for the space.669 of 673
Route object: RIR186.194.128.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.194.136.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR186.194.137.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:7a9c::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

186.194.135.0/24RADBValid
186.194.136.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.