ResearchRouting table, RPKI, IRR & looking glass

AS202730 1. FSV Mainz 05 e.V.

AS202730 (mainz05-as) is registered to 1. FSV Mainz 05 e.V. in DE. It originates 1 prefix in the global routing table.

1
IPv4 prefixes
0
IPv6 prefixes
256
IPv4 addresses
100%
RPKI valid

Who holds AS202730

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

AS number
AS202730
Handle
mainz05-as
Organization
1. FSV Mainz 05 e.V.
Country
DE
ASPA
None published

What AS202730 announces

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

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

Announced prefixes

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

IPv4 (1)

RPKI valid   RPKI invalid   no ROA covers it

Who AS202730 is reached through

The AS just before AS202730 in the paths our looking glass collectors hold, for 1 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
RIPEmainz05-asRIPE-NCC-END-MNT, DE-MAINZ05-1-MNT

Route objects with origin AS202730: RIPE 2

as-sets that list AS202730 (4)