Announced routes
Every prefix a peer of the route collectors sees with origin AS22772, 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.
| 52.124.58.0/24 | No ROA | RIR databaseARIN | 670 100% |
| 69.160.160.0/24 | No ROA | RIR databaseARIN | 670 100% |
| 139.60.16.0/22 | No ROA | RIR databaseARIN | 670 100% |
| 148.59.152.0/24 | No ROA | RIR databaseARIN | 670 100% |
| 198.160.250.0/24 | No ROA | RIR databaseARIN | 670 100% |
| 199.85.92.0/22 | No ROA | RIR databaseARIN | 670 100% |
| 204.8.239.0/24 | No ROA | RIR databaseARIN | 670 100% |
| 207.229.78.0/24 | No ROA | RIR databaseARIN | 670 100% |
| 204.17.50.0/24 | Valid | Nonecovered by 204.17.32.0/19 | 671 100% |
| 209.104.16.0/22 | Valid | Nonecovered by 209.104.0.0/19 | 670 100% |
| 192.195.240.0/24 | Valid | RIR databaseARIN | 670 100% |
| 198.182.64.0/18 | Valid | RIR databaseARIN | 670 100% |
| 199.33.243.0/24 | Valid | RIR databaseARIN | 670 100% |
| 204.17.32.0/19 | Valid | RIR databaseARIN | 670 100% |
| 209.104.0.0/19 | Valid | RIR databaseARIN | 670 100% |
| 2605:8e00::/32 | Valid | RIR databaseARIN | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS22772: AS-22772. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS22772 isn't in the set, or no route object for AS22772 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS22772 in it | Not covered |
|---|---|---|---|---|---|
| AS-22772 | ARIN | 15 | 1 | Yes | 0 |
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.
- ROA: none8
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 52.124.58.0/24 | No ROA covers it. Add a ROA for AS22772, maxLength 24. |
| ROA: none | 69.160.160.0/24 | No ROA covers it. Add a ROA for AS22772, maxLength 24. |
| ROA: none | 139.60.16.0/22 | No ROA covers it. Add a ROA for AS22772, maxLength 22. |
| ROA: none | 148.59.152.0/24 | No ROA covers it. Add a ROA for AS22772, maxLength 24. |
| ROA: none | 198.160.250.0/24 | No ROA covers it. Add a ROA for AS22772, maxLength 24. |
| ROA: none | 199.85.92.0/22 | No ROA covers it. Add a ROA for AS22772, maxLength 22. |
| ROA: none | 204.8.239.0/24 | No ROA covers it. Add a ROA for AS22772, maxLength 24. |
| ROA: none | 207.229.78.0/24 | No ROA covers it. Add a ROA for AS22772, maxLength 24. |
| Route object: none | 204.17.50.0/24 | No route object for it. A route object for 204.17.32.0/19 with origin AS22772 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22772 in the RIR database for the space. |
| Route object: none | 209.104.16.0/22 | No route object for it. A route object for 209.104.0.0/19 with origin AS22772 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22772 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS22772 is announced.
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.