Network · data from 2026-11-12
AS26229 US-SEC - U.S. Securities & Exchange Commission
Registry name: US-SEC - U.S. Securities & Exchange Commission, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26229, 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.
| 162.138.192.0/20 | No ROA | None | 672 100% |
| 162.138.217.0/24 | No ROA | Nonecovered by 162.138.208.0/20 | 672 100% |
| 162.138.199.0/24 | No ROA | None | 670 100% |
| 2602:80b:8021::/48 | No ROA | Nonecovered by 2602:80b:8000::/40 | 633 100% |
| 162.138.208.0/20 | No ROA | Other IRR onlyNTTCOM | 670 100% |
| 162.138.16.0/24 | Valid | RIR databaseARIN | 672 100% |
| 162.138.32.0/24 | Valid | RIR databaseARIN | 672 100% |
| 162.138.182.0/24 | Valid | RIR databaseARIN | 672 100% |
| 162.138.194.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 162.138.196.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 162.138.197.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 162.138.198.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 162.138.200.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 162.138.201.0/24 | Valid | RIR databaseARIN | 672 100% |
| 162.138.202.0/24 | Valid | RIR databaseARIN | 672 100% |
| 162.138.203.0/24 | Valid | RIR databaseARIN | 672 100% |
| 162.138.204.0/24 | Valid | RIR databaseARIN | 672 100% |
| 162.138.205.0/24 | Valid | RIR databaseARIN | 672 100% |
| 162.138.206.0/24 | Valid | RIR databaseARIN | 672 100% |
| 162.138.207.0/24 | Valid | RIR databaseARIN | 672 100% |
| 162.138.208.0/24 | Valid | RIR databaseARIN | 672 100% |
| 162.138.209.0/24 | Valid | RIR databaseARIN | 672 100% |
| 162.138.210.0/24 | Valid | RIR databaseARIN | 672 100% |
| 162.138.211.0/24 | Valid | RIR databaseARIN | 672 100% |
| 162.138.212.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 162.138.213.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 162.138.214.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 162.138.215.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 162.138.216.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 162.138.222.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 162.138.192.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 162.138.195.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
AS-SET
AS26229 isn't in PeeringDB, where networks name their AS-SET.
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 19 are in fix.csv.
- ROA: none5
- Route object: none4
- Route object: RIR1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 162.138.192.0/20 | No ROA covers it. Add a ROA for AS26229, maxLength 20. |
| Route object: none | 162.138.192.0/20 | No route object for it. Add a route object with origin AS26229 in the RIR database for the space. |
| ROA: none | 162.138.217.0/24 | No ROA covers it. Add a ROA for AS26229, maxLength 24. |
| Route object: none | 162.138.217.0/24 | No route object for it. A route object for 162.138.208.0/20 with origin AS26229 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26229 in the RIR database for the space. |
| ROA: none | 162.138.199.0/24 | No ROA covers it. Add a ROA for AS26229, maxLength 24. |
| Route object: none | 162.138.199.0/24 | No route object for it. Add a route object with origin AS26229 in the RIR database for the space. |
| ROA: none | 2602:80b:8021::/48 | No ROA covers it. Add a ROA for AS26229, maxLength 48. |
| Route object: none | 2602:80b:8021::/48 | No route object for it. A route object for 2602:80b:8000::/40 with origin AS26229 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26229 in the RIR database for the space. |
| ROA: none | 162.138.208.0/20 | No ROA covers it. Add a ROA for AS26229, maxLength 20. |
| Route object: RIR | 162.138.208.0/20 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS26229 whose prefix no peer sees AS26229 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 162.138.16.0/23 | NTTCOM | No ROA |
| 162.138.128.0/22 | RADB | No ROA |
| 162.138.136.0/22 | RADB | No ROA |
| 162.138.202.0/23 | RADB | No ROA |
| 162.138.204.0/22 | RADB | No ROA |
| 162.138.208.0/22 | RADB | No ROA |
| 2602:80b:8000::/40 | ARIN | No ROA |
| 2602:80b:8011::/48 | RADB | No ROA |
| 2620::/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.