Network · data from 2026-11-12
AS40412 PAHOUSE - PA House of Representatives - Democratic Caucus
Registry name: PAHOUSE - PA House of Representatives - Democratic Caucus, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40412, 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.
| 23.134.225.0/24 | No ROA | Nonecovered by 23.134.224.0/23 | 673 100% |
| 63.88.36.0/22 | No ROA | None | 673 100% |
| 63.88.39.0/24 | No ROA | None | 673 100% |
| 63.88.36.0/24 | No ROA | None | 2 0%low visibility |
| 63.88.37.0/24 | No ROA | None | 2 0%low visibility |
| 63.88.38.0/24 | No ROA | None | 2 0%low visibility |
| 8.38.174.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 23.134.224.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 23.134.224.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS40412 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 20 are in fix.csv.
- ROA: none9
- Route object: none6
- Route object: RIR3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 23.134.225.0/24 | No ROA covers it. Add a ROA for AS40412, maxLength 24. |
| Route object: none | 23.134.225.0/24 | No route object for it. A route object for 23.134.224.0/23 with origin AS40412 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40412 in the RIR database for the space. |
| ROA: none | 63.88.36.0/22 | No ROA covers it. Add a ROA for AS40412, maxLength 22. |
| Route object: none | 63.88.36.0/22 | No route object for it. Add a route object with origin AS40412 in the RIR database for the space. |
| ROA: none | 63.88.39.0/24 | No ROA covers it. Add a ROA for AS40412, maxLength 24. |
| Route object: none | 63.88.39.0/24 | No route object for it. Add a route object with origin AS40412 in the RIR database for the space. |
| ROA: none | 63.88.36.0/24 | No ROA covers it. Add a ROA for AS40412, maxLength 24. |
| Route object: none | 63.88.36.0/24 | No route object for it. Add a route object with origin AS40412 in the RIR database for the space. |
| ROA: none | 63.88.37.0/24 | No ROA covers it. Add a ROA for AS40412, maxLength 24. |
| Route object: none | 63.88.37.0/24 | No route object for it. Add a route object with origin AS40412 in the RIR database for the space. |
| ROA: none | 63.88.38.0/24 | No ROA covers it. Add a ROA for AS40412, maxLength 24. |
| Route object: none | 63.88.38.0/24 | No route object for it. Add a route object with origin AS40412 in the RIR database for the space. |
| ROA: none | 8.38.174.0/24 | No ROA covers it. Add a ROA for AS40412, maxLength 24. |
| Route object: RIR | 8.38.174.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 23.134.224.0/23 | No ROA covers it. Add a ROA for AS40412, maxLength 23. |
| Route object: RIR | 23.134.224.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 23.134.224.0/24 | No ROA covers it. Add a ROA for AS40412, maxLength 24. |
| Route object: RIR | 23.134.224.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS40412 whose prefix no peer sees AS40412 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 12.108.193.0/24 | RADB | No ROA |
| 2620:139::/40 | RADB | 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.