ResearchRouting table, RPKI, IRR & looking glass

AS393682 AIsleCom

AS393682 (AICASNREQ10232014) is registered to AIsleCom in GD. It originates 5 prefixes in the global routing table.

4
IPv4 prefixes
1
IPv6 prefixes
1,024
IPv4 addresses
100%
RPKI valid

Who holds AS393682

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

AS number
AS393682
Handle
AICASNREQ10232014
Organization
AIsleCom
Country
GD
ASPA
2 providers

What AS393682 announces

Prefixes originated by AS393682 in the RouteViews table (refreshed every four hours), each checked against the RPKI (every ten minutes) and the IRR (daily).

IPv4 prefixes
4
IPv6 prefixes
1
IPv4 addresses
1,024 (4 /24s)
RPKI valid
5 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS393682
2
With an IRR route object
1 20%

Announced prefixes

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

IPv4 (4)
IPv6 (1)

RPKI valid   RPKI invalid   no ROA covers it

Who AS393682 buys transit from

Inferred from the AS paths in the RouteViews tables, refreshed every 4 hours, most-seen first. 2 upstreams; those marked ASPA are also named in its ASPA.

Who buys transit from AS393682

None seen: AS393682 does not appear to provide transit to anyone.

Provider authorization

AS393682 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.

Sourceas-nameMaintained by
ARINAS393682-AICMNT-AIC-124

Route objects with origin AS393682: ARIN 2 · RADB 2

as-sets that list AS393682 (4)