ResearchRouting table, RPKI, IRR & looking glass

AS26016

No registry name is on file for AS26016. It originates 2 prefixes in the global routing table.

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

Who holds AS26016

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

AS number
AS26016
Handle
n/a
Organization
n/a
Country
n/a
ASPA
None published

What AS26016 announces

Prefixes originated by AS26016 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
0 0%
RPKI invalid
0
RPKI not found
2
ROAs naming AS26016
0
With an IRR route object
2 100%

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 AS26016 is reached through

The AS just before AS26016 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.

Route objects with origin AS26016: RADB 3

as-sets that list AS26016 (5)