bgpreport

Network · data from 2026-11-12

AS200291 SAP_SE_WDF SAP SE

Registry name: SAP_SE_WDF SAP SE, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200291, 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.
193.16.224.0/23 Valid RIR databaseRIPE 672 100% 67
193.16.224.0/24 Valid RIR databaseRIPE 672 100% 67
193.16.225.0/24 Valid RIR databaseRIPE 672 100% 67
2a00:fe00:a400::/38 Valid RIR databaseRIPE 636 100% 67
2a00:fe00:a000::/38 Valid RIR databaseRIPE 635 100% 67
2a00:fe00:a800::/38 Valid RIR databaseRIPE 635 100% 67
2a00:fe00:a000::/36 Valid RIR databaseRIPE 628 99% 67
2a00:fe00:ac00::/38 Valid RIR databaseRIPE 627 99% 67

AS-SET

AS200291 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.

  • Route object: not announced8

Route objects not announced

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

193.16.224.0/22RIPEValid
193.16.226.0/24RIPEValid
193.16.227.0/24RIPEValid
2a00:fe00:a000::/46RIPEValid
2a00:fe00:a000::/48RIPEValid
2a00:fe00:a001::/48RIPEValid
2a00:fe00:a002::/48RIPEValid
2a00:fe00:a003::/48RIPEValid

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.