Network · data from 2026-11-12
AS396303 Nato Internet Service (Experimental)
Registry name: NATOLAB-LEGACY - Black Mesa Corporation, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS396303, 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.
| 2602:feda:f400::/40 | No ROA | RIR databaseARIN | 635 100% |
| 2602:feda:105::/48 | Valid | Other origin onlycovered by 2602:feda::/36 | 633 100% |
| 2602:feda:102::/48 | Valid | Other origin onlycovered by 2602:feda::/36 | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS396303: AS-NATOLAB. 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 (AS396303 isn't in the set, or no route object for AS396303 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 | AS396303 in it | Not covered |
|---|---|---|---|---|---|
| AS-NATOLAB | ALTDBlists itself further down1 member set in no database: AS-ROUTE48 | 688 | 37 | Yes | 0 |
| ARIN (also)1 member set in no database: AS-APERNET | 138 | 3 | 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 17 are in fix.csv.
- ROA: none1
- Route object: none2
- AS-SET: missing member1
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2602:feda:f400::/40 | No ROA covers it. Add a ROA for AS396303, maxLength 40. |
| Route object: none | 2602:feda:105::/48 | Route objects for it name AS38008. A route object for 2602:feda::/36 with origin AS396303 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396303 in the RIR database for the space. |
| Route object: none | 2602:feda:102::/48 | Route objects for it name AS38008. A route object for 2602:feda::/36 with origin AS396303 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396303 in the RIR database for the space. |
| AS-SET: missing member | AS-NATOLAB | AS-NATOLAB (ALTDB) lists AS-ROUTE48; no IRR database read has it. |
Route objects not announced
Route objects with origin AS396303 whose prefix no peer sees AS396303 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 141.193.21.0/24 | ARIN | Invalid: origin |
| 2406:4440:50::/44 | ALTDB | Valid |
| 2406:4440:60::/44 | ALTDB | Valid |
| 2406:4440:70::/44 | ALTDB | Valid |
| 2602:feda::/36 | ARIN | No ROA |
| 2602:feda:2::/48 | ARIN | No ROA |
| 2602:feda:4::/48 | ARIN | Invalid: origin |
| 2602:feda:a1::/48 | ARIN | No ROA |
| 2602:feda:a6::/48 | ARIN | No ROA |
| 2602:feda:e000::/36 | ARIN | No ROA |
| 2602:feda:f0d0::/44 | ALTDB | No ROA |
| 2602:feda:f0e0::/44 | ALTDB | No ROA |
| 2602:feda:f0f0::/44 | ALTDB | No ROA |
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.