Network · data from 2026-11-12
AS12536 Allegro Networks
Registry name: BSO Network Solutions SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS12536, 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.
| 212.121.32.0/19 | Valid | Other origin only | 527 78% |
AS-SET
AS12536'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 7 are in fix.csv.
- Route object: none1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 212.121.32.0/19 | Route objects for it name AS4455. Add a route object with origin AS12536 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS12536 whose prefix no peer sees AS12536 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 193.58.198.0/23 | RIPE | No ROA |
| 193.58.199.0/24 | RIPE | Invalid: origin |
| 212.121.32.0/23 | RIPE | Valid |
| 212.121.36.0/24 | RIPE | Valid |
| 212.121.40.0/24 | RIPE | Valid |
| 212.121.41.0/24 | 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.