bgpreport

Network · data from 2026-11-12

AS62415 ADF Agricultural Development Fund (gov)

Registry name: ADF Agricultural Development Fund (gov), SA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS62415, 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.
188.248.249.112/29 Invalid: origin None 1 0%low visibility 4
77.232.121.0/24 Valid RIR databaseRIPE 672 100% 67
82.197.52.0/24 Valid RIR databaseRIPE 671 100% 68

AS-SET

AS62415 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 2 are in fix.csv.

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin188.248.249.112/29ROAs covering it name AS19905, AS47794, AS48695, not AS62415. If AS62415 should announce it, add a ROA for AS62415.1 of 673
Route object: none188.248.249.112/29No route object for it. Add a route object with origin AS62415 in the RIR database for the space.1 of 673

Route objects not announced

Every route object with origin AS62415 is announced.

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.