Network · data from 2026-11-12
AS61808 AS61808 - CONTINUY SERVICOS EM TECNOLOGIA DA INFORMACAO LTDA
Registry name: AS61808 - CONTINUY SERVICOS EM TECNOLOGIA DA INFORMACAO LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61808, 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:19a0:200::/40 | No ROA | Nonecovered by 2804:19a0::/32 | 634 100% |
| 201.7.208.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
| 201.7.209.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 201.7.210.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 201.7.211.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 201.7.208.0/24 | No ROA | Other IRR onlyRADB | 668 99% |
| 38.141.64.0/24 | No ROA | RIR databaseARIN | 668 99% |
| 38.141.65.0/24 | No ROA | RIR databaseARIN | 668 99% |
AS-SET
AS61808 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 16 are in fix.csv.
- ROA: none8
- Route object: none1
- Route object: RIR5
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:19a0:200::/40 | No ROA covers it. Add a ROA for AS61808, maxLength 40. |
| Route object: none | 2804:19a0:200::/40 | No route object for it. A route object for 2804:19a0::/32 with origin AS61808 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61808 in the RIR database for the space. |
| ROA: none | 201.7.208.0/22 | No ROA covers it. Add a ROA for AS61808, maxLength 22. |
| Route object: RIR | 201.7.208.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 201.7.209.0/24 | No ROA covers it. Add a ROA for AS61808, maxLength 24. |
| Route object: RIR | 201.7.209.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 201.7.210.0/24 | No ROA covers it. Add a ROA for AS61808, maxLength 24. |
| Route object: RIR | 201.7.210.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 201.7.211.0/24 | No ROA covers it. Add a ROA for AS61808, maxLength 24. |
| Route object: RIR | 201.7.211.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 201.7.208.0/24 | No ROA covers it. Add a ROA for AS61808, maxLength 24. |
| Route object: RIR | 201.7.208.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.141.64.0/24 | No ROA covers it. Add a ROA for AS61808, maxLength 24. |
| ROA: none | 38.141.65.0/24 | No ROA covers it. Add a ROA for AS61808, maxLength 24. |
Route objects not announced
Route objects with origin AS61808 whose prefix no peer sees AS61808 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:19a0::/32 | RADB | No ROA |
| 2804:19a0::/40 | 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.