bgpreport

Network · data from 2026-11-12

AS266441 LWNET COMERCIO E SERVICOS DE COMUNICACOES LTDA

Registry name: AS266441 - LWNET COMERCIO E SERVICOS DE COMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266441, 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.
170.82.30.0/23 No ROA Nonecovered by 170.82.28.0/22 670 100% 66
2804:37e0:8b00::/40 No ROA Nonecovered by 2804:37e0:8000::/36 632 99% 67
170.82.28.0/24 No ROA Other IRR onlyRADB 671 100% 67
170.82.29.0/24 No ROA Other IRR onlyRADB 670 100% 66
2804:37e0::/32 No ROA Other IRR onlyRADB, TC 633 100% 67
2804:37e0:8000::/36 No ROA Other IRR onlyRADB 632 99% 67

AS-SET

AS266441'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: none6
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none170.82.30.0/23No ROA covers it. Add a ROA for AS266441, maxLength 23.670 of 673
Route object: none170.82.30.0/23No route object for it. A route object for 170.82.28.0/22 with origin AS266441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266441 in the RIR database for the space.670 of 673
ROA: none2804:37e0:8b00::/40No ROA covers it. Add a ROA for AS266441, maxLength 40.632 of 636
Route object: none2804:37e0:8b00::/40No route object for it. A route object for 2804:37e0:8000::/36 with origin AS266441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266441 in the RIR database for the space.632 of 636
ROA: none170.82.28.0/24No ROA covers it. Add a ROA for AS266441, maxLength 24.671 of 673
Route object: RIR170.82.28.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none170.82.29.0/24No ROA covers it. Add a ROA for AS266441, maxLength 24.670 of 673
Route object: RIR170.82.29.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:37e0::/32No ROA covers it. Add a ROA for AS266441, maxLength 32.633 of 636
Route object: RIR2804:37e0::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
ROA: none2804:37e0:8000::/36No ROA covers it. Add a ROA for AS266441, maxLength 36.632 of 636
Route object: RIR2804:37e0:8000::/36Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

170.82.28.0/22RADB, TCNo ROA
170.82.30.0/24RADBNo ROA
170.82.31.0/24RADBNo ROA
2804:3a00::/32RADBNo 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.