Network · data from 2026-11-12
AS268319 AS268319 - CONTINENTAL EMPREENDIMENTOS EIRELI-ME
Registry name: AS268319 - CONTINENTAL EMPREENDIMENTOS EIRELI-ME, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS268319, 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.
| 45.238.76.0/22 | No ROA | Other IRR onlyRADB, TC | 669 99% |
| 2804:4f50::/32 | No ROA | Other IRR onlyRADB, TC | 631 99% |
AS-SET
AS268319 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: none2
- Route object: RIR2
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.238.76.0/22 | No ROA covers it. Add a ROA for AS268319, maxLength 22. |
| Route object: RIR | 45.238.76.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:4f50::/32 | No ROA covers it. Add a ROA for AS268319, maxLength 32. |
| Route object: RIR | 2804:4f50::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS268319 whose prefix no peer sees AS268319 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.238.76.0/23 | RADB, TC | No ROA |
| 45.238.76.0/24 | TC | No ROA |
| 45.238.77.0/24 | RADB, TC | No ROA |
| 45.238.78.0/23 | RADB, TC | No ROA |
| 45.238.78.0/24 | RADB, TC | No ROA |
| 45.238.79.0/24 | RADB, TC | No ROA |
| 2804:4f50::/33 | TC | No ROA |
| 2804:4f50::/34 | TC | No ROA |
| 2804:4f50:4000::/34 | TC | No ROA |
| 2804:4f50:8000::/33 | TC | No ROA |
| 2804:4f50:8000::/34 | TC | No ROA |
| 2804:4f50: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.