ResearchRouting table, RPKI, IRR & looking glass

AS39029 Redpill Linpro AS

AS39029 (REDPILL-LINPRO) is registered to Redpill Linpro AS in NO. It originates 4 prefixes in the global routing table.

3
IPv4 prefixes
1
IPv6 prefixes
9,472
IPv4 addresses
100%
RPKI valid

Who holds AS39029

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

AS number
AS39029
Handle
REDPILL-LINPRO
Organization
Redpill Linpro AS
Country
NO
ASPA
2 providers

What AS39029 announces

Prefixes originated by AS39029 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
1
IPv4 addresses
9,472 (37 /24s)
RPKI valid
4 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS39029
4
With an IRR route object
4 100%

Announced prefixes

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

IPv4 (3)
IPv6 (1)

RPKI valid   RPKI invalid   no ROA covers it

Who AS39029 is reached through

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

Provider authorization

AS39029 publishes an ASPA naming these providers. Check a path.

Routing registry objects

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