Network · data from 2026-11-12
AS201188 BJTPARTNERS-AS BJT Partners SAS
Registry name: BJTPARTNERS-AS BJT Partners SAS, FR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201188, 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.
| 64.111.88.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 64.111.88.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 2a03:ba0::/64 | Valid | Nonecovered by 2a03:ba0::/32 | 42 7%low visibility |
| 45.151.184.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.16.110.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.63.92.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.63.92.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.63.93.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.63.94.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.151.184.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.151.186.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.151.185.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.63.16.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.63.18.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a03:ba0::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a0f:3500::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS201188 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 14 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR2
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.111.88.0/22 | No ROA covers it. Add a ROA for AS201188, maxLength 22. |
| Route object: RIR | 64.111.88.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 64.111.88.0/24 | No ROA covers it. Add a ROA for AS201188, maxLength 24. |
| Route object: RIR | 64.111.88.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 2a03:ba0::/64 | No route object for it. A route object for 2a03:ba0::/32 with origin AS201188 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS201188 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS201188 whose prefix no peer sees AS201188 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.151.187.0/24 | RIPE | Valid |
| 64.111.88.0/23 | RADB | No ROA |
| 64.111.89.0/24 | RADB | No ROA |
| 64.111.90.0/23 | RADB | No ROA |
| 64.111.90.0/24 | RADB | No ROA |
| 64.111.91.0/24 | RADB | No ROA |
| 185.63.17.0/24 | RIPE | Valid |
| 185.63.95.0/24 | RIPE | Valid |
| 2a03:ba0::/32 | RIPE | Valid |
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.