Network · data from 2026-11-12
AS263759 Celero Networks
Registry name: AS263759 - CELERO NETWORKS CORP, PA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263759, 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.229.134.0/24 | Valid | Nonecovered by 91.229.134.0/23 | 672 100% |
| 91.229.135.0/24 | Valid | Nonecovered by 91.229.134.0/23 | 672 100% |
| 38.250.10.0/24 | Valid | Nonecovered by 38.250.10.0/23 | 671 100% |
| 38.250.11.0/24 | Valid | Nonecovered by 38.250.10.0/23 | 671 100% |
| 190.122.188.0/24 | Valid | Nonecovered by 190.122.188.0/22 | 671 100% |
| 190.122.189.0/24 | Valid | Nonecovered by 190.122.188.0/22 | 671 100% |
| 190.122.190.0/24 | Valid | Nonecovered by 190.122.188.0/22 | 671 100% |
| 190.122.191.0/24 | Valid | Nonecovered by 190.122.188.0/22 | 671 100% |
| 185.91.206.0/23 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 2803:4300::/32 | Valid | RIR databaseLACNIC | 635 100% |
AS-SET
AS263759'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 11 are in fix.csv.
- Route object: none8
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 91.229.134.0/24 | No route object for it. A route object for 91.229.134.0/23 with origin AS263759 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263759 in the RIR database for the space. |
| Route object: none | 91.229.135.0/24 | No route object for it. A route object for 91.229.134.0/23 with origin AS263759 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263759 in the RIR database for the space. |
| Route object: none | 38.250.10.0/24 | No route object for it. A route object for 38.250.10.0/23 with origin AS263759 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263759 in the RIR database for the space. |
| Route object: none | 38.250.11.0/24 | No route object for it. A route object for 38.250.10.0/23 with origin AS263759 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263759 in the RIR database for the space. |
| Route object: none | 190.122.188.0/24 | No route object for it. A route object for 190.122.188.0/22 with origin AS263759 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263759 in the RIR database for the space. |
| Route object: none | 190.122.189.0/24 | No route object for it. A route object for 190.122.188.0/22 with origin AS263759 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263759 in the RIR database for the space. |
| Route object: none | 190.122.190.0/24 | No route object for it. A route object for 190.122.188.0/22 with origin AS263759 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263759 in the RIR database for the space. |
| Route object: none | 190.122.191.0/24 | No route object for it. A route object for 190.122.188.0/22 with origin AS263759 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263759 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263759 whose prefix no peer sees AS263759 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.250.10.0/23 | ARIN | Valid |
| 91.229.134.0/23 | RADB, RIPE | Valid |
| 190.122.188.0/22 | LACNIC, RADB | 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.