Announced routes
Every prefix a peer of the route collectors sees with origin AS27814, 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.
| 200.110.112.0/22 | Valid | Nonecovered by 200.110.112.0/21 | 668 99% |
| 200.110.116.0/22 | Valid | Nonecovered by 200.110.112.0/21 | 668 99% |
| 200.110.124.0/23 | Valid | Nonecovered by 200.110.124.0/22 | 668 99% |
| 200.110.126.0/24 | Valid | Nonecovered by 200.110.124.0/22 | 668 99% |
| 2001:13c7:6f00::/46 | Valid | Nonecovered by 2001:13c7:6f00::/45 | 633 100% |
| 2001:13c7:6f04::/46 | Valid | Nonecovered by 2001:13c7:6f00::/45 | 633 100% |
| 2001:13c7:6f08::/48 | Valid | Nonecovered by 2001:13c7:6f00::/41 | 633 100% |
| 2001:13c7:6f09::/48 | Valid | Nonecovered by 2001:13c7:6f00::/41 | 633 100% |
| 2001:13c7:6f0a::/48 | Valid | Nonecovered by 2001:13c7:6f00::/41 | 633 100% |
| 2001:13c7:6f10::/45 | Valid | Nonecovered by 2001:13c7:6f00::/41 | 633 100% |
| 200.110.112.0/23 | Valid | Nonecovered by 200.110.112.0/21 | 19 3%low visibility |
| 200.110.114.0/23 | Valid | Nonecovered by 200.110.112.0/21 | 19 3%low visibility |
| 200.110.116.0/23 | Valid | Nonecovered by 200.110.112.0/21 | 19 3%low visibility |
| 200.110.118.0/23 | Valid | Nonecovered by 200.110.112.0/21 | 19 3%low visibility |
| 2001:13c7:6f00::/47 | Valid | Nonecovered by 2001:13c7:6f00::/45 | 15 2%low visibility |
| 2001:13c7:6f02::/47 | Valid | Nonecovered by 2001:13c7:6f00::/45 | 15 2%low visibility |
| 2001:13c7:6f04::/47 | Valid | Nonecovered by 2001:13c7:6f00::/45 | 15 2%low visibility |
| 2001:13c7:6f06::/47 | Valid | Nonecovered by 2001:13c7:6f00::/45 | 15 2%low visibility |
| 200.110.127.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 2001:13c7:6f00::/45 | Valid | Other IRR onlyRADB | 632 99% |
| 2001:13c7:6f10::/48 | Valid | Other IRR onlyRADB | 630 99% |
| 200.110.112.0/21 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 200.110.122.0/23 | Valid | RIR databaseLACNIC | 668 99% |
AS-SET
AS27814's PeeringDB record names no 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 34 are in fix.csv.
- Route object: none18
- Route object: RIR3
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 200.110.112.0/22 | No route object for it. A route object for 200.110.112.0/21 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 200.110.116.0/22 | No route object for it. A route object for 200.110.112.0/21 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 200.110.124.0/23 | No route object for it. A route object for 200.110.124.0/22 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 200.110.126.0/24 | No route object for it. A route object for 200.110.124.0/22 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 2001:13c7:6f00::/46 | No route object for it. A route object for 2001:13c7:6f00::/45 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 2001:13c7:6f04::/46 | No route object for it. A route object for 2001:13c7:6f00::/45 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 2001:13c7:6f08::/48 | No route object for it. A route object for 2001:13c7:6f00::/41 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 2001:13c7:6f09::/48 | No route object for it. A route object for 2001:13c7:6f00::/41 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 2001:13c7:6f0a::/48 | No route object for it. A route object for 2001:13c7:6f00::/41 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 2001:13c7:6f10::/45 | No route object for it. A route object for 2001:13c7:6f00::/41 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 200.110.112.0/23 | No route object for it. A route object for 200.110.112.0/21 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 200.110.114.0/23 | No route object for it. A route object for 200.110.112.0/21 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 200.110.116.0/23 | No route object for it. A route object for 200.110.112.0/21 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 200.110.118.0/23 | No route object for it. A route object for 200.110.112.0/21 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 2001:13c7:6f00::/47 | No route object for it. A route object for 2001:13c7:6f00::/45 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 2001:13c7:6f02::/47 | No route object for it. A route object for 2001:13c7:6f00::/45 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 2001:13c7:6f04::/47 | No route object for it. A route object for 2001:13c7:6f00::/45 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: none | 2001:13c7:6f06::/47 | No route object for it. A route object for 2001:13c7:6f00::/45 with origin AS27814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27814 in the RIR database for the space. |
| Route object: RIR | 200.110.127.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:13c7:6f00::/45 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:13c7:6f10::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS27814 whose prefix no peer sees AS27814 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.110.112.0/20 | RADB | No ROA |
| 200.110.112.0/24 | RADB | Valid |
| 200.110.113.0/24 | RADB | Valid |
| 200.110.114.0/24 | RADB | Valid |
| 200.110.115.0/24 | RADB | Valid |
| 200.110.116.0/24 | RADB | Valid |
| 200.110.117.0/24 | RADB | Valid |
| 200.110.118.0/24 | RADB | Valid |
| 200.110.119.0/24 | RADB | Valid |
| 200.110.124.0/22 | LACNIC | Valid |
| 2001:13c7:6f00::/40 | RADB | No ROA |
| 2001:13c7:6f00::/41 | LACNIC | Valid |
| 2001:13c7:6f81::/48 | 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.