Network · data from 2026-11-12
AS15753 BP-US-2 BP International Ltd
Registry name: BP-US-2 BP International Ltd, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS15753, 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.
| 164.63.236.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 164.63.237.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 164.63.238.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 129.230.229.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 164.63.235.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 164.63.253.0/24 | No ROA | RIR databaseARIN, NTTCOM, RADB | 671 100% |
| 129.230.228.0/24 | No ROA | RIR databaseARIN | 2 0%low visibility |
| 129.230.253.0/24 | Valid | Nonecovered by 129.230.252.0/23 | 673 100% |
| 129.230.184.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 129.230.186.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 129.230.188.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 129.230.190.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 129.230.252.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 129.230.254.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
AS-SET
AS15753 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 26 are in fix.csv.
- ROA: none7
- Route object: none1
- Route object: RIR3
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 164.63.236.0/24 | No ROA covers it. Add a ROA for AS15753, maxLength 24. |
| Route object: RIR | 164.63.236.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 164.63.237.0/24 | No ROA covers it. Add a ROA for AS15753, maxLength 24. |
| Route object: RIR | 164.63.237.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 164.63.238.0/24 | No ROA covers it. Add a ROA for AS15753, maxLength 24. |
| Route object: RIR | 164.63.238.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 129.230.229.0/24 | No ROA covers it. Add a ROA for AS15753, maxLength 24. |
| ROA: none | 164.63.235.0/24 | No ROA covers it. Add a ROA for AS15753, maxLength 24. |
| ROA: none | 164.63.253.0/24 | No ROA covers it. Add a ROA for AS15753, maxLength 24. |
| ROA: none | 129.230.228.0/24 | No ROA covers it. Add a ROA for AS15753, maxLength 24. |
| Route object: none | 129.230.253.0/24 | No route object for it. A route object for 129.230.252.0/23 with origin AS15753 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15753 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS15753 whose prefix no peer sees AS15753 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 129.230.236.0/22 | ARIN | No ROA |
| 129.230.239.0/24 | RIPE-NONAUTH | No ROA |
| 149.177.128.0/22 | RIPE | Valid |
| 149.177.148.0/22 | RIPE | Valid |
| 149.177.152.0/22 | RIPE | Valid |
| 149.177.164.0/22 | RIPE | Valid |
| 149.177.176.0/21 | RIPE | Valid |
| 149.177.192.0/23 | RIPE | Valid |
| 149.177.194.0/23 | RIPE | Valid |
| 149.177.212.0/23 | RIPE | Valid |
| 149.177.214.0/23 | RIPE | Valid |
| 149.177.216.0/23 | RIPE | Valid |
| 149.177.218.0/23 | RIPE | Valid |
| 149.177.224.0/22 | RIPE | Valid |
| 149.177.228.0/22 | 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.