bgpreport

Network · data from 2026-11-12

AS271661 AS271661 - WESLEY RAMOS DIAS

Registry name: AS271661 - WESLEY RAMOS DIAS, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271661, 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.

187.63.232.0/24 No ROA Nonecovered by 187.63.232.0/23 669 99% 67
187.63.233.0/24 No ROA Nonecovered by 187.63.232.0/23 669 99% 67
187.63.234.0/24 No ROA Nonecovered by 187.63.234.0/23 669 99% 67
187.63.235.0/24 No ROA Nonecovered by 187.63.234.0/23 669 99% 67
187.63.232.0/22 No ROA Other IRR onlyTC 669 99% 67
187.63.232.0/23 No ROA Other IRR onlyTC 669 99% 67
187.63.234.0/23 No ROA Other IRR onlyTC 669 99% 67
2804:7f04::/32 No ROA Other IRR onlyRADB, TC 635 100% 67

AS-SET

AS271661 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 18 are in fix.csv.

  • ROA: none8
  • Route object: none4
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none187.63.232.0/24No ROA covers it. Add a ROA for AS271661, maxLength 24.669 of 673
Route object: none187.63.232.0/24No route object for it. A route object for 187.63.232.0/23 with origin AS271661 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271661 in the RIR database for the space.669 of 673
ROA: none187.63.233.0/24No ROA covers it. Add a ROA for AS271661, maxLength 24.669 of 673
Route object: none187.63.233.0/24No route object for it. A route object for 187.63.232.0/23 with origin AS271661 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271661 in the RIR database for the space.669 of 673
ROA: none187.63.234.0/24No ROA covers it. Add a ROA for AS271661, maxLength 24.669 of 673
Route object: none187.63.234.0/24No route object for it. A route object for 187.63.234.0/23 with origin AS271661 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271661 in the RIR database for the space.669 of 673
ROA: none187.63.235.0/24No ROA covers it. Add a ROA for AS271661, maxLength 24.669 of 673
Route object: none187.63.235.0/24No route object for it. A route object for 187.63.234.0/23 with origin AS271661 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271661 in the RIR database for the space.669 of 673
ROA: none187.63.232.0/22No ROA covers it. Add a ROA for AS271661, maxLength 22.669 of 673
Route object: RIR187.63.232.0/22Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none187.63.232.0/23No ROA covers it. Add a ROA for AS271661, maxLength 23.669 of 673
Route object: RIR187.63.232.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none187.63.234.0/23No ROA covers it. Add a ROA for AS271661, maxLength 23.669 of 673
Route object: RIR187.63.234.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:7f04::/32No ROA covers it. Add a ROA for AS271661, maxLength 32.635 of 636
Route object: RIR2804:7f04::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

2804:7f04::/33RADBNo ROA
2804:7f04:8000::/33RADBNo 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.