Network · data from 2026-11-12
AS10487 SIMPLENET - Simple Network Communications, Inc
Registry name: SIMPLENET - Simple Network Communications, Inc, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10487, 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.
| 204.10.64.0/24 | No ROA | Nonecovered by 204.10.64.0/21 | 672 100% |
| 209.132.80.0/20 | No ROA | Nonecovered by 209.132.0.0/17 | 672 100% |
| 209.132.96.0/19 | No ROA | Nonecovered by 209.132.0.0/17 | 672 100% |
| 216.188.146.0/23 | No ROA | Nonecovered by 216.188.128.0/18 | 672 100% |
| 216.188.148.0/22 | No ROA | Nonecovered by 216.188.128.0/18 | 672 100% |
| 216.188.152.0/21 | No ROA | Nonecovered by 216.188.128.0/18 | 672 100% |
| 216.188.160.0/19 | No ROA | Other origin onlycovered by 216.188.128.0/18 | 672 100% |
| 2607:4d00:6000::/35 | No ROA | Other IRR onlyRADB | 635 100% |
AS-SET
AS10487 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 29 are in fix.csv.
- ROA: none8
- Route object: none7
- Route object: RIR1
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 204.10.64.0/24 | No ROA covers it. Add a ROA for AS10487, maxLength 24. |
| Route object: none | 204.10.64.0/24 | No route object for it. A route object for 204.10.64.0/21 with origin AS10487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10487 in the RIR database for the space. |
| ROA: none | 209.132.80.0/20 | No ROA covers it. Add a ROA for AS10487, maxLength 20. |
| Route object: none | 209.132.80.0/20 | No route object for it. A route object for 209.132.0.0/17 with origin AS10487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10487 in the RIR database for the space. |
| ROA: none | 209.132.96.0/19 | No ROA covers it. Add a ROA for AS10487, maxLength 19. |
| Route object: none | 209.132.96.0/19 | No route object for it. A route object for 209.132.0.0/17 with origin AS10487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10487 in the RIR database for the space. |
| ROA: none | 216.188.146.0/23 | No ROA covers it. Add a ROA for AS10487, maxLength 23. |
| Route object: none | 216.188.146.0/23 | No route object for it. A route object for 216.188.128.0/18 with origin AS10487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10487 in the RIR database for the space. |
| ROA: none | 216.188.148.0/22 | No ROA covers it. Add a ROA for AS10487, maxLength 22. |
| Route object: none | 216.188.148.0/22 | No route object for it. A route object for 216.188.128.0/18 with origin AS10487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10487 in the RIR database for the space. |
| ROA: none | 216.188.152.0/21 | No ROA covers it. Add a ROA for AS10487, maxLength 21. |
| Route object: none | 216.188.152.0/21 | No route object for it. A route object for 216.188.128.0/18 with origin AS10487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10487 in the RIR database for the space. |
| ROA: none | 216.188.160.0/19 | No ROA covers it. Add a ROA for AS10487, maxLength 19. |
| Route object: none | 216.188.160.0/19 | Route objects for it name AS14572. A route object for 216.188.128.0/18 with origin AS10487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10487 in the RIR database for the space. |
| ROA: none | 2607:4d00:6000::/35 | No ROA covers it. Add a ROA for AS10487, maxLength 35. |
| Route object: RIR | 2607:4d00:6000::/35 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10487 whose prefix no peer sees AS10487 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 199.48.232.0/21 | RADB | No ROA |
| 199.180.80.0/22 | RADB | No ROA |
| 199.187.184.0/22 | RADB | No ROA |
| 204.10.64.0/21 | RADB | No ROA |
| 204.15.120.0/21 | RADB | No ROA |
| 208.77.48.0/21 | RADB | No ROA |
| 209.132.0.0/17 | RADB | No ROA |
| 216.188.0.0/17 | RADB | No ROA |
| 216.188.128.0/18 | RADB | No ROA |
| 2607:4d00::/32 | RADB | No ROA |
| 2607:4d00::/35 | RADB | No ROA |
| 2607:4d00:2000::/35 | RADB | No ROA |
| 2607:4d00:4000::/35 | 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.