bgpreport

Network · data from 2026-11-12

AS266641 Lavrasnet Servicos de Provedor de Internet Ltda

Registry name: AS266641 - Lavrasnet Servicos de Provedor de Internet Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266641, 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:3f20:c000::/44 Valid Nonecovered by 2804:3f20:c000::/34 634 100% 67
160.238.180.0/23 Valid Other IRR onlyRADB, TC 672 100% 67
160.238.183.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
160.238.180.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
160.238.181.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
160.238.182.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
2804:3f20:c010::/44 Valid Other IRR onlyALTDB, RADB 634 100% 67
2804:3f20::/33 Valid Other IRR onlyRADB, TC 631 99% 68
2804:3f20::/34 Valid Other IRR onlyRADB, TC 631 99% 68
2804:3f20:4000::/34 Valid Other IRR onlyRADB, TC 631 99% 68
2804:3f20:8000::/34 Valid Other IRR onlyRADB, TC 631 99% 68

AS-SET

AS266641'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.

  • Route object: none1
  • Route object: RIR10
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none2804:3f20:c000::/44No route object for it. A route object for 2804:3f20:c000::/34 with origin AS266641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266641 in the RIR database for the space.634 of 636
Route object: RIR160.238.180.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR160.238.183.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR160.238.180.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR160.238.181.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR160.238.182.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:3f20:c010::/44Route object only in ALTDB, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:3f20::/33Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:3f20::/34Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:3f20:4000::/34Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:3f20:8000::/34Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

160.238.180.0/22RADB, TCValid
160.238.182.0/23RADB, TCValid
2804:3f20::/32RADB, TCValid
2804:3f20:8000::/33RADB, TCValid
2804:3f20:c000::/34RADB, TCValid

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.