Network · data from 2026-11-12
AS270336 Careassunet Informatica
Registry name: AS270336 - Careassunet Informatica Ltda - ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270336, 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.
| 190.83.24.0/22 | No ROA | Other IRR onlyRADB, TC | 668 99% |
| 190.83.24.0/24 | No ROA | Other IRR onlyRADB, TC | 667 99% |
| 190.83.25.0/24 | No ROA | Other IRR onlyRADB, TC | 667 99% |
| 190.83.26.0/24 | No ROA | Other IRR onlyRADB, TC | 667 99% |
| 190.83.27.0/24 | No ROA | Other IRR onlyTC | 667 99% |
| 190.83.24.0/23 | No ROA | Other IRR onlyRADB, TC | 663 99% |
| 190.83.26.0/23 | No ROA | Other IRR onlyRADB, TC | 663 99% |
AS-SET
PeeringDB's irr_as_set for AS270336: AS270336:AS-UPSTREAMS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS270336 isn't in the set, or no route object for AS270336 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS270336 in it | Not covered |
|---|---|---|---|---|---|
| AS270336:AS-UPSTREAMS | TC | 4 | 1 | No | 7 |
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 22 are in fix.csv.
- ROA: none7
- Route object: RIR7
- AS-SET: own ASN1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 190.83.24.0/22 | No ROA covers it. Add a ROA for AS270336, maxLength 22. |
| Route object: RIR | 190.83.24.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 190.83.24.0/24 | No ROA covers it. Add a ROA for AS270336, maxLength 24. |
| Route object: RIR | 190.83.24.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 190.83.25.0/24 | No ROA covers it. Add a ROA for AS270336, maxLength 24. |
| Route object: RIR | 190.83.25.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 190.83.26.0/24 | No ROA covers it. Add a ROA for AS270336, maxLength 24. |
| Route object: RIR | 190.83.26.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 190.83.27.0/24 | No ROA covers it. Add a ROA for AS270336, maxLength 24. |
| Route object: RIR | 190.83.27.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 190.83.24.0/23 | No ROA covers it. Add a ROA for AS270336, maxLength 23. |
| Route object: RIR | 190.83.24.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 190.83.26.0/23 | No ROA covers it. Add a ROA for AS270336, maxLength 23. |
| Route object: RIR | 190.83.26.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS270336:AS-UPSTREAMS | AS270336 isn't in AS270336:AS-UPSTREAMS (TC) once expanded. Add AS270336 to it. |
Route objects not announced
Route objects with origin AS270336 whose prefix no peer sees AS270336 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:6a70::/32 | RADB, TC | No ROA |
| 2804:6a70::/33 | TC | No ROA |
| 2804:6a70::/34 | TC | No ROA |
| 2804:6a70:4000::/34 | TC | No ROA |
| 2804:6a70:8000::/33 | TC | No ROA |
| 2804:6a70:8000::/34 | TC | No ROA |
| 2804:6a70:c000::/34 | 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.