Network · data from 2026-11-12
AS38870 BGCP-AP - BGC Partners - APAC
Registry name: BGCP-AP - BGC Partners - APAC, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38870, 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.
| 148.106.72.0/24 | No ROA | Other IRR onlyRADB, RIPE-NONAUTH | 673 100% |
| 148.106.69.0/24 | No ROA | RIR databaseARIN, RADB, RIPE-NONAUTH | 673 100% |
| 148.106.70.0/24 | No ROA | RIR databaseARIN, RIPE-NONAUTH | 673 100% |
| 148.106.71.0/24 | No ROA | RIR databaseARIN, RADB, RIPE-NONAUTH | 673 100% |
| 148.106.81.0/24 | No ROA | RIR databaseARIN, RIPE-NONAUTH | 673 100% |
| 148.106.82.0/24 | No ROA | RIR databaseARIN, RIPE-NONAUTH | 673 100% |
| 148.106.83.0/24 | No ROA | RIR databaseARIN, RIPE-NONAUTH | 673 100% |
| 148.106.84.0/24 | No ROA | RIR databaseARIN, RIPE-NONAUTH | 673 100% |
| 148.106.93.0/24 | No ROA | RIR databaseARIN, RADB | 671 100% |
| 148.106.95.0/24 | No ROA | RIR databaseARIN, RADB, RIPE-NONAUTH | 671 100% |
AS-SET
AS38870 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 12 are in fix.csv.
- ROA: none10
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 148.106.72.0/24 | No ROA covers it. Add a ROA for AS38870, maxLength 24. |
| Route object: RIR | 148.106.72.0/24 | Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 148.106.69.0/24 | No ROA covers it. Add a ROA for AS38870, maxLength 24. |
| ROA: none | 148.106.70.0/24 | No ROA covers it. Add a ROA for AS38870, maxLength 24. |
| ROA: none | 148.106.71.0/24 | No ROA covers it. Add a ROA for AS38870, maxLength 24. |
| ROA: none | 148.106.81.0/24 | No ROA covers it. Add a ROA for AS38870, maxLength 24. |
| ROA: none | 148.106.82.0/24 | No ROA covers it. Add a ROA for AS38870, maxLength 24. |
| ROA: none | 148.106.83.0/24 | No ROA covers it. Add a ROA for AS38870, maxLength 24. |
| ROA: none | 148.106.84.0/24 | No ROA covers it. Add a ROA for AS38870, maxLength 24. |
| ROA: none | 148.106.93.0/24 | No ROA covers it. Add a ROA for AS38870, maxLength 24. |
| ROA: none | 148.106.95.0/24 | No ROA covers it. Add a ROA for AS38870, maxLength 24. |
Route objects not announced
Route objects with origin AS38870 whose prefix no peer sees AS38870 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 148.106.96.0/24 | RADB | 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.