AS40513
No registry name is on file for AS40513. It originates 6 prefixes in the global routing table.
Who holds AS40513
Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.
What AS40513 announces
Prefixes originated by AS40513 in the routing table our collectors hold (kept current as routes change), each checked against the RPKI (every ten minutes) and the IRR (daily).
Announced prefixes
Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.
RPKI valid RPKI invalid no ROA covers it
Who AS40513 buys transit from
Inferred from the AS paths in the RouteViews tables and our own collectors’ feeds, refreshed every 4 hours, most-seen first. 7 upstreams.
Who buys transit from AS40513
None seen: AS40513 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 AS40513: RADB 16 · RIPE 5 · APNIC 3 · NTTCOM 2 · ARIN 1 · REACH 1