ResearchRouting table, RPKI, IRR & looking glass

AS40518

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

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

Who holds AS40518

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

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

What AS40518 announces

Prefixes originated by AS40518 in the routing table our collectors hold (kept current as routes change), each checked against the RPKI (every ten minutes) and the IRR (daily).

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

Announced prefixes

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

IPv4 (4)

RPKI valid   RPKI invalid   no ROA covers it

Who AS40518 buys transit from

Inferred from the AS paths in the RouteViews tables and our own collectors’ feeds, refreshed every 4 hours, most-seen first. 1 upstream.

Who buys transit from AS40518

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

Routing registry objects

From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.

Route objects with origin AS40518: RADB 2

as-sets that list AS40518 (4)