Network · data from 2026-11-12
AS49952 Bluestone Bluestone AS
Registry name: Bluestone Bluestone AS, NO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49952, 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.213.224.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.197.208.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.197.209.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS49952 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 2 are in fix.csv.
- Route object: not announced2
Route objects not announced
Route objects with origin AS49952 whose prefix no peer sees AS49952 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a00:e4a0:100::/40 | RIPE | Valid |
| 2a00:e4a0:200:100::/56 | RIPE | 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.