ResearchRouting table, RPKI, IRR & looking glass

AS396861

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

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

Who holds AS396861

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

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

What AS396861 announces

Prefixes originated by AS396861 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 AS396861
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 AS396861 is reached through

The AS just before AS396861 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
RADBRoadrunnerMAINT-RR

Route objects with origin AS396861: RADB 2

as-sets that list AS396861 (3)