bgpreport

Network · data from 2026-11-12

AS266092 RCOSTADONASCIMENTO

Registry name: AS266092 - R. COSTA DO NASCIMENTO, BR · PeeringDB

4IPv4 routes 0.0% RPKI valid · 100.0% with a route object
2IPv6 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
32Route objects not announced registered with origin AS266092, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266092, 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.5.108.0/24 No ROA Other IRR onlyRADB 672 100% 66
45.5.110.0/24 No ROA Other IRR onlyRADB 672 100% 66
45.5.109.0/24 No ROA Other IRR onlyRADB 669 99% 66
45.5.111.0/24 No ROA Other IRR onlyRADB 667 99% 67
2804:3a7c::/34 No ROA Other IRR onlyRADB 634 100% 67
2804:3a7c:8000::/34 No ROA Other IRR onlyRADB 634 100% 67

AS-SET

AS266092'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 44 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: none45.5.108.0/24No ROA covers it. Add a ROA for AS266092, maxLength 24.672 of 673
Route object: RIR45.5.108.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.5.110.0/24No ROA covers it. Add a ROA for AS266092, maxLength 24.672 of 673
Route object: RIR45.5.110.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.5.109.0/24No ROA covers it. Add a ROA for AS266092, maxLength 24.669 of 673
Route object: RIR45.5.109.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none45.5.111.0/24No ROA covers it. Add a ROA for AS266092, maxLength 24.667 of 673
Route object: RIR45.5.111.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none2804:3a7c::/34No ROA covers it. Add a ROA for AS266092, maxLength 34.634 of 636
Route object: RIR2804:3a7c::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:3a7c:8000::/34No ROA covers it. Add a ROA for AS266092, maxLength 34.634 of 636
Route object: RIR2804:3a7c:8000::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

45.5.108.0/22NTTCOM, RADB, TCNo ROA
45.5.108.0/23RADBNo ROA
45.5.110.0/23RADBNo ROA
2804:3a7c::/32NTTCOM, TCNo ROA
2804:3a7c::/33RADBNo ROA
2804:3a7c::/35RADBNo ROA
2804:3a7c::/36RADBNo ROA
2804:3a7c:1000::/36RADBNo ROA
2804:3a7c:2000::/35RADBNo ROA
2804:3a7c:2000::/36RADBNo ROA
2804:3a7c:3000::/36RADBNo ROA
2804:3a7c:4000::/34RADBNo ROA
2804:3a7c:4000::/35RADBNo ROA
2804:3a7c:4000::/36RADBNo ROA
2804:3a7c:5000::/36RADBNo ROA
2804:3a7c:6000::/35RADBNo ROA
2804:3a7c:6000::/36RADBNo ROA
2804:3a7c:7000::/36RADBNo ROA
2804:3a7c:8000::/33RADBNo ROA
2804:3a7c:8000::/35RADBNo ROA
2804:3a7c:8000::/36RADBNo ROA
2804:3a7c:9000::/36RADBNo ROA
2804:3a7c:a000::/35RADBNo ROA
2804:3a7c:a000::/36RADBNo ROA
2804:3a7c:b000::/36RADBNo ROA
2804:3a7c:c000::/34RADBNo ROA
2804:3a7c:c000::/35RADBNo ROA
2804:3a7c:c000::/36RADBNo ROA
2804:3a7c:d000::/36RADBNo ROA
2804:3a7c:e000::/35RADBNo ROA
2804:3a7c:e000::/36RADBNo ROA
2804:3a7c: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.