Network · data from 2026-11-12
AS40475 Applied Operations
Registry name: APPLIEDOPS - Applied Operations, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40475, 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.
| 69.22.175.0/24 | No ROA | Other IRR onlyALTDB, RADB | 668 99% |
| 74.116.248.0/22 | No ROA | Other IRR onlyALTDB | 668 99% |
| 199.181.107.0/24 | No ROA | Other IRR onlyALTDB | 668 99% |
| 204.27.132.0/24 | No ROA | Other IRR onlyALTDB | 668 99% |
| 208.83.220.0/22 | No ROA | Other IRR onlyALTDB | 668 99% |
| 2607:ff58::/32 | No ROA | Other IRR onlyALTDB, RADB | 636 100% |
| 199.48.144.0/22 | No ROA | Other IRR onlyALTDB | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS40475: AS-APPLIEDOPS. 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 (AS40475 isn't in the set, or no route object for AS40475 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 | AS40475 in it | Not covered |
|---|---|---|---|---|---|
| AS-APPLIEDOPS | ALTDB | 9 | 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 17 are in fix.csv.
- ROA: none7
- Route object: RIR7
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 69.22.175.0/24 | No ROA covers it. Add a ROA for AS40475, maxLength 24. |
| Route object: RIR | 69.22.175.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| ROA: none | 74.116.248.0/22 | No ROA covers it. Add a ROA for AS40475, maxLength 22. |
| Route object: RIR | 74.116.248.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 199.181.107.0/24 | No ROA covers it. Add a ROA for AS40475, maxLength 24. |
| Route object: RIR | 199.181.107.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 204.27.132.0/24 | No ROA covers it. Add a ROA for AS40475, maxLength 24. |
| Route object: RIR | 204.27.132.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 208.83.220.0/22 | No ROA covers it. Add a ROA for AS40475, maxLength 22. |
| Route object: RIR | 208.83.220.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 2607:ff58::/32 | No ROA covers it. Add a ROA for AS40475, maxLength 32. |
| Route object: RIR | 2607:ff58::/32 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| ROA: none | 199.48.144.0/22 | No ROA covers it. Add a ROA for AS40475, maxLength 22. |
| Route object: RIR | 199.48.144.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS40475 whose prefix no peer sees AS40475 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 69.22.167.0/26 | ALTDB | No ROA |
| 192.203.228.0/24 | ALTDB | No ROA |
| 203.56.168.0/24 | ALTDB | 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.