bgpreport

Network · data from 2026-11-12

AS262634 LEMOS E MORAIS

Registry name: AS262634 - LEMOS E MORAIS LTDA., BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262634, 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:754::/33 No ROA Nonecovered by 2804:754::/32 636 100% 67
2804:754:8000::/33 No ROA Nonecovered by 2804:754::/32 636 100% 67
177.86.176.0/21 No ROA Other IRR onlyRADB, TC 672 100% 67
177.86.176.0/22 No ROA Other IRR onlyRADB 672 100% 67
177.86.180.0/22 No ROA Other IRR onlyRADB 672 100% 67
177.86.176.0/23 No ROA Other IRR onlyRADB 670 100% 67
177.86.178.0/23 No ROA Other IRR onlyRADB 670 100% 67
177.86.180.0/23 No ROA Other IRR onlyRADB 670 100% 67
177.86.182.0/23 No ROA Other IRR onlyRADB 670 100% 67
2804:754::/32 No ROA Other IRR onlyRADB, TC 636 100% 69

AS-SET

AS262634'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 21 are in fix.csv.

  • ROA: none10
  • Route object: none2
  • Route object: RIR8
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2804:754::/33No ROA covers it. Add a ROA for AS262634, maxLength 33.636 of 636
Route object: none2804:754::/33No route object for it. A route object for 2804:754::/32 with origin AS262634 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262634 in the RIR database for the space.636 of 636
ROA: none2804:754:8000::/33No ROA covers it. Add a ROA for AS262634, maxLength 33.636 of 636
Route object: none2804:754:8000::/33No route object for it. A route object for 2804:754::/32 with origin AS262634 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262634 in the RIR database for the space.636 of 636
ROA: none177.86.176.0/21No ROA covers it. Add a ROA for AS262634, maxLength 21.672 of 673
Route object: RIR177.86.176.0/21Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none177.86.176.0/22No ROA covers it. Add a ROA for AS262634, maxLength 22.672 of 673
Route object: RIR177.86.176.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.86.180.0/22No ROA covers it. Add a ROA for AS262634, maxLength 22.672 of 673
Route object: RIR177.86.180.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.86.176.0/23No ROA covers it. Add a ROA for AS262634, maxLength 23.670 of 673
Route object: RIR177.86.176.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.86.178.0/23No ROA covers it. Add a ROA for AS262634, maxLength 23.670 of 673
Route object: RIR177.86.178.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.86.180.0/23No ROA covers it. Add a ROA for AS262634, maxLength 23.670 of 673
Route object: RIR177.86.180.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.86.182.0/23No ROA covers it. Add a ROA for AS262634, maxLength 23.670 of 673
Route object: RIR177.86.182.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:754::/32No ROA covers it. Add a ROA for AS262634, maxLength 32.636 of 636
Route object: RIR2804:754::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

177.86.183.0/24TCNo ROA

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.