Network · data from 2026-11-12
AS22317 F5-NETWORKS - F5, Inc.
Registry name: F5-NETWORKS - F5, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS22317, 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.
| 12.202.13.0/24 | No ROA | None | 673 100% |
| 2620:0:c12::/48 | Valid | Nonecovered by 2620:0:c10::/44 | 636 100% |
| 2620:0:c13::/48 | Valid | Nonecovered by 2620:0:c10::/44 | 636 100% |
| 2620:0:c14::/48 | Valid | Nonecovered by 2620:0:c10::/44 | 636 100% |
| 2620:128:e000::/48 | Valid | Nonecovered by 2620:128:e000::/40 | 636 100% |
| 2620:128:e004::/48 | Valid | Nonecovered by 2620:128:e000::/40 | 636 100% |
| 2620:128:e008::/48 | Valid | Nonecovered by 2620:128:e000::/40 | 636 100% |
| 2620:128:e040::/48 | Valid | Nonecovered by 2620:128:e000::/40 | 636 100% |
| 2620:0:c15::/48 | Valid | Nonecovered by 2620:0:c10::/44 | 635 100% |
| 2620:128:e00c::/48 | Valid | Nonecovered by 2620:128:e000::/40 | 635 100% |
| 2620:128:e080::/48 | Valid | Nonecovered by 2620:128:e000::/40 | 635 100% |
| 2620:128:e082::/48 | Valid | Nonecovered by 2620:128:e000::/40 | 635 100% |
| 2001:559:c37c::/48 | Valid | None | 628 99% |
| 2620:128:e014::/48 | Valid | Other IRR onlyRADB | 1 0%low visibility |
| 104.219.105.0/24 | Valid | RIR databaseARIN | 673 100% |
| 104.219.107.0/24 | Valid | RIR databaseARIN | 673 100% |
| 104.219.109.0/24 | Valid | RIR databaseARIN | 673 100% |
| 104.219.104.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 104.219.106.0/24 | Valid | RIR databaseARIN | 672 100% |
| 104.219.108.0/24 | Valid | RIR databaseARIN | 672 100% |
| 104.219.110.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 104.219.111.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 208.85.208.0/24 | Valid | RIR databaseARIN | 672 100% |
| 208.85.209.0/24 | Valid | RIR databaseARIN | 672 100% |
AS-SET
AS22317 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 21 are in fix.csv.
- ROA: none1
- Route object: none13
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 12.202.13.0/24 | No ROA covers it. Add a ROA for AS22317, maxLength 24. |
| Route object: none | 12.202.13.0/24 | No route object for it. Add a route object with origin AS22317 in the RIR database for the space. |
| Route object: none | 2620:0:c12::/48 | No route object for it. A route object for 2620:0:c10::/44 with origin AS22317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22317 in the RIR database for the space. |
| Route object: none | 2620:0:c13::/48 | No route object for it. A route object for 2620:0:c10::/44 with origin AS22317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22317 in the RIR database for the space. |
| Route object: none | 2620:0:c14::/48 | No route object for it. A route object for 2620:0:c10::/44 with origin AS22317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22317 in the RIR database for the space. |
| Route object: none | 2620:128:e000::/48 | No route object for it. A route object for 2620:128:e000::/40 with origin AS22317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22317 in the RIR database for the space. |
| Route object: none | 2620:128:e004::/48 | No route object for it. A route object for 2620:128:e000::/40 with origin AS22317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22317 in the RIR database for the space. |
| Route object: none | 2620:128:e008::/48 | No route object for it. A route object for 2620:128:e000::/40 with origin AS22317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22317 in the RIR database for the space. |
| Route object: none | 2620:128:e040::/48 | No route object for it. A route object for 2620:128:e000::/40 with origin AS22317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22317 in the RIR database for the space. |
| Route object: none | 2620:0:c15::/48 | No route object for it. A route object for 2620:0:c10::/44 with origin AS22317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22317 in the RIR database for the space. |
| Route object: none | 2620:128:e00c::/48 | No route object for it. A route object for 2620:128:e000::/40 with origin AS22317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22317 in the RIR database for the space. |
| Route object: none | 2620:128:e080::/48 | No route object for it. A route object for 2620:128:e000::/40 with origin AS22317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22317 in the RIR database for the space. |
| Route object: none | 2620:128:e082::/48 | No route object for it. A route object for 2620:128:e000::/40 with origin AS22317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22317 in the RIR database for the space. |
| Route object: none | 2001:559:c37c::/48 | No route object for it. Add a route object with origin AS22317 in the RIR database for the space. |
| Route object: RIR | 2620:128:e014::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS22317 whose prefix no peer sees AS22317 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 104.219.104.0/21 | ARIN, RADB | Valid |
| 208.85.208.0/22 | ARIN, RADB | Valid |
| 212.113.24.64/27 | RADB | No ROA |
| 2620:0:c10::/44 | ARIN, RADB | Valid |
| 2620:0:c10::/48 | NTTCOM | Valid |
| 2620:128:e000::/40 | ARIN, 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.