Network · data from 2026-11-12
AS32130 BRIGHT-HORIZONS - Bright Horizons
Registry name: BRIGHT-HORIZONS - Bright Horizons, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS32130, 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.132.120.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 91.132.121.0/24 | No ROA | RIR databaseRADB, RIPE | 673 100% |
| 91.132.123.0/24 | No ROA | RIR databaseRADB, RIPE | 673 100% |
AS-SET
AS32130 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.
- ROA: none3
- Route object: RIR1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.132.120.0/24 | No ROA covers it. Add a ROA for AS32130, maxLength 24. |
| Route object: RIR | 91.132.120.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 91.132.121.0/24 | No ROA covers it. Add a ROA for AS32130, maxLength 24. |
| ROA: none | 91.132.123.0/24 | No ROA covers it. Add a ROA for AS32130, maxLength 24. |
Route objects not announced
Route objects with origin AS32130 whose prefix no peer sees AS32130 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 8.14.128.0/24 | RADB | No ROA |
| 8.14.129.0/24 | RADB | No ROA |
| 8.14.130.0/24 | RADB | No ROA |
| 8.14.131.0/24 | RADB | No ROA |
| 91.132.122.0/24 | RADB, 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.