Network · data from 2026-11-12
AS893 Ninja-IX Foundation
Registry name: NINJA-IX-FOUNDATION-ASN - Ninja-IX Foundation, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS893, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 23.137.88.0/24 | Valid | RIR databaseARIN | 670 100% |
| 2001:470:3b6::/48 | Valid | RIR databaseARIN | 634 100% |
| 2602:fb61::/40 | Valid | RIR databaseARIN | 634 100% |
| 2602:fb61:10::/48 | Valid | RIR databaseARIN | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS893: ARIN::AS-NINJA-FOUNDATION. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS893 isn't in the set, or no route object for AS893 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS893 in it | Not covered |
|---|---|---|---|---|---|
| ARIN::AS-NINJA-FOUNDATION | ARINlists itself further down2 member sets in no database: AS-FROOT, AS-NINJA-CACHE-RIX | 20 | 11 | Yes | 0 |
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 2 are in fix.csv.
- AS-SET: missing member2
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: missing member | ARIN::AS-NINJA-FOUNDATION | AS-NINJA-FOUNDATION (ARIN) lists AS-FROOT; no IRR database read has it. |
| AS-SET: missing member | ARIN::AS-NINJA-FOUNDATION | AS-NINJA-FOUNDATION (ARIN) lists AS-NINJA-CACHE-RIX; no IRR database read has it. |
Route objects not announced
Every route object with origin AS893 is announced.
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.