Network · data from 2026-11-12
AS5015 SHOUTING - Shouting Ground Technologies
Registry name: SHOUTING - Shouting Ground Technologies, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS5015, 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.
| 66.209.200.0/24 | No ROA | None | 2 0%low visibility |
| 66.209.212.0/23 | No ROA | None | 2 0%low visibility |
| 66.209.205.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 66.209.204.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 66.209.206.0/24 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 66.209.215.0/24 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 66.209.192.0/21 | No ROA | RIR databaseARIN | 2 0%low visibility |
| 66.209.202.0/23 | No ROA | RIR databaseARIN | 2 0%low visibility |
| 66.209.208.0/22 | No ROA | RIR databaseARIN | 2 0%low visibility |
| 66.209.214.0/24 | No ROA | RIR databaseARIN | 2 0%low visibility |
| 66.209.216.0/21 | No ROA | RIR databaseARIN | 2 0%low visibility |
AS-SET
AS5015 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 34 are in fix.csv.
- ROA: none11
- Route object: none2
- Route object: RIR4
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 66.209.200.0/24 | No ROA covers it. Add a ROA for AS5015, maxLength 24. |
| Route object: none | 66.209.200.0/24 | No route object for it. Add a route object with origin AS5015 in the RIR database for the space. |
| ROA: none | 66.209.212.0/23 | No ROA covers it. Add a ROA for AS5015, maxLength 23. |
| Route object: none | 66.209.212.0/23 | No route object for it. Add a route object with origin AS5015 in the RIR database for the space. |
| ROA: none | 66.209.205.0/24 | No ROA covers it. Add a ROA for AS5015, maxLength 24. |
| Route object: RIR | 66.209.205.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 66.209.204.0/24 | No ROA covers it. Add a ROA for AS5015, maxLength 24. |
| Route object: RIR | 66.209.204.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 66.209.206.0/24 | No ROA covers it. Add a ROA for AS5015, maxLength 24. |
| Route object: RIR | 66.209.206.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 66.209.215.0/24 | No ROA covers it. Add a ROA for AS5015, maxLength 24. |
| Route object: RIR | 66.209.215.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 66.209.192.0/21 | No ROA covers it. Add a ROA for AS5015, maxLength 21. |
| ROA: none | 66.209.202.0/23 | No ROA covers it. Add a ROA for AS5015, maxLength 23. |
| ROA: none | 66.209.208.0/22 | No ROA covers it. Add a ROA for AS5015, maxLength 22. |
| ROA: none | 66.209.214.0/24 | No ROA covers it. Add a ROA for AS5015, maxLength 24. |
| ROA: none | 66.209.216.0/21 | No ROA covers it. Add a ROA for AS5015, maxLength 21. |
Route objects not announced
Route objects with origin AS5015 whose prefix no peer sees AS5015 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 66.209.192.0/24 | RADB | No ROA |
| 66.209.193.0/24 | RADB | No ROA |
| 66.209.194.0/24 | RADB | No ROA |
| 66.209.195.0/24 | RADB | No ROA |
| 66.209.196.0/24 | RADB | No ROA |
| 66.209.197.0/24 | RADB | No ROA |
| 66.209.198.0/24 | RADB | No ROA |
| 66.209.199.0/24 | RADB | No ROA |
| 66.209.201.0/24 | RADB | No ROA |
| 66.209.202.0/24 | RADB | No ROA |
| 66.209.203.0/24 | RADB | No ROA |
| 66.209.207.0/24 | RADB | No ROA |
| 66.209.208.0/24 | RADB | No ROA |
| 66.209.209.0/24 | RADB | No ROA |
| 66.209.210.0/24 | RADB | No ROA |
| 66.209.212.0/24 | RADB | No ROA |
| 66.209.213.0/24 | ARIN | 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.