Network · data from 2026-11-12
AS271760 Creating Cloud Solutions
Registry name: AS271760 - CCS BRASIL SERVICOS EM TELECOMUNICACOES LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271760, 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.
| 2804:8094:1000::/38 | No ROA | Nonecovered by 2804:8094::/33 | 636 100% |
| 2804:8094::/32 | No ROA | Other IRR onlyRADB, TC | 635 100% |
AS-SET
AS271760'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 6 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:8094:1000::/38 | No ROA covers it. Add a ROA for AS271760, maxLength 38. |
| Route object: none | 2804:8094:1000::/38 | No route object for it. A route object for 2804:8094::/33 with origin AS271760 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271760 in the RIR database for the space. |
| ROA: none | 2804:8094::/32 | No ROA covers it. Add a ROA for AS271760, maxLength 32. |
| Route object: RIR | 2804:8094::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS271760 whose prefix no peer sees AS271760 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:8094::/33 | RADB, TC | No ROA |
| 2804:8094:8000::/33 | RADB, TC | 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.