ResearchRouting table, RPKI, IRR & looking glass

AS203080 SAP SE

AS203080 (SAP_SE_PRG) is registered to SAP SE in DE. It originates 3 prefixes in the global routing table.

3
IPv4 prefixes
0
IPv6 prefixes
512
IPv4 addresses
100%
RPKI valid

Who holds AS203080

Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.

AS number
AS203080
Handle
SAP_SE_PRG
Organization
SAP SE
Country
DE
ASPA
None published

What AS203080 announces

Prefixes originated by AS203080 in the RouteViews table (refreshed every four hours), each checked against the RPKI (every ten minutes) and the IRR (daily).

IPv4 prefixes
3
IPv6 prefixes
0
IPv4 addresses
512 (2 /24s)
RPKI valid
3 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS203080
1
With an IRR route object
3 100%

Announced prefixes

Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.

IPv4 (3)

RPKI valid   RPKI invalid   no ROA covers it

Who AS203080 is reached through

The AS just before AS203080 in the paths our looking glass collectors hold, for 3 of its prefixes. Usually a transit provider, sometimes a peer. The number is how many of those prefixes it was seen on.

Routing registry objects

From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.

Sourceas-nameMaintained by
RIPESAP_SE_PRGRIPE-NCC-END-MNT, SAP-MNT

Route objects with origin AS203080: RIPE 3

as-sets that list AS203080 (3)