bgpreport

Network · data from 2026-11-12

AS266177 Exon Technology

Registry name: AS266177 - Louvetel Comunicacao Comercial SCM Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266177, 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.
200.106.148.0/23 No ROA Nonecovered by 200.106.148.0/22 668 99% 67
200.106.149.0/24 No ROA Other origin onlycovered by 200.106.148.0/22 668 99% 67
200.106.150.0/23 No ROA Nonecovered by 200.106.148.0/22 668 99% 67
200.106.150.0/24 No ROA Other origin onlycovered by 200.106.148.0/22 668 99% 67
200.106.151.0/24 No ROA Other origin onlycovered by 200.106.148.0/22 667 99% 67
200.106.148.0/22 No ROA Other IRR onlyRADB, TC 668 99% 67
200.106.148.0/24 No ROA Other IRR onlyRADB 668 99% 67
2804:3be0::/32 No ROA Other IRR onlyRADB, TC 631 99% 67

AS-SET

AS266177'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 16 are in fix.csv.

  • ROA: none8
  • Route object: none5
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none200.106.148.0/23No ROA covers it. Add a ROA for AS266177, maxLength 23.668 of 673
Route object: none200.106.148.0/23No route object for it. A route object for 200.106.148.0/22 with origin AS266177 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266177 in the RIR database for the space.668 of 673
ROA: none200.106.149.0/24No ROA covers it. Add a ROA for AS266177, maxLength 24.668 of 673
Route object: none200.106.149.0/24Route objects for it name AS27990. A route object for 200.106.148.0/22 with origin AS266177 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266177 in the RIR database for the space.668 of 673
ROA: none200.106.150.0/23No ROA covers it. Add a ROA for AS266177, maxLength 23.668 of 673
Route object: none200.106.150.0/23No route object for it. A route object for 200.106.148.0/22 with origin AS266177 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266177 in the RIR database for the space.668 of 673
ROA: none200.106.150.0/24No ROA covers it. Add a ROA for AS266177, maxLength 24.668 of 673
Route object: none200.106.150.0/24Route objects for it name AS27990. A route object for 200.106.148.0/22 with origin AS266177 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266177 in the RIR database for the space.668 of 673
ROA: none200.106.151.0/24No ROA covers it. Add a ROA for AS266177, maxLength 24.667 of 673
Route object: none200.106.151.0/24Route objects for it name AS27990. A route object for 200.106.148.0/22 with origin AS266177 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266177 in the RIR database for the space.667 of 673
ROA: none200.106.148.0/22No ROA covers it. Add a ROA for AS266177, maxLength 22.668 of 673
Route object: RIR200.106.148.0/22Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none200.106.148.0/24No ROA covers it. Add a ROA for AS266177, maxLength 24.668 of 673
Route object: RIR200.106.148.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2804:3be0::/32No ROA covers it. Add a ROA for AS266177, maxLength 32.631 of 636
Route object: RIR2804:3be0::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636

Route objects not announced

Every route object with origin AS266177 is announced.

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.