ResearchRouting table, RPKI, IRR & looking glass

AS399920 Dayton

AS399920 (DAYNET-01) is registered to Dayton in US. It originates 2 prefixes in the global routing table.

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

Who holds AS399920

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

AS number
AS399920
Handle
DAYNET-01
Organization
Dayton
Country
US
ASPA
None published

What AS399920 announces

Prefixes originated by AS399920 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
1
IPv4 addresses
256 (1 /24s)
RPKI valid
0 0%
RPKI invalid
0
RPKI not found
2
ROAs naming AS399920
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 (1)
IPv6 (1)

RPKI valid   RPKI invalid   no ROA covers it

Who AS399920 is reached through

The AS just before AS399920 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 AS399920: RADB 3

as-sets that list AS399920 (3)