Network · data from 2026-11-12
AS203090 BitsFlowCloud
Registry name: BitsFlowCloud BITSFLOWCLOUD LTD, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS203090, 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.
| 2a0f:b240:10::/48 | Valid | None | 635 100% |
| 2a0f:b240:12::/48 | Valid | None | 635 100% |
| 216.23.84.0/23 | Valid | Nonecovered by 216.23.84.0/22 | 544 81% |
| 216.23.86.0/23 | Valid | Nonecovered by 216.23.84.0/22 | 544 81% |
| 216.23.112.0/23 | Valid | Nonecovered by 216.23.112.0/22 | 544 81% |
| 216.23.114.0/23 | Valid | Nonecovered by 216.23.112.0/22 | 544 81% |
| 216.23.84.0/24 | Valid | Nonecovered by 216.23.84.0/22 | 85 13% |
| 216.23.85.0/24 | Valid | Nonecovered by 216.23.84.0/22 | 85 13% |
| 216.23.86.0/24 | Valid | Nonecovered by 216.23.84.0/22 | 85 13% |
| 216.23.87.0/24 | Valid | Nonecovered by 216.23.84.0/22 | 85 13% |
| 216.23.112.0/24 | Valid | Nonecovered by 216.23.112.0/22 | 85 13% |
| 216.23.113.0/24 | Valid | Nonecovered by 216.23.112.0/22 | 85 13% |
| 216.23.114.0/24 | Valid | Nonecovered by 216.23.112.0/22 | 85 13% |
| 216.23.115.0/24 | Valid | Nonecovered by 216.23.112.0/22 | 85 13% |
| 91.233.10.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 216.23.94.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 216.23.95.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 108.186.9.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 108.186.105.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 108.186.129.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 108.186.216.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 212.60.151.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 212.60.153.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 217.216.140.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 217.216.141.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 217.216.143.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 217.216.170.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 108.165.23.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 82.39.250.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 169.40.110.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 169.40.123.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 216.23.84.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 216.23.112.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 216.23.92.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 216.23.93.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2a0f:9400:6909::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2602:fed2:708e::/48 | Valid | RIR databaseARIN | 634 100% |
| 2a0f:b240:19::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a12:4041:7::/48 | Valid | RIR databaseRIPE | 631 99% |
AS-SET
AS203090's PeeringDB record names no 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 24 are in fix.csv.
- Route object: none14
- Route object: RIR3
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a0f:b240:10::/48 | No route object for it. Add a route object with origin AS203090 in the RIR database for the space. |
| Route object: none | 2a0f:b240:12::/48 | No route object for it. Add a route object with origin AS203090 in the RIR database for the space. |
| Route object: none | 216.23.84.0/23 | No route object for it. A route object for 216.23.84.0/22 with origin AS203090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203090 in the RIR database for the space. |
| Route object: none | 216.23.86.0/23 | No route object for it. A route object for 216.23.84.0/22 with origin AS203090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203090 in the RIR database for the space. |
| Route object: none | 216.23.112.0/23 | No route object for it. A route object for 216.23.112.0/22 with origin AS203090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203090 in the RIR database for the space. |
| Route object: none | 216.23.114.0/23 | No route object for it. A route object for 216.23.112.0/22 with origin AS203090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203090 in the RIR database for the space. |
| Route object: none | 216.23.84.0/24 | No route object for it. A route object for 216.23.84.0/22 with origin AS203090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203090 in the RIR database for the space. |
| Route object: none | 216.23.85.0/24 | No route object for it. A route object for 216.23.84.0/22 with origin AS203090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203090 in the RIR database for the space. |
| Route object: none | 216.23.86.0/24 | No route object for it. A route object for 216.23.84.0/22 with origin AS203090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203090 in the RIR database for the space. |
| Route object: none | 216.23.87.0/24 | No route object for it. A route object for 216.23.84.0/22 with origin AS203090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203090 in the RIR database for the space. |
| Route object: none | 216.23.112.0/24 | No route object for it. A route object for 216.23.112.0/22 with origin AS203090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203090 in the RIR database for the space. |
| Route object: none | 216.23.113.0/24 | No route object for it. A route object for 216.23.112.0/22 with origin AS203090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203090 in the RIR database for the space. |
| Route object: none | 216.23.114.0/24 | No route object for it. A route object for 216.23.112.0/22 with origin AS203090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203090 in the RIR database for the space. |
| Route object: none | 216.23.115.0/24 | No route object for it. A route object for 216.23.112.0/22 with origin AS203090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203090 in the RIR database for the space. |
| Route object: RIR | 91.233.10.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 216.23.94.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 216.23.95.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS203090 whose prefix no peer sees AS203090 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.142.204.0/24 | ARIN | Valid |
| 87.85.140.0/24 | RIPE | Valid |
| 107.149.19.0/24 | ARIN, RADB | Valid |
| 108.186.209.0/24 | ARIN, RADB | Valid |
| 216.23.92.0/22 | RIPE | Valid |
| 2602:fd50:8006::/48 | ARIN | Valid |
| 2602:fed2:730b::/48 | ARIN | 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.