Network · data from 2026-11-12
AS202269 BitCommand BitCommand LLC
Registry name: BitCommand BitCommand LLC, AM · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS202269, 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.
| 195.248.240.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 195.248.241.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 195.248.243.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 185.208.173.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 194.26.195.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.106.206.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.110.188.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.110.189.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.110.190.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.208.172.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.239.1.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.248.242.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 2a0e:b084::/30 | Valid | RIR databaseRADB, RIPE | 635 100% |
| 2a14:7980::/32 | Valid | RIR databaseRADB, RIPE | 634 100% |
AS-SET
AS202269 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 9 are in fix.csv.
- Route object: RIR3
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 195.248.240.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 195.248.241.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 195.248.243.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202269 whose prefix no peer sees AS202269 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 95.128.197.0/24 | RIPE | No ROA |
| 185.110.188.0/32 | RIPE | Invalid: maxLength |
| 193.246.160.0/24 | RIPE | Invalid: origin |
| 195.248.240.0/23 | RIPE | No ROA |
| 217.197.97.0/24 | RIPE | Invalid: origin |
| 2a03:2dc0:3000::/36 | RIPE | 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.