bgpreport

Network · data from 2026-11-12

AS274617 AS274617 - RAFAEL RIBEIRO DE SOUZA

Registry name: AS274617 - RAFAEL RIBEIRO DE SOUZA, BR · not in PeeringDB

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

Announced routes

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

2804:9114::/33 No ROA Nonecovered by 2804:9114::/32 631 99% 67
2804:9114:4000::/34 No ROA Other IRR onlyRADB 635 100% 67
38.19.104.0/24 Valid Nonecovered by 38.19.104.0/23 666 99% 67
38.19.105.0/24 Valid Nonecovered by 38.19.104.0/23 664 99% 67

AS-SET

AS274617 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 8 are in fix.csv.

  • ROA: none2
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:9114::/33No ROA covers it. Add a ROA for AS274617, maxLength 33.631 of 636
Route object: none2804:9114::/33No route object for it. A route object for 2804:9114::/32 with origin AS274617 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274617 in the RIR database for the space.631 of 636
ROA: none2804:9114:4000::/34No ROA covers it. Add a ROA for AS274617, maxLength 34.635 of 636
Route object: RIR2804:9114:4000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: none38.19.104.0/24No route object for it. A route object for 38.19.104.0/23 with origin AS274617 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274617 in the RIR database for the space.666 of 673
Route object: none38.19.105.0/24No route object for it. A route object for 38.19.104.0/23 with origin AS274617 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274617 in the RIR database for the space.664 of 673

Route objects not announced

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

38.19.104.0/23ARINValid
2804:9114::/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.