bgpreport

Network · data from 2026-11-12

AS266288 AS266288 - LEANDRO BETOVO SANTOS DE ALBUQUERQUE-ME

Registry name: AS266288 - LEANDRO BETOVO SANTOS DE ALBUQUERQUE-ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266288, 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.79.112.0/22 No ROA Other IRR onlyRADB, TC 672 100% 66
2804:3578::/32 No ROA Other IRR onlyRADB, TC 635 100% 69
2804:3578::/33 No ROA Other IRR onlyRADB, TC 349 55% 65
2804:3578:8000::/33 No ROA Other IRR onlyRADB, TC 349 55% 65
170.79.112.0/23 No ROA Other IRR onlyRADB, TC 199 30% 56
170.79.114.0/23 No ROA Other IRR onlyTC 199 30% 56

AS-SET

AS266288 isn't in PeeringDB, where networks name their 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 20 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none170.79.112.0/22No ROA covers it. Add a ROA for AS266288, maxLength 22.672 of 673
Route object: RIR170.79.112.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:3578::/32No ROA covers it. Add a ROA for AS266288, maxLength 32.635 of 636
Route object: RIR2804:3578::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:3578::/33No ROA covers it. Add a ROA for AS266288, maxLength 33.349 of 636
Route object: RIR2804:3578::/33Route object only in RADB, TC. Add it in the RIR database for the space.349 of 636
ROA: none2804:3578:8000::/33No ROA covers it. Add a ROA for AS266288, maxLength 33.349 of 636
Route object: RIR2804:3578:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.349 of 636
ROA: none170.79.112.0/23No ROA covers it. Add a ROA for AS266288, maxLength 23.199 of 673
Route object: RIR170.79.112.0/23Route object only in RADB, TC. Add it in the RIR database for the space.199 of 673
ROA: none170.79.114.0/23No ROA covers it. Add a ROA for AS266288, maxLength 23.199 of 673
Route object: RIR170.79.114.0/23Route object only in TC. Add it in the RIR database for the space.199 of 673

Route objects not announced

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

170.79.112.0/24TCNo ROA
170.79.113.0/24TCNo ROA
170.79.114.0/24TCNo ROA
170.79.115.0/24TCNo ROA
2804:3578::/34TCNo ROA
2804:3578:4000::/34TCNo ROA
2804:3578:8000::/34TCNo ROA
2804:3578:c000::/34TCNo 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.