Network · data from 2026-11-12
AS61280 CMU_GRCHC FGUP "GRCHC"
Registry name: CMU_GRCHC FGUP "GRCHC", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61280, 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.
| 185.224.230.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.224.231.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 212.192.157.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.224.228.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 195.209.122.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 195.209.123.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 212.192.156.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 212.192.158.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 212.192.159.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 2a0c:a9c7:156::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 2a0c:a9c7:157::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 2a0c:a9c7:158::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 185.224.229.0/24 | No ROA | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS61280 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 17 are in fix.csv.
- ROA: none13
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.224.230.0/24 | No ROA covers it. Add a ROA for AS61280, maxLength 24. |
| ROA: none | 185.224.231.0/24 | No ROA covers it. Add a ROA for AS61280, maxLength 24. |
| ROA: none | 212.192.157.0/24 | No ROA covers it. Add a ROA for AS61280, maxLength 24. |
| ROA: none | 185.224.228.0/24 | No ROA covers it. Add a ROA for AS61280, maxLength 24. |
| ROA: none | 195.209.122.0/24 | No ROA covers it. Add a ROA for AS61280, maxLength 24. |
| ROA: none | 195.209.123.0/24 | No ROA covers it. Add a ROA for AS61280, maxLength 24. |
| ROA: none | 212.192.156.0/24 | No ROA covers it. Add a ROA for AS61280, maxLength 24. |
| ROA: none | 212.192.158.0/24 | No ROA covers it. Add a ROA for AS61280, maxLength 24. |
| ROA: none | 212.192.159.0/24 | No ROA covers it. Add a ROA for AS61280, maxLength 24. |
| ROA: none | 2a0c:a9c7:156::/48 | No ROA covers it. Add a ROA for AS61280, maxLength 48. |
| ROA: none | 2a0c:a9c7:157::/48 | No ROA covers it. Add a ROA for AS61280, maxLength 48. |
| ROA: none | 2a0c:a9c7:158::/48 | No ROA covers it. Add a ROA for AS61280, maxLength 48. |
| ROA: none | 185.224.229.0/24 | No ROA covers it. Add a ROA for AS61280, maxLength 24. |
Route objects not announced
Route objects with origin AS61280 whose prefix no peer sees AS61280 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 195.209.120.0/22 | RIPE | No ROA |
| 195.209.120.0/24 | RIPE | No ROA |
| 195.209.121.0/24 | RIPE | No ROA |
| 212.192.156.0/22 | 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.