Network · data from 2026-11-12
AS212217 bbonline BB-Online UK Ltd
Registry name: bbonline BB-Online UK Ltd, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS212217, 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.
| 91.238.194.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 2a13:e280:1::/48 | Valid | Other IRR onlyRADB | 633 100% |
| 81.30.104.0/24 | Valid | Other IRR onlyRADB | 550 82% |
| 46.253.129.0/24 | Valid | Other IRR onlyRADB | 364 54% |
| 185.206.123.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
AS-SET
AS212217 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: RIR4
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 91.238.194.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a13:e280:1::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 81.30.104.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 46.253.129.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS212217 whose prefix no peer sees AS212217 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a10:ca00:1::/48 | RADB, RIPE | Valid |
| 2a10:ca00:2::/48 | RADB | Valid |
| 2a10:ca00:3::/48 | RADB | Valid |
| 2a10:ca00:4::/48 | RADB | Valid |
| 2a11:60c0:1::/48 | 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.