ResearchRouting table, RPKI, IRR & looking glass

AS396260

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

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

Who holds AS396260

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

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

What AS396260 announces

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

The AS just before AS396260 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
RADBFONTAINEBLEAU-MIAMI-BEACH-ASMAINT-AS23089

Route objects with origin AS396260: RADB 2

as-sets that list AS396260 (4)