Network · data from 2026-11-12
AS395050 HCDSB - Halton Catholic District School Board
Registry name: HCDSB - Halton Catholic District School Board, CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS395050, 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.
| 209.250.162.0/24 | Valid | Other origin onlycovered by 209.250.160.0/19 | 670 100% |
| 209.250.163.0/24 | Valid | Other origin onlycovered by 209.250.160.0/19 | 670 100% |
| 209.250.170.0/24 | Valid | Other origin onlycovered by 209.250.160.0/19 | 670 100% |
| 209.250.178.0/24 | Valid | Other origin onlycovered by 209.250.160.0/19 | 670 100% |
| 209.250.160.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 209.250.161.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 209.250.173.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 209.250.190.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 209.250.191.0/24 | Valid | Other IRR onlyRADB | 670 100% |
AS-SET
AS395050 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 10 are in fix.csv.
- Route object: none4
- Route object: RIR5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 209.250.162.0/24 | Route objects for it name AS577. A route object for 209.250.160.0/19 with origin AS395050 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395050 in the RIR database for the space. |
| Route object: none | 209.250.163.0/24 | Route objects for it name AS577. A route object for 209.250.160.0/19 with origin AS395050 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395050 in the RIR database for the space. |
| Route object: none | 209.250.170.0/24 | Route objects for it name AS577. A route object for 209.250.160.0/19 with origin AS395050 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395050 in the RIR database for the space. |
| Route object: none | 209.250.178.0/24 | Route objects for it name AS577. A route object for 209.250.160.0/19 with origin AS395050 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395050 in the RIR database for the space. |
| Route object: RIR | 209.250.160.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 209.250.161.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 209.250.173.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 209.250.190.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 209.250.191.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS395050 whose prefix no peer sees AS395050 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 209.250.160.0/19 | ARIN | 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.