bgpreport

Network · data from 2026-11-12

AS51517 Oranjekoek

Registry name: AS-ORANJEKOEK Arend Brouwer, NL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51517, 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.
91.217.208.0/24 No ROA RIR databaseRIPE 672 100% 67
2a10:e300:8411::/48 Valid Nonecovered by 2a10:e300::/32 378 59% 65
103.251.156.0/22 Valid None 1 0%low visibility 1
103.251.156.0/24 Valid RIR databaseRIPE 672 100% 67
103.251.157.0/24 Valid RIR databaseRIPE 671 100% 67
103.251.159.0/24 Valid RIR databaseRIPE 671 100% 67
2a10:e300::/32 Valid RIR databaseRIPE 633 100% 67

AS-SET

AS51517'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 4 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none91.217.208.0/24No ROA covers it. Add a ROA for AS51517, maxLength 24.672 of 673
Route object: none2a10:e300:8411::/48No route object for it. A route object for 2a10:e300::/32 with origin AS51517 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51517 in the RIR database for the space.378 of 636
Route object: none103.251.156.0/22No route object for it. Add a route object with origin AS51517 in the RIR database for the space.1 of 673

Route objects not announced

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

103.251.158.0/24RIPEValid

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.