ResearchRouting table, RPKI, IRR & looking glass

AS201851 PJSC "PIK SPECIALIZED DEVELOPER"

AS201851 (PIK-AS) is registered to PJSC "PIK SPECIALIZED DEVELOPER" in RU. It originates 2 prefixes in the global routing table.

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

Who holds AS201851

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

AS number
AS201851
Handle
PIK-AS
Organization
PJSC "PIK SPECIALIZED DEVELOPER"
Country
RU
ASPA
None published

What AS201851 announces

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

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

Announced prefixes

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

IPv4 (2)

RPKI valid   RPKI invalid   no ROA covers it

Who AS201851 is reached through

The AS just before AS201851 in the paths our looking glass collectors hold, for 2 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
RIPEPIK-ASRIPE-NCC-END-MNT, LIDERTELECOM-MNT

Route objects with origin AS201851: RIPE 2

as-sets that list AS201851 (9)