Network · data from 2026-11-12
AS1029 Nato Internet Service (APAC)
Registry name: BLACK-MESA-LMN - Black Mesa Corporation, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS1029, 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.
| 154.6.118.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 2602:feda:c0::/48 | No ROA | RIR databaseARIN | 634 100% |
| 2602:feda:c1::/48 | No ROA | RIR databaseARIN | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS1029: 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 (AS1029 isn't in the set, or no route object for AS1029 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 | AS1029 in it | Not covered |
|---|---|---|---|---|---|
| AS-NATOLAB | ALTDBlists itself further down1 member set in no database: AS-ROUTE48 | 688 | 37 | No | 3 |
| ARIN (also)1 member set in no database: AS-APERNET | 138 | 3 | No | 3 |
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 8 are in fix.csv.
- ROA: none3
- Route object: RIR1
- AS-SET: own ASN1
- AS-SET: missing member1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 154.6.118.0/24 | No ROA covers it. Add a ROA for AS1029, maxLength 24. |
| Route object: RIR | 154.6.118.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2602:feda:c0::/48 | No ROA covers it. Add a ROA for AS1029, maxLength 48. |
| ROA: none | 2602:feda:c1::/48 | No ROA covers it. Add a ROA for AS1029, maxLength 48. |
| AS-SET: own ASN | AS-NATOLAB | AS1029 isn't in AS-NATOLAB (ALTDB) once expanded. Add AS1029 to it. |
| 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 AS1029 whose prefix no peer sees AS1029 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2602:feda:c2::/48 | ARIN | No ROA |
| 2602:feda:c3::/48 | ARIN | 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.