bgpreport

Network · data from 2026-11-12

AS274665 AS274665 - LURSA341

Registry name: AS274665 - LURSA341, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274665, 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.
45.233.212.0/24 No ROA Other origin only 671 100% 67
2804:91cc::/32 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

AS274665 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 34 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced30
ChangePrefix or setDetailFull-table peers
ROA: none45.233.212.0/24No ROA covers it. Add a ROA for AS274665, maxLength 24.671 of 673
Route object: none45.233.212.0/24Route objects for it name AS267380. Add a route object with origin AS274665 in the RIR database for the space.671 of 673
ROA: none2804:91cc::/32No ROA covers it. Add a ROA for AS274665, maxLength 32.636 of 636
Route object: RIR2804:91cc::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

2804:91cc::/33RADBNo ROA
2804:91cc::/34RADBNo ROA
2804:91cc::/35RADBNo ROA
2804:91cc::/36RADBNo ROA
2804:91cc:1000::/36RADBNo ROA
2804:91cc:2000::/35RADBNo ROA
2804:91cc:2000::/36RADBNo ROA
2804:91cc:3000::/36RADBNo ROA
2804:91cc:4000::/34RADBNo ROA
2804:91cc:4000::/35RADBNo ROA
2804:91cc:4000::/36RADBNo ROA
2804:91cc:5000::/36RADBNo ROA
2804:91cc:6000::/35RADBNo ROA
2804:91cc:6000::/36RADBNo ROA
2804:91cc:7000::/36RADBNo ROA
2804:91cc:8000::/33RADBNo ROA
2804:91cc:8000::/34RADBNo ROA
2804:91cc:8000::/35RADBNo ROA
2804:91cc:8000::/36RADBNo ROA
2804:91cc:9000::/36RADBNo ROA
2804:91cc:a000::/35RADBNo ROA
2804:91cc:a000::/36RADBNo ROA
2804:91cc:b000::/36RADBNo ROA
2804:91cc:c000::/34RADBNo ROA
2804:91cc:c000::/35RADBNo ROA
2804:91cc:c000::/36RADBNo ROA
2804:91cc:d000::/36RADBNo ROA
2804:91cc:e000::/35RADBNo ROA
2804:91cc:e000::/36RADBNo ROA
2804:91cc:f000::/36RADBNo 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.